dante2
dante2 copied to clipboard
Tooltip takes a few milliseconds to appear
Try selecting some text and immediately press delete button. You'll see the glitch that it won't erase the selected text. In fact, the editor does not work before tooltip appears.
When you select text by keyboard (by pressing Shift+Arrow Keys), tooltip appears quickly and editor works without glitch.
But if you select by mouse, Dante2 makes you wait 900 milliseconds to see the tooltip first and only then act on the editor.
This is a serious issue. Needs a fix.
I guess there is some setTimeout()
function in codebase for tooltip to appear after selecting text.
Hi @KumarAbhirup , it's not clear to me how the issue is. Can you make a screen record on the issue to dig further?
thanks for report this!
could not replicate it http://g.recordit.co/vhpwQAj0Rx.gif
Hi @KumarAbhirup , it's supposed to work like that. when you select with mouse the tooptip will only appear when you release the mouse (mouseup)
here is a demo that demonstrate that on medium.com it's the same functionality http://recordit.co/LaRVjQJRXZ
Tooltip's late appearance is not at all a problem. But the text selected cannot be deleted before tooltip appears. It's a small glitch that seldom appears. But for super mouse users like me, I feel the bug everytime I try to delete some text by selecting it.
it seems that is a problem on https://draftjs.org/ core . could you try to replicate it in order to confirm that ?
thanks
On Sun, May 5, 2019 at 12:33 PM Kumar Abhirup [email protected] wrote:
Tooltip's late appearance is not at all a problem. But the text selected cannot be deleted before tooltip appears. It's a small glitch that seldom appears. But for super mouse users like me, I feel the bug everytime I try to delete some text by selecting it.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/michelson/dante2/issues/165#issuecomment-489442018, or mute the thread https://github.com/notifications/unsubscribe-auth/AAAC5SGPJBJCNFUPKWNN4ULPT4D7BANCNFSM4HK2IE4A .
Yes, I was able to reproduce the issue. If it's a draftjs issue, could we do something to fix this bug?