Bug 53515 - zeroing box-flex value after document load causes content to stay unexpectedly wide
Summary: zeroing box-flex value after document load causes content to stay unexpectedl...
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: CSS (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Nobody
URL:
Keywords: BrowserCompat, InRadar
Depends on:
Blocks:
 
Reported: 2011-02-01 11:51 PST by Andy Huang
Modified: 2023-10-28 16:29 PDT (History)
4 users (show)

See Also:


Attachments
CSS test case (1.57 KB, application/xhtml+xml)
2011-02-01 11:51 PST, Andy Huang
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Andy Huang 2011-02-01 11:51:31 PST
Created attachment 80798 [details]
CSS test case

tested on WebKit version: 534.17+

Setting an element's box-flex value to zero after a document has already loaded does not shrink the element to size as expected.  Instead, the element retains its former flexed size while neighboring elements are pushed beyond their parent container's bounds.

Having an element with an initial box-flex of zero does behave correctly, as does modifying an element's box-flex value immediately following document load.  The problem only manifests when JavaScript modifies the value some time after the document has loaded using an event handler.
Comment 1 Brent Fulgham 2022-07-12 14:17:56 PDT
Safari fails this test. Chrome and Firefox match.
Comment 2 Radar WebKit Bug Importer 2022-07-12 14:18:12 PDT
<rdar://problem/96909945>