Long wrapping lines in devtools console cause autocomplete popup to be misplaced.

NEW
Unassigned

Status

defect
P2
normal
5 years ago
6 months ago

People

(Reporter: bugs, Unassigned)

Tracking

(Blocks 1 bug)

Trunk
x86_64
Linux
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [btpp-fix-later])

Attachments

(2 attachments)

Reporter

Description

5 years ago
Encountered when trying to create a bookmarklet for a friend.  The grey suggest text overlapped my typing, and the suggestion popup was positioned to the far right of my fullscreened browser.

When I made a non-fullscreen browser for purpose of screenshotting and testing this, the suggestions were positioned way outside the browser window even.  I'll attach a screenshot of this.
Reporter

Comment 1

5 years ago
Posted image Screenshot of bug
Duplicate of this bug: 1101887
Duplicate of this bug: 1234085
This should be fixed by Bug 983473
Depends on: 983473
Priority: -- → P2
Whiteboard: [btpp-fix-later]
Copying STR from Bug 1101887

1. Open Nightly
2. Resize the browser window so the width takes half of the screen, position the browser window to the left of your screen.
3. Open Tools -> Web Developer -> Web Console  
4. Type the following example JS: var xpathResult = document.evaluate( 'body/div/div/div/div/div/div/div/div/div/div/div/div/div/div/div/div/div/div/div', document, null, XPathResult.ANY_TYPE,  );

(the xpath selector here may be ridicilous, the point is to have the command line multi lined. Add /div if needed).

5. In the last evaluate() argument, start typing eg. document (so the autocomplete popup shows)

Updated

Last year
Product: Firefox → DevTools
The completion text issue seems fixed on Nightly (with CodeMirror Jsterm enabled), but the positioning issue for the autocomplete popup remains.
Summary: Long wrapping lines in devtools console cause autocomplete to overlap text, and suggest to be misplaced. → Long wrapping lines in devtools console cause autocomplete popup to be misplaced.
You need to log in before you can comment on or make changes to this bug.