This repository has been archived by the owner on Jul 18, 2018. It is now read-only.
forked from ChromiumWebApps/chromium
-
Notifications
You must be signed in to change notification settings - Fork 8
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[LayoutNG] Implement atomic inlines for LayoutNGInline
This patch implements the initial support for atomic inlines in LayoutNGInline. Atomic inlines are the first type of objects in LayoutNGInline that needs be laid out to compute in-flow inline size. NGLineBuilder now keeps NGLayoutResult for atomic inlines while it builds a line box. Some tests turned from false-passes to real-failures. Because atomic inlines were not rendered before this patch, tests using images and inline-blocks passed by comparing blank result with blank reference. Some work are not included in this patch and will follow, such as: * Keep NGBlockNode for atomic inlines in NGLayoutInlineItem. * Use NGLayoutResult not only for layout but also for fragment generation. * Margin, padding, borders. * BreakToken if we support breaking atomic inlines[1]. * ...and obviously more. [1] w3c/csswg-drafts#1111 BUG=636993 Review-Url: https://codereview.chromium.org/2745973002 Cr-Commit-Position: refs/heads/master@{#457673}
- Loading branch information
Showing
7 changed files
with
171 additions
and
42 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.