etr2460 opened a new issue #9253: Cursor falls behind in SQL Lab
URL: https://github.com/apache/incubator-superset/issues/9253
 
 
   When typing in SQL Lab, the cursor slowly falls behind the characters.
   
   ### Expected results
   
   Typing to be normal
   
   ### Actual results
   
   ![cursor falls 
behind](https://user-images.githubusercontent.com/7409244/76133512-5360ab00-5fcd-11ea-90a6-c684b4086154.gif)
   
   #### Screenshots
   
   If applicable, add screenshots to help explain your problem.
   
   #### How to reproduce the bug
   
   Type a longish line in SQL Lab
   
   ### Environment
   
   (please complete the following information):
   
   - superset version: master
   - browser: latest Chrome
   
   ### Checklist
   
   Make sure these boxes are checked before submitting your issue - thank you!
   
   - [x] I have checked the superset logs for python stacktraces and included 
it here as text if there are any.
   - [x] I have reproduced the issue with at least the latest released version 
of superset.
   - [x] I have checked the issue tracker for the same issue and I haven't 
found one similar.
   
   ### Additional context
   
   I suspect this is related to the change that was made to fix cursor position 
in Safari. I then think the issue was exacerbated by the new font in SQL Lab. 
This seems likely as we saw a report from a user that the cursor was messed up 
in Chrome prior to rolling out the new fonts, but with the new font it's way 
more obvious and happens way more often
   
   cc: @rusackas @nytai 

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

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

Reply via email to