[Bug] Stacked bar chart is missing a bar when log scale is used

[kawsndriy]

Version

5.4.3

Link to Minimal Reproduction

https://echarts.apache.org/examples/en/editor.html?code=PYBwLglsB2AEC8sDeAoWsCG0IFsORgC5YAzDAGwGcBTAGjVjGGHMhGKQF970BPAQQAeEShwbowvENWIBycsADmshtwaChIseglSZsWQGN81RcABOvWTx0ATfBmIBtWQDEI5ymGsGAytUMYW1kAXVUbGnMIalFYJ3FkBN1pOQAjDHNrJNgAehzYVIBXRWIwAAtqc2pYSkKQEGAaW0ZgAuryquqqwzAsRXIY2BhGCprDTuhsvNgAeWhyXkYAd1aM6ttzDCXoADps-17nWQBaHwAmAAYrkJsdGt7DAGs5PAhoFTu1O9Q75P1ZdKZW52BzOM4AViutFgAGYrhcbtkvBgni8MG8PjpOAwwpwANxAA

Steps to Reproduce

Use the following configuration:

option = {
  animation: false,
  tooltip: {},
  yAxis: {
    type: 'log' // this is important
  },
  xAxis: {
    type: 'category',
    data: ['First', 'Second']
  },
  series: [
    {
      type: 'bar',
      // bug: there supposed to be three rectangles on the screen
      // Only two are drawn.
      data: ['-', 2000],
      stack: 'main'
    },
    {
      type: 'bar',
      data: [2500, 3000],
      stack: 'main'
    }
  ]
};

Current Behavior

Looks like starting from version 5.3.0 the stacked bar chart with log scale is no longer rendered correctly when one of the stacks has no data marker (-). I

Expected Behavior

Expected to see all three bars present.

Environment

- OS: MacOS 13.6.3
- Browser: Chrome Version 120.0.6099.216 
- Framework: plain javascript

Any additional comments?

Looks like the bug was introduced by this commit in the barGrid.ts component - in pre 5.3.0 version the computation accounted for log scale correctly. In 5.3.0+ the log(0) is used to determine the height of the bar, which gives a negative infinity and lack of the rendered rectangle.

[helgasoft]

see also #19234, #18330, #17960

[Ovilia]

See conclusion at #19234. Stacked bars using log axis is misleading and thus this problem is not going to be fixed.

[kawsndriy]

I agree it might be misleading. I'd like to offer a few brief points for reconsideration:

• Community Interest: There's been notable interest in this feature. Based on number of referenced issues - it meets a specific user need.
• Correctness: The issue comes with a proposed fix that addresses a very narrow bug, enhancing reliability and trust built with users
• Other Libraries: Similar functionalities exist in other charting libraries, indicating a recognized utility in certain data visualization contexts.

For example, this matplotlib code allows to render log scaled stacked bars:

import matplotlib.pyplot as plt

categories = ['First', 'Second']
values1 = [1, 2000]
values2 = [2500, 3000]

fig, ax = plt.subplots()
ax.bar(categories, values1, label='Series 1')
ax.bar(categories, values2, bottom=values1, label='Series 2')

# Setting the y-axis to logarithmic scale - ok
ax.set_yscale('log')

plt.xlabel('Categories')
plt.ylabel('Values')
plt.title('Stacked Bar Chart with Log Scale')
plt.legend()

# Display the plot
plt.show()

Results in this nice looking image:

I hope the Pull request can be accepted as it limits the impact to a very narrow case and address one of our own concerns. Thank you!

[helgasoft]

Results in this nice looking image

If you like the matplot image, just replace '-' with 1 in the data and you'll get the exact same result

[kawsndriy]

just replace '-' with 1 in the data and you'll get the exact same result

That's essentially what the PR is doing

[helgasoft]

I think data transformation is a developer's task, it should not be part of any charting library.
Often data has to be modified to meet the needs of the chosen charting library, not the other way around.