Bug 134302

Summary: REGRESSION: Height of a single CSS region is not being respected
Product: WebKit Reporter: Jon Lee <jonlee>
Component: Layout and RenderingAssignee: Mihnea Ovidenie <mihnea>
Status: RESOLVED DUPLICATE    
Severity: Normal CC: abucur, dino, hyatt, stavila, stearns, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: 528+ (Nightly build)   
Hardware: All   
OS: Unspecified   
Attachments:
Description Flags
Test Case none

Jon Lee
Reported 2014-06-25 10:42:57 PDT
Height of a single CSS region is not being respected. Instead, it inherits the height of the named flow. This only occurs when one CSS region is defined for a particular named region, see attached test case. <rdar://problem/17428123>
Attachments
Test Case (1.22 KB, text/html)
2014-06-25 10:43 PDT, Jon Lee 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Jon Lee
Comment 1 2014-06-25 10:43:17 PDT
Created attachment 233824 [details] Test Case
Alan Stearns
Comment 2 2014-06-25 10:59:13 PDT
The region height is correct when I look at the test case. What you're seeing is overflow. try these to make it more apparent - set overflow: hidden - check the region height in the dev tools - add a border to the region
Andrei Bucur
Comment 3 2014-06-26 00:02:02 PDT
As Alan says, the test seems to behave correctly. Were you expecting the blur to apply ONLY to the region border box, without affecting the overflow? This doesn't seem to be the case for non-region boxes either.
Radu Stavila
Comment 4 2014-06-26 01:37:58 PDT
Hi Jon, I suppose you compared this to Safari 7 when you marked it as a regression. The reason you are seeing this difference between Safari 7 and the newest code in Nightly is because Safari 7 was not painting regions overflow, at all. This has been fixed some time ago in https://bugs.webkit.org/show_bug.cgi?id=118665. Please let me know if there is another problem that we are missing.
Jon Lee
Comment 5 2014-06-30 11:10:54 PDT
Thanks for the clarification. Closing as dupe. *** This bug has been marked as a duplicate of bug 118665 ***
Note You need to log in before you can comment on or make changes to this bug.