Closed Bug 458558 Opened 16 years ago Closed 16 years ago

FUNDAMENTAL FLAW in page loading

Categories

(Firefox :: General, defect)

PowerPC
macOS
defect
Not set
critical

Tracking

()

RESOLVED DUPLICATE of bug 457459

People

(Reporter: anthony.clune, Unassigned)

References

()

Details

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-US; rv:1.9.0.3) Gecko/2008092414 Firefox/3.0.3
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-US; rv:1.9.0.3) Gecko/2008092414 Firefox/3.0.3

Previously reported as BUG 457459. The main "content" area is bumped to the bottom of the nav. bar - 

This site is set up simply and has function perfectly on virtually every other browser for over a year.

Over 45% of my site views come from this broken version of Firefox. Any and all help would be much appreciated.

I do not understand this firebug community, do people from Mozilla actually fix these things?

Who can I contact to get this problem on the map.

Should I consider legal action? This is costing me money by the day.

Reproducible: Always

Steps to Reproduce:
1. Visit http://tonkydesigns.com/wallstickers/index.html
2. Scroll down and observe that the main content area appears below nav bar
3. See disgusting white void this leaves

Actual Results:  
What happened is that I continue to be baffled and my blood is starting to approach boiling temperature.

Why should I have to reverse engineer my website because of Mozilla's irresponsible premature release?

HELP!

Expected Results:  
The software should have loaded the page correctly. Simple tables
We use Bugzilla to make our product better and you get no support here.
Please don't report bugs again and please read https://bugzilla.mozilla.org/page.cgi?id=etiquette.html
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
I know that you are frustrated but that doesn't help
Most people working in their free time on Mozilla and fixing such a bug takes time and a rendering error on some rare pages is not always high priority.
You need to log in before you can comment on or make changes to this bug.