Closed Bug 457055 Opened 16 years ago Closed 15 years ago

CSS Display issue

Categories

(Firefox :: General, defect)

x86
All
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: internetbusiness, Unassigned)

References

()

Details

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9) Gecko/2008061004 Firefox/3.0
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9) Gecko/2008061004 Firefox/3.0

The page is displayed improperly. It fails in Firefox, Safari, and Camino, but is displayed properly in Camino 9.4

Reproducible: Always

Steps to Reproduce:
1. Go to http://www.lorieslittlequilts.com/index.htm
2. scroll down to "SOFTouch™ hangers have a slot running the entire length..."
3. The pictures are placed incorrectly.
Actual Results:  
Fails in Firefox 3.0, Safari 3.1.2, and Camino 2007102517 (1.5.3), but each in a different way.

Expected Results:  
Displays properly in Opera 9.4

I have not looked at the source code to further isolate the issue, so I don't know if it's bad CSS in the source or not.
First off, when looking at that site, it was made with FrontPage, which has a habit of terrible markup. That makes it hard to pinpoint it to any one cause. Could you please make a testcase (http://developer.mozilla.org/en/Reducing_testcases) that shows that issue with all unnecessary info removed?

> The page is displayed improperly. It fails in Firefox, Safari, and Camino, but
> is displayed properly in Camino 9.4

I assume you meant Opera 9.4?

Another thing, make sure to update to Firefox 3.0.2. It has a few minor web site issues that are fixed, though I am not sure if they would apply. Worth checking though.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Mac OS X → All
Hardware: Macintosh → PC
Version: unspecified → Trunk
Tyler - I looked in the source code and see that the problem has something to do with <span> and position:relative. Some time back I reported a different problem regarding <span> and improperly positioned elements, which was a duplicate of several other issues. Why don't we just kill this bug report and wait til those others get resolved? When I start messing with the source code of this URL, the problem just moves all over the page and I can't boil it down to a decent "before" and "after" situation. Sorry, I guess I was a little too fast on the trigger.

Bill
Bill, what bug is it that you filed earlier?
We could mark as INCOMPLETE, but lets make sure it is not a dupe first.
(In reply to comment #3)
> Bill, what bug is it that you filed earlier?
> We could mark as INCOMPLETE, but lets make sure it is not a dupe first.

=> incomplete due to no response, but URL displays properly for me
bill, if you have addiitonal information please update the bug
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.