Open
Bug 375180
Opened 18 years ago
Updated 2 years ago
Odd sizing behavior for html tags in XUL with outlines
Categories
(Core :: Layout, defect)
Tracking
()
NEW
People
(Reporter: sharparrow1, Unassigned)
Details
(Keywords: testcase)
Attachments
(3 files)
362 bytes,
application/vnd.mozilla.xul+xml
|
Details | |
3.87 KB,
patch
|
Details | Diff | Splinter Review | |
468 bytes,
patch
|
Details | Diff | Splinter Review |
Per description; testcase+patch coming up.
Reporter | ||
Comment 1•18 years ago
|
||
I'm not sure what this chunk of code was intended to do; probably a workaround for some bug in XUL overflow support. (I can't say for sure since the code has been there since version 1.1 of nsBoxToBlockAdaptor.cpp.) It seems completely bogus, though, and XUL can deal with overflow in the current codebase.
Attachment #259501 -
Flags: review?(roc)
Reporter | ||
Comment 2•18 years ago
|
||
(Of course, the first bit is from Bug 372037, and isn't relevant.)
This changes behavior of HTML-in-XUL in quite a big way. How can we be sure that this won't break XUL users?
Reporter | ||
Comment 4•18 years ago
|
||
(In reply to comment #3)
> This changes behavior of HTML-in-XUL in quite a big way. How can we be sure
> that this won't break XUL users?
Excluding form controls, HTML-in-XUL isn't very common, and hopefully overflowing HTML-in-XUL is very rare. The only case I can imagine content depending upon would be positioned children forcing the parent to resize.
If you think this is too risky, though, we can put it off to Gecko 2.0.
Yeah, I think we should put this on ice for now.
Reporter | ||
Comment 6•18 years ago
|
||
Comment on attachment 259501 [details] [diff] [review]
Patch
Okay then; iced until 1.9 branches.
Attachment #259501 -
Flags: review?(roc)
Comment 7•17 years ago
|
||
Removing the overflow code completely causes blocks in boxes to be sized incorrectly in some cases. Does this following testcase work?
Comment 8•3 years ago
|
||
The bug assignee didn't login in Bugzilla in the last 7 months, so the assignee is being reset.
Assignee: sharparrow1 → nobody
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•