Issue metadata
Sign in to add a comment
|
key press event in wysiwig editor are blocked for almost full minute before bound
Reported by
mdibb...@gmail.com,
Jun 6 2017
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36 Steps to reproduce the problem: 1. get octobercms. get a plugin with backend rich editor 2. try to select a line and delete. only one letter is removed on cursor position, not entire selection 3. select line, try to make italic. It only starts to work after roughly half a minute, minute. As if the javascript is delayed. Must be a chrome update, because is in firefox it works normal and I didn't change a thing. What is the expected behavior? loads, events get bound, select text, hit ctrl +i text becomes italic. What went wrong? chrome update Did this work before? Yes the one that was there last thursday Chrome version: 58.0.3029.110 Channel: n/a OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version:
,
Jun 7 2017
Thank you for providing more feedback. Adding requester "dtapuska@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 7 2017
Here is the trace
,
Jun 7 2017
There are no input events in this trace. Did you start tracing and then perform the action and then end tracing?
,
Jun 7 2017
Attached a new trace + a windows recording done with PSR which shows which keys I pressed. I repeated the same steps I did for as for the original recording. Hit CTRL + i, select, try to delete, etc.. stuff one does with a wysiwyg editor. Curious thing is, if I save it to desktop, it works immedeately as it should, but if I request it from webserver it refuses, without giving any errors, but intermittently starts working after x seconds, without me changing anything to that code, the loading mechanics, etc.., and it still works as it should in other browsers. It almost seems as if some network security policy is calling hiccups.
,
Jun 7 2017
I still don't see the input events in the log. What type of trace did you record. What about recording one with all the categories on? This sounds like the key events are sent to the network and then the response updates the UI model.
,
Jun 7 2017
Okay, I clicked on more and select all. I noticed that if I select all text, I can do ctrl + b and ctrl + i, but if I only select a part of the text it doesn't work. Has something changed how text selections are handled in chrome?
,
Jun 7 2017
So from the trace the latency of the keydown is about 15-39ms and the keyup is 4-5ms The request for a single network request seems to be around for: 1,284.138 ms to URI: http://eeboffice/eeb/app/exitcontrol/hotelmanager/hotelcontroller/update/10525 You probably want to grab a chrome://net-export/ log.
,
Jun 8 2017
That request takes only 1.2 sec, which is much shorter than 30sec. - Could you provide a NetLog? https://dev.chromium.org/for-testers/providing-network-details - Is there any public sites to reproduce the issue? - Can you tell me what "chrome update" means for "What went wrong"? Thanks!
,
Jul 11 2017
Feel free to reopen if you still have the issue. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by dtapu...@chromium.org
, Jun 6 2017