Closed
Bug 1279704
Opened 9 years ago
Closed 9 years ago
Highlighted word has an extra space after stylized characters
Categories
(Toolkit :: Find Toolbar, defect)
Tracking
()
VERIFIED
FIXED
| Tracking | Status | |
|---|---|---|
| firefox49 | --- | unaffected |
| firefox50 | --- | unaffected |
| firefox51 | --- | unaffected |
| firefox52 | --- | verified |
People
(Reporter: Fanolian+BMO, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: nightly-community, regression, testcase)
Attachments
(1 file)
|
374 bytes,
text/html
|
Details |
User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:50.0) Gecko/20100101 Firefox/50.0
Build ID: 20160611030214
Steps to reproduce:
1. Open attached testcase.
2. Search for "testcase" (without quote).
Actual results:
An extra space between T and C for the highlighted item.
There is no extra spaces if I manually add a space after stylized characters. (4th line, search for "test case")
p.s. Some highlighted words are stylized but stylized too much. See <b> or <code>.
Updated•9 years ago
|
Keywords: nightly-community
Comment 1•9 years ago
|
||
confirmed
Comment 2•9 years ago
|
||
[Tracking Requested - why for this release]: Regression
status-firefox49:
--- → unaffected
status-firefox50:
--- → affected
tracking-firefox50:
--- → ?
Keywords: regression
Comment 3•9 years ago
|
||
Feature has been backed out so not tracking these bugs for 50.
tracking-firefox50:
? → ---
Comment 4•9 years ago
|
||
Bulk update to find bar bugs that won't be in 50 (according to https://bugzilla.mozilla.org/show_bug.cgi?id=1279695#c4 and local testing).
Comment 5•9 years ago
|
||
Seems this is due to us drawing multiple boxes for the currently-found work, and those boxes pick up the default padding. When using multiple boxes we probably want to set left/right padding to 0.
Updated•9 years ago
|
Flags: qe-verify+
Flags: firefox-backlog+
Comment 8•9 years ago
|
||
Bug 1305033 is verified fixed. Should this bug be tested and closed?
Comment 9•9 years ago
|
||
I checked the attached (visual) test case and I agree it looks fixed.
Fanolian, please feel free to re-open if you feel otherwise!
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Updated•9 years ago
|
status-firefox51:
--- → unaffected
status-firefox52:
--- → fixed
Comment 10•9 years ago
|
||
I have reproduced this issue using Firefox 50.0a1 (2016.06.11) on Win 8.1 x64.
I can confirm this issue is fixed, I verified using Firefox 52.0b2 on Win 8.1 x64, Ubuntu 16.04 x64 and Mac OS X 10.11.
You need to log in
before you can comment on or make changes to this bug.
Description
•