Cursor should update position when console input is resized and caused lines to wrap
Categories
(DevTools :: Console, defect, P3)
Tracking
(firefox74 wontfix, firefox75 wontfix, firefox76 wontfix, firefox78 wontfix, firefox79 fixed)
People
(Reporter: cfogel, Assigned: nchevobbe, Mentored)
References
Details
(Keywords: regression)
Attachments
(1 file)
171.18 KB,
image/gif
|
Details |
Affected versions
- 75.0b4; 73.0b6, 76.0a1 (2020-03-15)
Affected platforms
- Windows 10, macOS 10.15, Ubuntu 18.04;
Steps to reproduce
- Launch Firefox, enable DevTools, select the Console tab;
- Type in the following expression:
` Spans with 'e': `+ Array.from(document.querySelectorAll("span")) .map(el => el.textContent) .filter(s => s.includes("e")) .join(" ")
- Ensure the mouse cursor is at the end of the string(can also click);
- Press CTRL+Shift+B(enable Multi-Line) mode;
- Repeat step 4;
Expected result
- cursor is at the last character in the input;
Actual result
- step 4: cursor is in the middle of the expression;
- step 5: cursor is 1 row bellow even tho there were no extra space_characters pasted;
Regression range
- will check if a regression and provide one asap;
Additional notes
- attached recording with the issue.
Updated•5 years ago
|
Comment 1•5 years ago
|
||
Regression range:
Last good: 2019-06-28
First bad: 2019-06-29
Pushlog: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=af62dfeb5c0eeb6e5bf5a8626f2556f3fa0d7cd2&tochange=938ba43a3350c4f81a5ed152b02eb92f9e68c949
Reporter | ||
Updated•5 years ago
|
Assignee | ||
Comment 2•5 years ago
|
||
The issue here is that the cursor position should be updated if the expression is wrapped.
We should call refresh()
on codeMirror when resizing the editor or switching between inline and editor mode.
Assignee | ||
Updated•5 years ago
|
Updated•5 years ago
|
Assignee | ||
Comment 4•5 years ago
|
||
sure, it's yours now :)
Updated•5 years ago
|
Updated•5 years ago
|
Comment 5•5 years ago
|
||
Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is P3
(Backlog,) indicating it has been triaged, the bug's Severity is being updated to S3
(normal.)
Assignee | ||
Updated•4 years ago
|
Assignee | ||
Comment 6•4 years ago
•
|
||
This was fixed by Bug 1624531
Updated•4 years ago
|
Reporter | ||
Comment 7•4 years ago
|
||
Quick check with 80.0a1 (2020-07-26), confirmed.
Description
•