Bug 195417

Summary: [ContentChangeObserver] Check if max-height change triggers visible content change.
Product: WebKit Reporter: zalan <zalan>
Component: Layout and RenderingAssignee: zalan <zalan>
Status: RESOLVED FIXED    
Severity: Normal CC: bfulgham, commit-queue, simon.fraser, webkit-bug-importer, zalan
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Patch
none
Patch none

zalan
Reported 2019-03-07 10:37:28 PST
going from fixed max-height: 0px; to max-height: non-zero
Attachments
Patch (8.93 KB, patch)
2019-03-07 10:45 PST, zalan 		no flags
DetailsFormatted DiffDiff
Patch (9.07 KB, patch)
2019-03-07 21:22 PST, zalan 		no flags
DetailsFormatted DiffDiff
Show Obsolete (1) View All Add attachment proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1 2019-03-07 10:40:58 PST
<rdar://problem/48680631>
zalan
Comment 2 2019-03-07 10:45:24 PST
Created attachment 363897 [details] Patch
Simon Fraser (smfr)
Comment 3 2019-03-07 11:40:43 PST
Comment on attachment 363897 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=363897&action=review > Source/WebCore/page/ios/ContentChangeObserver.cpp:299 > if (left.isFixed() && width.isFixed() && -left.value() >= width.value()) This is stupid and you should add a comment to explain how stupid it is. > Source/WebCore/page/ios/ContentChangeObserver.cpp:305 > + auto maxHeight = style.maxHeight(); Maybe comment to say that height + overflow:hidden should also be checked at some point.
zalan
Comment 4 2019-03-07 21:22:38 PST
Created attachment 363985 [details] Patch
WebKit Commit Bot
Comment 5 2019-03-07 22:09:04 PST
Comment on attachment 363985 [details] Patch Clearing flags on attachment: 363985 Committed r242634: <https://trac.webkit.org/changeset/242634>
WebKit Commit Bot
Comment 6 2019-03-07 22:09:06 PST
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.