[GitHub] [echarts] jiawulin001 commented on issue #16992: [Bug] the second log Y axis affects the first log

[GitBox <gi...@apache.org>]

jiawulin001 commented on issue #16992:
URL: https://github.com/apache/echarts/issues/16992#issuecomment-1129657338

   ### Problem locating
   This problem exist here:
   https://github.com/apache/echarts/blob/5cf53e24ac751650ce8d76dde957f1b0d0bd50e6/src/scale/Log.ts#L74-L76
   When Echarts tries to obtain the extent of data and set ticks, it's trying to use the precision of `originalExtent` to fix `powVal`. This behavior is to fix the problem of #4158, where precision issue is caused by logarithm and exponentiation. However here `powVal` can be user-set min/max, which is 0.01 here and `originalExtent` is the real extent of data, which is 44 here. When using the precision of 44 to fix 0.01, tick value becomes 0 and it has nowhere to go on log axis. That's the reason why there's a big 0 up there.
   
   ### Plan to fix
   The way to fix #4158 is not fixing it completely (a user-set max of 2000000000000 still displays wrongly) and it also causes #16992. My plan is to change the way to fix #4158 and can fix #16992 in the same time.
   
   **Submitting a PR to solve this**


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@echarts.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@echarts.apache.org
For additional commands, e-mail: commits-help@echarts.apache.org