Open
Bug 162841
Opened 23 years ago
Updated 3 years ago
radio + + href will wrap
Categories
(Core :: Layout: Text and Fonts, defect, P3)
Tracking
()
NEW
Future
People
(Reporter: ryan.gustafson, Unassigned)
Details
(Keywords: intl, testcase)
Attachments
(1 file)
1.09 KB,
text/html
|
Details |
A radio followed by a followed by an href will wrap. However, a radio
followed by a followed by text will not. I'm attaching test case showing
the problem. Works fine in IE. In Mozilla 1.0 though, the top table (fixed
width) does a break, and the bottom table (not fixed width) will break if you
resize your browser window small enough.
Reporter | ||
Comment 1•23 years ago
|
||
Resize your browser smaller to get the 2nd table to show the problem.
I'm not reporting this as a bug, but looks like the text itself will draw
_outside_ the bounds of the table as well.
Problem confirmed 2002081504/winXP.
Reporter: Please ALWAYS tell us your BuildID. Also, it is highly recommended
to use Bugzilla Helper, not Advanced Entry form for reporting bugs.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Reporter | ||
Comment 3•23 years ago
|
||
Apologies, didn't realize I used the advanced, was wondering why it was not as
simple/friendly as the last time I submitted a bug.
Build ID is 2002052306, would be 1.0-pre3, I just realized.
Just downloaded 1.0-release, Build ID is 2002053012, verified to exist there as
well.
![]() |
||
Comment 4•23 years ago
|
||
To intl; this is a line-breaking problem.
Assignee: attinasi → yokoyama
Component: Layout → Internationalization
QA Contact: petersen → ruixu
Comment 7•23 years ago
|
||
I could not reproduce the problem. Would you mind try it on latest trunk build
and attach a screen shot. I will update my local tree and try again.
Is this anyway related to bug 122441 or bug 139723?
Comment 9•23 years ago
|
||
This bug looks like a regression. I could not reproduce the bug before, but I
could not. And it seems ok to me with Netscape7.0. As I looked into the
problem, I found that we did things differently with normal text run and
connecting frame text run.
I believe this bug reveals several problems. nsLineLayout::LineIsBreakable and
nsTextFrame::MeasureText are 2 of them.
Yuying, could you help figure out when do we began to have this regression?
Comment 10•23 years ago
|
||
This seeems not a regression for me, cause I don't see there is different
between N6.23 and N7.0.
However, there is a difference when set page encoding as Chinese (TC or SC) and
other encodings (western, Japanese, Korean...etc).
With Chinese encoding, there is no line wrap in 1st table while with other
encodings will get line wrapped.
Comment 11•23 years ago
|
||
thanks yuying for checking this for me.
Here is my guess of what's happenning:
When there is frame before the text frame, "mCanBreakBefore" is set to true.
This value is ignored for text measuring in same text frame when mX == 0. For
joining frames, mCanBreakBefore is observed and we break if the word is too
long. Clearly, there is a inconsistency here. The inconsistency is easy to fix,
but the bug reveals a more complicated problem. That is the text extruding
outside table cell boundary. The reason is we use maxWordWidth to computer the
width of table cell. This computation will not work if the longest word is not
breakable with a non-text frame, eg. radio buttion in the bug report. This is a
rather troublesome problem to handle.
change component to layout, this is not line-breaker problem.
Component: Internationalization → Layout
Comment 12•23 years ago
|
||
Really reassigning
Assignee: shanjian → attinasi
Status: ASSIGNED → NEW
QA Contact: ylong → petersen
Updated•23 years ago
|
Priority: -- → P3
Target Milestone: --- → Future
![]() |
||
Comment 13•22 years ago
|
||
.
Assignee: attinasi → font
Component: Layout → Layout: Fonts and Text
Priority: P3 → --
QA Contact: cpetersen0953 → ian
Target Milestone: Future → ---
Updated•22 years ago
|
Priority: -- → P3
Target Milestone: --- → Future
Updated•16 years ago
|
Assignee: layout.fonts-and-text → nobody
QA Contact: ian → layout.fonts-and-text
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•