Closed
Bug 241626
Opened 21 years ago
Closed 19 years ago
{inc}changing font of parent of position:absolute div doesn't reposition child's text
Categories
(Core :: Layout: Positioned, defect)
Core
Layout: Positioned
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: jruderman, Unassigned)
Details
(Keywords: testcase)
Attachments
(1 file, 1 obsolete file)
735 bytes,
text/html
|
Details |
Reporter | ||
Comment 1•21 years ago
|
||
Steps to reproduce:
1. Load the testcase.
2. Bonk the button.
Result: all the text changes size, but each text node (?) stays in place.
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a) Gecko/20040423
Firefox/0.8.0+
Comment 2•21 years ago
|
||
So you need the <link>, or can you just set inline style?
Updated•21 years ago
|
OS: Windows XP → All
Hardware: PC → All
Reporter | ||
Comment 3•21 years ago
|
||
If you set the inline style (font-size: 80%) on the BODY element, you get the
bug. If you set the same inline style on the B element, you don't get the bug.
Attachment #146966 -
Attachment is obsolete: true
Comment 4•21 years ago
|
||
Interesting. This also works if I change the font of the <p> itself... It does
not work if I make the body relatively or absolutely positioned, so it's not a
"doesn't propagate reflow to out-of-flows" issue.
It looks like we're overoptimizing reflow of abs pos frames.
Resummarizing, since we're not changing the font of the child, in fact.
I can't shake the feeling that we have known bugs on this....
Component: Layout: Fonts and Text → Layout: R & A Pos
QA Contact: core.layout.fonts-and-text → core.layout.r-and-a-pos
Summary: changing font in child of position:absolute div doesn't reposition text → {inc}changing font of parent of position:absolute div doesn't reposition child's text
Whiteboard: DUPEME
Comment 5•19 years ago
|
||
WFM, SeaMonkey 2005-07-28-01 trunk Linux
Comment 6•19 years ago
|
||
Yeah, roc's changes to abs pos reflow stuff a while back probably fixed this.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•