Chart Engine v1.1.3

Release Date: August 26, 2026 Tags: ALERTS, CHART, INTERACTION, RENDERING

Overview

Price alerts drawn on the chart are now the same alerts the server watches. They lived in the browser's own storage: they existed on one device, in one browser, and were only evaluated while the tab was open — which is the situation an alert exists for the absence of. They now sync to the account, so an alert set on a laptop fires on a phone with the tab closed, and the chart lines, the trade panel and the alert list all read one record.

Syncing is best effort in one direction only. A push that fails leaves a working local alert rather than an error in a chart render, and a truncated list from the server is never read as "these were deleted" — the reconciler refuses to remove anything it cannot prove is gone.

The alert hover card was also being sliced in half. It was drawn inside the clipped lines layer at a fixed offset, so an alert near the top or bottom of the plot lost its header row — and the header is the row carrying the condition, so what survived was a headless number that read like nothing at all.

Update Instructions

pnpm updator

Ship the frontend build. Existing alerts in a browser are adopted on first load and pushed to the account; nothing is lost. Requires Core v6.7.2 for the server side.

Added

Alerts belong to the account, not to the browser

• Added two-way syncing between the chart's alerts and the account's alert list, so one alert exists once and is evaluated whether or not a tab is open.
• Added adoption of the alerts already in a browser on first load, so nobody loses what they had set.
• Every network call is best effort and degrades to the previous browser-only behaviour. An alert that cannot reach the server is still a working alert in this browser.
• A server list that hits its cap is marked incomplete, and the reconciler will not delete a local alert on the strength of a list that may be missing rows.

Fixed

The alert hover card was cut off near the edges of the plot

The lines layer needs to clip — a dashed rule and a percentage chip are drawn at the alert's price and must not bleed past the plot. The hover card was drawn in that same clipped layer at a fixed offset above the line, so an alert anywhere near the top or bottom lost part of the card. The header row went first, and the header is what says whether the alert rises above or falls below.

• Fixed the card to live in its own unclipped layer, measure itself and clamp into the space available, so it stays whole at any price.
• Changed the notch to move inside the card rather than moving the card, which is what lets it keep pointing at the right line without leaving the plot.
• Changed the card's clearance from the price axis to scale with the axis width. The percentage chip that marks which line the card belongs to is drawn at an offset from that axis, and a card anchored closer covered it.

Dragging an alert line lost sub-pixel movement

• Fixed the drag threshold to accumulate across the whole gesture rather than looking at a single sample. A slow drag made of sub-pixel steps never crossed the threshold, so the line did not move and the press was treated as a click.
• Changed the re-render to happen twice per gesture rather than twice per sample.