286882 - iframe explicit width overrides userContent.css "width: auto !important" and overprints the next column when fonts are larger

Status: RESOLVED WORKSFORME

(Core :: Layout, defect)

Description

[Silas S. Brown]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041217
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041217

The "Ads by Google" script found on many pages writes an IFRAME with an explicit
WIDTH.  I have very large fonts (as I am legally blind) so I set every element
to "width: auto !important" in my userContent.css (for my full css file see
http://www.cus.cam.ac.uk/~ssb22/source/lv-css.html ) - I do this because layouts
using explicit pixel WIDTHs are often corrupted when the font is very large. 
However, Mozilla does not honor my request to delete the explicit WIDTH in the
case of the IFRAME; instead, the IFRAME often overwrites the next table column,
making a large part of the text impossible to read.

Reproducible: Always

Steps to Reproduce:
1. Use a userContent.css file that specifies large fonts and width:auto !important
2. Load the above example (or one of many other pages) and observe how the "Ads
by Google iframe overwrites the text
Actual Results:  
Parts of the main text couldn't be read

Expected Results:  
It should have ignored the author's explicit WIDTH on the IFRAME and set the
width to "auto" (e.g. same as the table column's width).  Or if that's not
possible then it should not make the IFRAME overwrite the next column (give it a
horizontal scrollbar or something if necessary).

Comment 1

[Boris Zbarsky [:bzbarsky]]

Hmm..  On that page, with the following userContent.css:

* { width: auto !important; }
* { font-size: 2cm !important; }

I see the iframe at its auto width (300px).  The text _inside_ the iframe is not
so readable, but it doesn't overlap anything....  This is a current trunk Linux
build.

Comment 2

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 3

[Boris Zbarsky [:bzbarsky]]

This works fine for me.  Please reopen if it doesn't for you, and provide more details (like your exact userContent.css file).