Closed
Bug 389666
Opened 18 years ago
Closed 17 years ago
Text wraps to second line when focusing link
Categories
(Core :: Layout, defect)
Core
Layout
Tracking
()
VERIFIED
FIXED
mozilla1.9beta1
People
(Reporter: martijn.martijn, Assigned: roc)
References
()
Details
(Keywords: regression, testcase, Whiteboard: [dbaron-1.9:RwCt])
Attachments
(4 files, 1 obsolete file)
206 bytes,
text/html
|
Details | |
10.14 KB,
patch
|
smontagu
:
review+
vlad
:
approval1.9+
|
Details | Diff | Splinter Review |
2.98 KB,
image/png
|
Details | |
3.55 KB,
image/png
|
Details |
See testcase, when focusing the first link, the word after the link wraps to the second line with current trunk build.
This regressed between 2007-06-20 and 2007-06-21, a regression from bug 367177.
Comment 1•18 years ago
|
||
Ah, that explains what I've been seeing at the bottom of the Bugzilla page too!
Assignee | ||
Updated•18 years ago
|
Flags: blocking1.9?
Assignee | ||
Updated•18 years ago
|
Assignee: nobody → roc
Flags: blocking1.9? → blocking1.9+
Assignee | ||
Comment 4•17 years ago
|
||
This is the fix. It's bit mixed up with the patch for bug 393096, so I'll wait for that one to land before I push this one.
The problem is that the mTransformedTextOffset field of the MappedFlows is not initialized when we scan, but do not need to recreate, an existing textrun, so setting up the line breaks in that textrun goes haywire. The fix here is to eliminate that field, we can use a gfxSkipCharsIterator to compute the offset of each MappedFlow in the textrun.
Assignee | ||
Updated•17 years ago
|
Whiteboard: [depends on 393096]
Whiteboard: [depends on 393096] → [depends on 393096][dbaron-1.9:RwCt]
Assignee | ||
Comment 5•17 years ago
|
||
This is the patch now that 393096 has landed.
Attachment #282251 -
Attachment is obsolete: true
Attachment #285576 -
Flags: review?(smontagu)
Assignee | ||
Updated•17 years ago
|
Whiteboard: [depends on 393096][dbaron-1.9:RwCt] → [needs review][dbaron-1.9:RwCt]
Updated•17 years ago
|
Attachment #285576 -
Flags: review?(smontagu) → review+
Assignee | ||
Comment 6•17 years ago
|
||
I'd like to get this into M9 now that we have a patch. It fixed layout regressions on real sites such as http://www.google.com/ig.
Target Milestone: --- → mozilla1.9 M9
Assignee | ||
Updated•17 years ago
|
Whiteboard: [needs review][dbaron-1.9:RwCt] → [dbaron-1.9:RwCt]
Assignee | ||
Updated•17 years ago
|
Whiteboard: [dbaron-1.9:RwCt] → [dbaron-1.9:RwCt][need landing]
Assignee | ||
Comment 7•17 years ago
|
||
going for new branch approval procedure
Target Milestone: mozilla1.9 M9 → ---
Assignee | ||
Updated•17 years ago
|
Attachment #285576 -
Flags: approval1.9?
Target Milestone: --- → mozilla1.9 M9
Comment on attachment 285576 [details] [diff] [review]
fix
Approved for M9, please land ASAP.
Attachment #285576 -
Flags: approval1.9? → approval1.9+
Assignee | ||
Comment 9•17 years ago
|
||
checked in
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Whiteboard: [dbaron-1.9:RwCt][need landing] → [dbaron-1.9:RwCt]
Assignee | ||
Comment 10•17 years ago
|
||
I checked in a reftest based on a test in bug 389468.
Flags: in-testsuite+
Comment 11•17 years ago
|
||
Using Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.9a9pre) Gecko/2007102504 Minefield/3.0a9pre and the testcase in the bug, I see slightly different layout between the branch and the trunk, at least on the Mac. Screenshots coming. Martijn mentions that the font sizes seem to be different between trunk and branch and that should be a separate bug.
Comment 12•17 years ago
|
||
Comment 13•17 years ago
|
||
Assignee | ||
Comment 14•17 years ago
|
||
The difference is probably just a slightly smaller font on trunk, so not significant.
Comment 15•17 years ago
|
||
verified fixed using Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a9pre) Gecko/2007102504 Minefield/3.0a9pre. Roc has addressed my concerns about the mac rendering in Comment 14.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•