Closed
Bug 785820
Opened 12 years ago
Closed 12 years ago
Global search match sometimes not visible when lines are too long
Categories
(DevTools :: Debugger, defect, P3)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 789027
People
(Reporter: Optimizer, Unassigned)
Details
Attachments
(1 file)
52.03 KB,
image/png
|
Details |
This happens when the searched text is at a column number high enough that it is not visible in the debugger as the area that displays the line containing the search result text displays the line containing the searched text starting from its origin.
Comment 1•12 years ago
|
||
Please provide detailed steps to reproduce what you're describing. Screenshot if necessary. Are you suggesting we *crop* long lines of source code?
Reporter | ||
Comment 2•12 years ago
|
||
In the attached screenshot, I am doing a free search for the text ja. The first line has that phrase 3 times, but not even one is visible, similarly for the next 3 lines. Only in the fourth line, the searched phrase is visible. I am not suggesting to crop the lines, instead, the first four lines should be aligned horizontally to show atleast one of the searched phrase occurrence, like the source editor does automatically.
Reporter | ||
Comment 3•12 years ago
|
||
only in the fifth line*
Reporter | ||
Comment 4•12 years ago
|
||
Please note that I am not talking about the lines shown in the editor (that is built using the source editor ), but the area which shows the results lines of free text. The feature that Victor made (and is awesome)
Comment 5•12 years ago
|
||
Reworded subject to something more understandable :)
Priority: -- → P3
Summary: The area that displays the line containing the search result text should crop the line to make the searched text visible for long lines. → Global search match sometimes not visible when lines are too long
Comment 6•12 years ago
|
||
Actually we have a dupe.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
Updated•6 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•