Apache ECharts 5.3.3 Release: New Features and Bug Fixes
Apache ECharts 5.3.3 has been released, introducing new stacking strategies for bar charts, tree focus support, boolean selectedMode for visualMap, and a series of bug fixes across line, tree, graph, radar, geo, tooltip, dataZoom, markLine, markArea, axis, graphic, decal, radialGradient, and type definitions.
Apache ECharts is an open‑source JavaScript visualization library that runs smoothly on both PC and mobile devices and supports most modern browsers. It is built on the ZRender vector graphics engine and offers intuitive, highly interactive, and customizable charts.
Version 5.3.3 has been released with the following updates:
Feature: Added new stacking strategies for bar series.
Feature: Tree focus now supports relative.
Feature: visualMap now supports a boolean selectedMode.
Fix: Resolved an issue where polygons did not update when switching from line to step line chart with notMerge: true.
Fix: Fixed unexpected expansion of child nodes when edgeShape is set to polyline in tree charts.
Fix: Corrected the type handling of autoCurveness in graph series.
Fix: Patched a regression bug caused by branch merging in radar charts.
Fix: Fixed rendering issues for the linesGL series in geo charts.
Fix: Improved the type definition of PictorialBarSeriesOption.
Fix: Resolved tooltip content not updating correctly when triggerOn is set to click.
Fix: Fixed borderColor not working in some bundled environments for dataZoom.
Fix: Corrected tooltip content errors for markLine labels.
Fix: Prevented accidental filtering of markArea elements.
Fix: Fixed year‑month formatting issue where {yy} was not padded to two digits.
Fix: Adjusted quarter calculation to correctly divide a year into four quarters.
Fix: Fixed custom series incompatibility with singleAxis.
Fix: Prevented certain graphic options from being unintentionally reset during updates.
Fix: Fixed decal rendering when legend.itemStyle.decal is set to 'none'.
Fix: Added safety checks for radial gradients.
Fix: Corrected a spelling mistake in the DataStore type definitions.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
Laravel Tech Community
Specializing in Laravel development, we continuously publish fresh content and grow alongside the elegant, stable Laravel framework.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.
