prosdev0107 opened a new pull request, #20011:
URL: https://github.com/apache/superset/pull/20011

   ### SUMMARY
   [viz] heatmap Y axis labels rendering out-of-bounds
   
   **Description**
   Heatmap Y axis label rendering out-of-bounds, despite using `auto` for the 
`LEFT MARGIN` control.
   This issue is happened when the Y axis value is number type and in case of 
that Y axis value is string type, Y axis label is rendering correctly in 
bounds. So I fixed this issue by increasing the pixel value per char in case of 
number type.
   
   ### BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
   BEFORE:
   
   
https://user-images.githubusercontent.com/47900232/167644335-1400b0c2-a963-4978-a57a-f40c3eeca70e.mov
   
   AFTER:
   
   
https://user-images.githubusercontent.com/47900232/167642557-84d5f4c1-9d55-4ec9-b656-f484c317912f.mov
   
   
   ### TESTING INSTRUCTIONS
   <!--- Required! What steps can be taken to manually verify the changes? -->
   
   ### ADDITIONAL INFORMATION
   <!--- Check any relevant boxes with "x" -->
   <!--- HINT: Include "Fixes #nnn" if you are fixing an existing issue -->
   - [ ] Has associated issue:
   - [ ] Required feature flags:
   - [ ] Changes UI
   - [ ] Includes DB Migration (follow approval process in 
[SIP-59](https://github.com/apache/superset/issues/13351))
     - [ ] Migration is atomic, supports rollback & is backwards-compatible
     - [ ] Confirm DB migration upgrade and downgrade tested
     - [ ] Runtime estimates and downtime expectations provided
   - [ ] Introduces new feature or API
   - [ ] Removes existing feature or API
   


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to