Bug 113947 - REGRESSION (r147373): Auto-sizing doesn't always respect minimum width changes
Summary: REGRESSION (r147373): Auto-sizing doesn't always respect minimum width changes
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Layout and Rendering (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Tim Horton
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2013-04-04 12:11 PDT by Tim Horton
Modified: 2013-04-04 14:14 PDT (History)
4 users (show)

See Also:


Attachments
patch (1.65 KB, patch)
2013-04-04 12:36 PDT, Tim Horton
andersca: review+
Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Tim Horton 2013-04-04 12:11:05 PDT
Now that we reset the size of the FrameView and do layout upon every autoSizeIfEnabled, we also need to reset our width to the minimum auto-size width. Previously we were resetting to the FrameView's current width, which is vaguely OK if we only reset it the first time we autosize, but breaks everything (makes minimum width changes not take effect unless the view is forcefully resized) if we reset it every time.
Comment 1 Radar WebKit Bug Importer 2013-04-04 12:11:45 PDT
<rdar://problem/13579024>
Comment 2 Tim Horton 2013-04-04 12:36:51 PDT
Created attachment 196505 [details]
patch
Comment 3 Tim Horton 2013-04-04 12:57:50 PDT
https://trac.webkit.org/r147664
Comment 4 Benjamin Poulain 2013-04-04 14:11:10 PDT
fast/layers/no-clipping-overflow-hidden-added-after-transition.html fails after this patch:

http://build.webkit.org/results/Apple%20MountainLion%20Debug%20WK1%20(Tests)/r147664%20(6940)/results.html

Can you please have a look?
Comment 5 Tim Horton 2013-04-04 14:14:58 PDT
(In reply to comment #4)
> fast/layers/no-clipping-overflow-hidden-added-after-transition.html fails after this patch:
> 
> http://build.webkit.org/results/Apple%20MountainLion%20Debug%20WK1%20(Tests)/r147664%20(6940)/results.html
> 
> Can you please have a look?

There's no way my change affected tests on Mac at all.