Open Bug 428533 Opened 16 years ago Updated 2 years ago

xul:iframe/browser/editor@type handling should happen in content, not in layout

Categories

(Core :: XUL, defect)

x86
Linux
defect

Tracking

()

People

(Reporter: smaug, Unassigned)

References

Details

Sorry for not finding/thinking this when fixing bug 395609.
I think this should block since anyone using <browser> with
some 'hidden' and 'type' attributes may easily start getting strange
behavior.
Flags: blocking1.9?
Flags: blocking1.9? → blocking1.9+
Hang on, are we just talking about the code in nsSubDocumentFrame::AttributeChanged for handling dynamic changes to the "type" attribute? If we are, then I don't think this should block ... since all it means is that dynamic changes to the "type" attribute of display:none XUL frames won't be noticed, right? I would hope that dynamic changes to "type" are actually very rare...
Flags: blocking1.9+ → blocking1.9?
(In reply to comment #1)
>I would hope that dynamic changes to "type" are actually very rare...
Happens every time a tab is switched. (Though in that case <browser> is visible.)
 

OK, well I still hope that dynamic changes to "type" on display:none XUL frames are rare :-), so I'd rather not block.
Flags: blocking1.9? → blocking1.9-
Component: XP Toolkit/Widgets: XUL → XUL
QA Contact: xptoolkit.xul → xptoolkit.widgets
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.