Bug 7095

Summary:

Removing positioning from an element does not relayout properly

Product:

WebKit

Reporter:

Maciej Stachowiak <mjs>

Component:

Layout and Rendering

Assignee:

Nobody <webkit-unassigned>

Status:

RESOLVED FIXED

Severity:

Normal

CC:

hyatt, mitz

Priority:

Version:

420+

Hardware:

Mac

OS:

OS X 10.4

Bug Depends on:

Bug Blocks:

9610

Attachments:

Description	Flags
test case	none
Proposed patch	hyatt: review+

Maciej Stachowiak

Reported 2006-02-05 19:50:10 PST

Sometimes, removing positioning from an element after layout fails to update properly. In the attached test case, the red box inside the yellow one is initially positioned but the positioning is removed. However it does not reset to its normal position until you resize the window.

Attachments
test case (647 bytes, text/html) 2006-02-05 19:50 PST, Maciej Stachowiak	no flags	Details
Proposed patch (6.29 KB, patch) 2006-02-06 08:08 PST, mitz	hyatt: review+	Details Formatted Diff Diff
View All Add attachment proposed patch, testcase, etc.

Maciej Stachowiak

Comment 1 2006-02-05 19:50:41 PST

Created attachment 6277 [details] test case

mitz

Comment 2 2006-02-06 07:56:40 PST

I'm going to attach a patch.

mitz

Comment 3 2006-02-06 08:08:38 PST

Created attachment 6289 [details] Proposed patch

Dave Hyatt

Comment 4 2006-02-06 13:15:17 PST

Comment on attachment 6289 [details] Proposed patch r=me

Timothy Hatcher

Comment 5 2006-02-08 21:14:06 PST

Darin landed this in r12682.

David Kilzer (:ddkilzer)

Comment 6 2006-12-23 04:17:17 PST

This is a Quirksmode bug: Element retains position: absolute after class change Reported on 3 October 2006 http://www.quirksmode.org/bugreports/archives/2006/10/Parent_Element_Sticky_Position.html When changing a parent element's class via JavaScript/DOM, an initial position:absolute declaration sticks. The problem is corrected by applying a position:relative declaration to the parent element's children. Test page: http://indorgs.virginia.edu/betech/bugs/safari-stickyposition.html

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