[Bug] - markline ignores zlevel of the series it belongs to
- Dominant language
- TypeScript
- Stars
- 67.3k
- Forks
- 19.8k
- Avg merge
- 11d 14h
- Merged PRs (30d)
- 8
Description
### Version
4.2.0
### Link to Minimal Reproduction
https://echarts.apache.org/examples/en/editor.html?code=PYBwLglsB2AEC8sDeAoWsAeBBDEDOAXMmurGAJ4gCmRA5AMYCGYVA5sAE7m0A0J6AE2aMiAbVoBZGL1i0AKgFcqM2gHUqAlXIAWClQDEOEFQGVmphdFoBdEgF8-6cjnxFUpMpRqyAbowA2SrT2jrB4VEZUhLCi_MQegsJiAIwArAAMPLAATADMmTnZACxZ2ckAHFnJualVRQDspQBs6dahHhTUdP4Q0MrtpABe_lQ-VP5EyXEOce4Jnd60PX28cejDo-NE2QPo9MD-nEQARBwax7uwQmAiMcn1tbD3j89VD28v708PbWuwALaMDgAawAMr1vHMEmFyP8AEYHIiZP7ofyMOFbeLQ0ggYB4CCQGB0PA3DhgVbY2AzSnLKgmCgjNwo0j7Q4cE5nAQXZnoBYnPAHCBcy4eADuQrA2km6WZ1Ox11usUp6ChyowdAqAFIZM5cNE0jLlVSRbBbNC7NMBqreV5uhCKQkNmMJrAALTJS6so6ycjjQ6ih0eBVibLZR6h8Nh0pRwqRuO_aGAkHgvpMyl4WEIl3ImnozHWhK4_GE6DE0nkk1y6G0-nkRlYyle9mwY6-_z-7lGvktgU9YU82DigSS6Wyk3BmIDgvQ9WyLU6lzRbLpQ3KqsJM0JC0ebemlB2ADcQA
### Steps to Reproduce
1. Set up a chart with 3 series
2. First series should be just data at the zlevel 1
3. Second series is data plus a markline at the zlevel 2 (can be any value higher than 1)
4. Third series is data plus a markline at the zlevel 0 (can be any value lower than 1)
### Current Behavior
The second and third series's data is correctly placed either above or below the first according to their zlevels. However as can be observed in the link to minimal reproduction both marklines get placed below the first series, thus ignoring the zlevel.
### Expected Behavior
The marklines should follow the behaviour of the data itself.
### Environment
```markdown
- OS: macOs Sonoma Version 14.2 (23C64)
- Browser: Google Chrome Version 125.0.6422.113 (Official Build) (arm64)
- Framework: Angular v7
```
### Any additional comments?
From what i was able to gather, all the canvas (corresponding to the different zlevels) are correctly placed however the markline is just drawn in the first layer regardless of zlevel.
Additionally, the link to the minimal reproduction is from echarts 5.5 however i'm having the same issue in my project using 4.2.
Contributor guide
Assessment
This issue has not been assessed yet.