Open
Bug 1327250
Opened 8 years ago
Updated 2 years ago
Event listeners tooltip teleports opened event listener to the end of visible area when I try to select text
Categories
(DevTools :: Inspector, defect, P3)
DevTools
Inspector
Tracking
(Not tracked)
REOPENED
People
(Reporter: arni2033, Unassigned)
References
()
Details
Attachments
(1 file)
|
(deleted),
video/webm
|
Details |
>>> My Info: Win7_64, Nightly 49, 32bit, ID 20160429030215 STR_1: 1. Open the following "data:" url (without ">" in the start) or click URL in the form above > data::,<script>for(i=0;++i<99;)addEventListener(i<49?'cut':'copy',_=>{%0A%0A%0A%0A%0A%0A})</script> 2. Open inspector, click (ev) button near <html> node to open event listeners tooltip 3. There're event listeners for one type of event in the beginning. Scroll the tooltip contents so that the first event listener for second type of event was displayed in the ~middle of visible area 4. Open that event listener, make sure its code area is scrollable, scroll it to the beginning 5. Select all text in code area with mouse: Place mouse pointer before the 1st character in code area, hold left mouse button, move mouse to the bottom side of the screen. AR: Event listener opened in the middle of visible area teleports to the end of visible area ER: Event listener opened in Step 4 should stay still Note: I know that it is codemirror bug, but I won't provide any exact information. Explanation: the author of codemirror doesn't care about quality at all, as he completely ignored bug 1257815 comment 19 explaining his long-standing fail. That's probably because he doesn't even know how that code works. So if you care about _quality_ as I do, please do not debug this anyhow, and let the author of codemirror read his code himself, figure out how it works and finally form a strong opinion about it.
Component: Developer Tools: Animation Inspector → Developer Tools: Inspector
|
||
Comment 1•8 years ago
|
||
If this is a codemirror bug, it should be filed on the codemirror repo. Also I was unable to reproduce this with Firefox 51. For complex STRs like these, a screencast would help a lot. I know they are very detailed, but it's hard to know whether the bug is fixed or whether you've just not clicked exactly where you should have. Closing for now.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
|
||
Comment 2•8 years ago
|
||
>>> My Info: Win7_64, Nightly 53, 32bit, ID 20170104030214 (2017-01-04)
Reproducible.
There's a way for browser to use CodeMirror in another way to avoid this bug. I think somebody
else than reporter should actually investigate what it is - more a CodeMirror bug or devtools bug.
(, but I saw that CodeMirror bugs reproducible in devtools are tracked here w/o major problems)
Expecting 1 person to be able to test 913 in the latest version and attach 913 new screencasts
is not reasonable, I must say.Flags: needinfo?(pbrosset)
|
|
||
Comment 3•8 years ago
|
||
Thanks for the video. I was able to reproduce with FF53.
Status: RESOLVED → REOPENED
Flags: needinfo?(pbrosset)
Priority: -- → P3
Resolution: WONTFIX → ---
|
|
||
Updated•8 years ago
|
|
||
Updated•6 years ago
|
Product: Firefox → DevTools
|
|
||
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•