Closed Bug 240368 Opened 16 years ago Closed 6 years ago
Overflow properties doesn't work with object which are XUL documents
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7b) Gecko/20040411 Firefox/0.8.0+ Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7b) Gecko/20040411 Firefox/0.8.0+ When we embed a XUL document in a XHTML one, with the object tag, and when we try to specify differents values for the overflow property, it doesn't work. Reproducible: Always Steps to Reproduce: 1. Load the URL 2. Compare the first objects with XUL files and the last one with HTML file Actual Results: At first seen, it's like if all XUL objects where with overflow : hidden But sometimes, when you swith to another tab or another window and come back, the text of the XUL file is shown even outside the object. Expected Results: Scrollbars for the auto and scroll properties I think that this is a regression, because with Mozilla 1.6 and Firebird 0.7 the scrollbars existed. (I don't know if I should put this bug in XP toolkit : XUL)
The fact that 'overflow' on the OBJECT or IFRAME is applied to the HTML document is really a quirk. 'overflow' on the OBJECT element controls what happens if the child elements of the OBJECT overflow, but the OBJECT doesn't really have children. It's just "the document". You really need to control this using 'overflow' *inside* the XUL document.
hmm. I take it back. I don't know what's going on here.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Priority: -- → P2
Well, per CSS overflow applied to a replaced element means nothing, last I checked....
No, it applies to replaced elements. http://www.w3.org/TR/CSS21/visufx.html#propdef-overflow I think this testcase should work as Xanthor expects. I'm actually not sure how the XUL content escapes from the box in the first place...
Assignee: roc → nobody
Is this still an issue ?
The testcase has gone away.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WORKSFORME
Component: Layout: View Rendering → Layout: Web Painting
You need to log in before you can comment on or make changes to this bug.