apache / echarts

Apache ECharts is a powerful, interactive charting and data visualization library for browser
https://echarts.apache.org
Apache License 2.0
60.7k stars 19.62k forks source link

Value not shown on 'coord' markPoint with time axis #20410

Open mKainzbauer opened 1 month ago

mKainzbauer commented 1 month ago

Version

5.5.1

Link to Minimal Reproduction

https://echarts.apache.org/examples/en/editor.html?c=line-simple&code=PYBwLglsB2AEC8sDeAoWsA2BTA5l6AJgFzJrqxgCeIWJA5CBgIYTR0A0Z6BTYTJAbSSxoTALa1YdACpYxNAE68Argqx1YAXwC6ZTZ3QBjYBmALBdAMQAjACy2ATI7raDFYCcggSqchQUQOHjmUkwAHhAAzhxcsOFRAArArGBYIcJUNPQYrOpabuiRABbAAO4kYArKWAWwIMCREJAw9KyNBOp6bmEAghGRPrHFZRVVNbFirACS0KkKAG5MGCQAjA4rAKwADDtbtfGRADK5PrDD5bAAZkuRWPmxB9IQhgDWp-ck1xi3936ZknRIBIYn5IowmsdoJJhB9_NUtF0yJQ-lFBLFfH4ROIAQAGgDCIMx_3oiww1UJfiWgWgT1eAzh40xWIksjCYAAylRsKdLjAwAB1LCBIpgejWEwEDT6WLoA6HJjWLDLZBXPnsiAAL0kKxWv0xkUMS0klWqsU0ZFcZFuASw9IE6JlzIBsnkaRUagp5GU0Ca9HxnvQxKkOShAbOlDE4uVdGgMHUtXQIawnMo3JVpQgBDARVWer8PD4aKZ6AEKwA7A4ABwANhWthWux27FgAE4AHSVy3F2Clis12wbFstgDMu2bK2HbeHXeLvar1crti2DbHsGrbbLM6Zc8rZa2w5bZcrq8nm4T5B3ZZ1jabsEnLYcuiZW_IyP6Mw6YRIe0dYiYCheJIUkGbtIgjKN1S1b9z24Xh-B7R0_AyagAT_MIwyZZhFWVGESguE0ajqBomigaB6DAUApUQ8hpW7dBhGMMxiB7ct50XZdG2bdcz2ovwsKVd48NGapm3qRpmjIqQKJAKi6LzYsMTkxiFGYy990PY9b1PF9u34nCziEhlROIiSxWAMAKLEDhVQUP8LLSegkEMTRZLo81uyfTFaMxP8AMhaFqJANRDCiUjVhg2AC3goQKBQ-gmHmN08Gs0QJHoHp5hway9J8TQtE8vx3Joi03CYH07LCoyyFSNkUzTYReVmSDtS2BFNAAbiAA

Steps to Reproduce

  1. See reproduction link
  2. See reproduction link
  3. None

Current Behavior

When having a series with a time based x-axis, 'coord' mark points values are undefined. Using a type 'max' markPoint, the value is shown. Using a formatter with the 'coord' markPoint, {c} is shown as undefined.

Expected Behavior

The value of the 'coord' markPoint should be shown just like with the 'max' type markPoint

Environment

- OS:win 11
- Browser: chrome
- Framework: -

Any additional comments?

No response

helgasoft commented 1 month ago

yes, value is not set for format:'{c}' - it's a bug. workaround is to use formatter: x => {return x.data.coord[1];}