Closed Bug 286192 Opened 20 years ago Closed 11 years ago

foxboro.com - Page layout is a complete mess

Categories

(Tech Evangelism Graveyard :: English US, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: kypont, Unassigned)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050223 Firefox/1.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050223 Firefox/1.0.1

Alignment is wrong on almost every part of the page.

Reproducible: Always

Steps to Reproduce:
1. Visit URL.
2. 
3.

Actual Results:  
Viewed page in disbelief
Conforming summary to TFM item 10 at 
http://www.mozilla.org/projects/tech-evangelism/site/procedures.html#file-new

Reporter, when you file a TE bug, please follow the reporting guidelines.

Subject page is invalid HTML http://tinyurl.com/5dwkl that renders in quirks
mode. I don't seem to see what problem you see.
Summary: Page layout is a complete mess. → foxboro.com - Page layout is a complete mess
I'm not sure what the heck this page is "supposed" to look like, but their CSS file is seriously FUBARed:

Warning: Expected identifier for class selector but found '.'.  Ruleset ignored due to bad selector.
Source File: http://www.foxboro.com/InvensysGlobal/CommonSiteElements/style/global.css
Line: 299

That's one of maybe 60 or 70 similar lines in the Error Console after visiting the page in Firefox 2. The page is similarly broken in Firefox, Camino, and Safari, so I'm assuming they just never tested it in anything besides IE. Confirming.

Someone should let them know their site is busted in all non-IE browsers.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows XP → All
Hardware: PC → All
Problem not found
Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en; rv:1.9.0.19) Gecko/2011032020 Camino/2.0.7 (like Firefox/3.0.19)
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
Product: Tech Evangelism → Tech Evangelism Graveyard
You need to log in before you can comment on or make changes to this bug.