We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
5.5.1
https://echarts.apache.org/examples/en/editor.html?c=bar-negative&version=5.3.0&code=PYBwLglsB2AEC8sDeBYAULTsBEAPAgrhAM7YBcy6WW2AJgIZj3mwDaAjAEwC6VWAvgBo-mbAE9CJFkiEicxAKYAnCAtIVWc6qgzU9osGJAKW2AEb0l2Ybv3U6jZhq13qm2689cbn37ABs7C6-3D5-ocF62MRMAMYA1qbMYfqyHtqR9obGphZWKZ4OTCzufnqlZXbemX4AzAAcNfoR6XYtZdFxiRTYyZH8crxo_EA
Create a chart with the following options with atleast echarts v5.3.0:
{ "xAxis": { "data": [12] }, "yAxis": {}, "series": [ { "type": "bar", "data": [ [ 12, 61 ], ], "stack": "a", }, { "type": "bar", "data": [ [ 12, 38 ], ], "stack": "a", } ] }
The Bars overlap and each series starts at 0.
The Bars should be stacked.
- OS: Windows 11 - Browser: Chrome 128.0.6613.138 - Framework:
The Bug exists since version 5.3.0. It still worked with version 5.2.2.
The text was updated successfully, but these errors were encountered:
duplicate of #16765 and others, PR pending. BTW does not seem to work with version 5.2.2 either.
Sorry, something went wrong.
No branches or pull requests
Version
5.5.1
Link to Minimal Reproduction
https://echarts.apache.org/examples/en/editor.html?c=bar-negative&version=5.3.0&code=PYBwLglsB2AEC8sDeBYAULTsBEAPAgrhAM7YBcy6WW2AJgIZj3mwDaAjAEwC6VWAvgBo-mbAE9CJFkiEicxAKYAnCAtIVWc6qgzU9osGJAKW2AEb0l2Ybv3U6jZhq13qm2689cbn37ABs7C6-3D5-ocF62MRMAMYA1qbMYfqyHtqR9obGphZWKZ4OTCzufnqlZXbemX4AzAAcNfoR6XYtZdFxiRTYyZH8crxo_EA
Steps to Reproduce
Create a chart with the following options with atleast echarts v5.3.0:
Current Behavior
The Bars overlap and each series starts at 0.
Expected Behavior
The Bars should be stacked.
Environment
Any additional comments?
The Bug exists since version 5.3.0.
It still worked with version 5.2.2.
The text was updated successfully, but these errors were encountered: