Bug 9346

Summary:

Direction of html element does not affect position: fixed elements properly in Strict Mode

Product:

WebKit

Reporter:

Sam Weinig <sam>

Component:

CSS

Assignee:

Nobody <webkit-unassigned>

Status:

RESOLVED CONFIGURATION CHANGED

Severity:

Normal

CC:

ahmad.saleem792, ap, bfulgham, ian, mrowe, rniwa, simon.fraser, webkit

Priority:

Keywords:

HasReduction

Version:

420+

Hardware:

Mac

OS:

OS X 10.4

Attachments:

Description	Flags
test case in Strict mode	none
test case in Quirks mode	none

Sam Weinig

Reported 2006-06-07 15:14:54 PDT

I can't tell if the behavior is correct or not but I am posting the bug non-the-less.

Attachments
test case in Strict mode (320 bytes, text/html) 2006-06-07 15:15 PDT, Sam Weinig	no flags	Details
test case in Quirks mode (304 bytes, text/html) 2006-06-07 15:15 PDT, Sam Weinig	no flags	Details
View All Add attachment proposed patch, testcase, etc.

Sam Weinig

Comment 1 2006-06-07 15:15:28 PDT

Created attachment 8755 [details] test case in Strict mode

Sam Weinig

Comment 2 2006-06-07 15:15:52 PDT

Created attachment 8756 [details] test case in Quirks mode

Mark Rowe (bdash)

Comment 3 2006-07-02 07:36:59 PDT

I'm not sure if this is a bug either, but WebKit r15138 differs in behaviour from WebKit 418.8, Firefox 1.5.0.4 and Camino 1.0. The latter three render the box on the right side in both examples, while WebKit from ToT renders the strict mode box to the left side.

Robert Blaut

Comment 4 2008-02-11 14:21:22 PST

In my opinion it's a bug. Checked also in Gecko and Opera. Both browsers display the blue box on the right in strict mode.

Ahmad Saleem

Comment 5 2022-07-22 08:58:26 PDT

I am unable to reproduce this bug in Safari 15.6 on macOS 12.5 based on attached test cases (both) and get expected result of "blue" square / box being shown on right-side. It matches with other browsers (Chrome Canary 105 and Firefox Nightly 104) as well. I think it was fixed along the way and this can be marked as "RESOLVED CONFIGURATION CHANGED". Thanks!

Note You need to log in before you can comment on or make changes to this bug.