Closed Bug 198266 Opened 23 years ago Closed 23 years ago

Div contents do not fit and spill out

Categories

(Core :: Layout, defect)

defect
Not set
major

Tracking

()

RESOLVED INVALID

People

(Reporter: AstroDrabb, Unassigned)

References

()

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3) Gecko/20030312 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3) Gecko/20030312 See http://web.tampabay.rr.com/jdrabb/moz-1.3-div.html for details. Also, here is some simple HTML to illustrate: http://web.tampabay.rr.com/jdrabb/portal-8.4-moz-1.3.html Reproducible: Always Steps to Reproduce: 1. Got to URL's above 2. 3. Actual Results: Unreadable pages Expected Results: Mozilla should disreagard style attributes if the content does not fit as the other three main browsers do. User experience is more important then being the most standards compliant.
Actually, the site just needs to fix their broken CSS. There's no point in implementing CSS if we're going to do it wrong.
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → INVALID
I understand your point. However, that basically makes Mozilla sub-optimal as a browser. A huge majority of the sites out there turn out **** HTML/CSS using horrible tools like front page. While other browser are forgiving of this, Mozilla, is not. So Mozilla users are left out in the cold. A lot of corporations won't support Mozilla because of issues like this. The company I work for has 110,000+ employees and they will not support any employee using Mozilla. I have been pushing Mozilla, but when issues like this happens, I get shot down. Most people say things like "Well, it works in IE, so we won't support Mozilla". I can understand wanting to have full CSS 1/2 support, but at least give the user an option to turn off strict CSS. Otherwise, people are just going to look for other browsers.
James, IE is the _only_ browser that's "forgiving" of such CSS, and the only reason people author it is "because it works in IE". So our options are to make an IE clone (why bother?) or to implement the specification and send polite mail to authors of pages with such errors requesting that they fix them.
*** Bug 202259 has been marked as a duplicate of this bug. ***
You need to log in before you can comment on or make changes to this bug.