Changeset 153781 in webkit


Ignore:
Timestamp:
Aug 7, 2013 2:11:04 AM (11 years ago)
Author:
mihnea@adobe.com
Message:

[CSSRegions] Wrong auto-height region computation for nested named flows
https://bugs.webkit.org/show_bug.cgi?id=119517

Reviewed by David Hyatt.

Source/WebCore:

Test: fast/regions/abspos-autoheight-nested-region.html

In the case of an (inner) auto-height region that is absolutely positioned in a named flow that is displayed in an (outer) auto-height region,
when we are doing the layout for the named flow we need to add a "forced region break" also for the case of simplified layout, otherwise
the outer auto-height region will not get the chance to compute its auto-height, ending up with a huge value that was used to initialize
the auto-height computed value before the start of the layout algorithm.

  • rendering/RenderBlock.cpp:

(WebCore::RenderBlock::simplifiedLayout):

LayoutTests:

  • fast/regions/abspos-autoheight-nested-region-expected.txt: Added.
  • fast/regions/abspos-autoheight-nested-region.html: Added.
Location:
trunk
Files:
2 added
3 edited

Legend:

Unmodified
Added
Removed
  • trunk/LayoutTests/ChangeLog

    r153780 r153781  
     12013-08-07  Mihnea Ovidenie  <mihnea@adobe.com>
     2
     3        [CSSRegions] Wrong auto-height region computation for nested named flows
     4        https://bugs.webkit.org/show_bug.cgi?id=119517
     5
     6        Reviewed by David Hyatt.
     7
     8        * fast/regions/abspos-autoheight-nested-region-expected.txt: Added.
     9        * fast/regions/abspos-autoheight-nested-region.html: Added.
     10
    1112013-08-07  Krzysztof Czech  <k.czech@samsung.com>
    212
  • trunk/Source/WebCore/ChangeLog

    r153775 r153781  
     12013-08-07  Mihnea Ovidenie  <mihnea@adobe.com>
     2
     3        [CSSRegions] Wrong auto-height region computation for nested named flows
     4        https://bugs.webkit.org/show_bug.cgi?id=119517
     5
     6        Reviewed by David Hyatt.
     7
     8        Test: fast/regions/abspos-autoheight-nested-region.html
     9
     10        In the case of an (inner) auto-height region that is absolutely positioned in a named flow that is displayed in an (outer) auto-height region,
     11        when we are doing the layout for the named flow we need to add a "forced region break" also for the case of simplified layout, otherwise
     12        the outer auto-height region will not get the chance to compute its auto-height, ending up with a huge value that was used to initialize
     13        the auto-height computed value before the start of the layout algorithm.
     14
     15        * rendering/RenderBlock.cpp:
     16        (WebCore::RenderBlock::simplifiedLayout):
     17
    1182013-08-06  Stephanie Lewis  <slewis@apple.com>
    219
  • trunk/Source/WebCore/rendering/RenderBlock.cpp

    r153688 r153781  
    27982798        simplifiedNormalFlowLayout();
    27992799
     2800    // Make sure a forced break is applied after the content if we are a flow thread in a simplified layout.
     2801    // This ensures the size information is correctly computed for the last auto-height region receiving content.
     2802    if (isRenderFlowThread())
     2803        toRenderFlowThread(this)->applyBreakAfterContent(clientLogicalBottom());
     2804
    28002805    // Lay out our positioned objects if our positioned child bit is set.
    28012806    // Also, if an absolute position element inside a relative positioned container moves, and the absolute element has a fixed position
Note: See TracChangeset for help on using the changeset viewer.