New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Layout `position: fixed` in the initial containing block #25273
Merged
+549
−401
Merged
Changes from 1 commit
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
b43a3de
Introduce PositioningContext
SimonSapin 9edda95
Make adjust_static_positions a method of PositioningContext
SimonSapin 1c8d14a
Upgrade rayon_croissant to 0.2.0
SimonSapin c44ee51
Give `PositioningContext` more responsibilities
SimonSapin 5ebddf1
Layout `position: fixed` in the initial containing block
SimonSapin 53a8a60
Fix a width v.s. height confusion bug in abspos layout
SimonSapin 6fce97c
Parse `background: <color>`
SimonSapin c0962aa
Replace the closure in `layout_in_flow_non_replaced_block_level` with…
SimonSapin 672d971
Regroup branches specific to `SameFormattingContextBlock`
SimonSapin 04b701b
Move call to `for_maybe_position_relative` out of `layout_in_flow_non…
SimonSapin b218957
Rename `CollectedAbsolutelyPositionedBox` to `HoistedAbsolutelyPositi…
SimonSapin 58b7005
Make `for_maybe_position_relative` take care of relative adjustment.
SimonSapin 6f3c5ce
Rename `BlockLevelKind` to `NonReplacedContents`
SimonSapin File filter...
Filter file types
Jump to…
Jump to file
Failed to load files.
Give `PositioningContext` more responsibilities
Iits details are now private to the module. It has a couple methods that take closures to make sure that "before" and "after" steps are done together: * In an absolutely positioned box, take care of nested abspos (establish a new containing block, etc.) * For a box that *might* be `position: relative`, optionally take care of the same.
- Loading branch information
commit c44ee516a10fca4d4d715337cc5c61c10bca1a44
Oops, something went wrong.
ProTip!
Use n and p to navigate between commits in a pull request.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
I understand the logic but I'm not sure I like how big this closure is and how it drifts everything even more to the right. Do you think it could be its own function, living in the module next to this one?