| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
I used this to trace #11818 to a style bug, rather than a layout bug.
|
| |
|
| |
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
stylo: Allow computing change hints during the traversal.
<!-- Please describe your changes on the following line: -->
---
<!-- Thank you for contributing to Servo! Please replace each `[ ]` by `[X]` when the step is complete, and replace `__` with appropriate data: -->
- [x] `./mach build -d` does not report any errors
- [x] `./mach test-tidy` does not report any errors
<!-- Either: -->
- [x] These changes do not require tests because geckolib :-(
<!-- Pull requests that do not address these steps are welcome, but they will require additional verification as part of the review process. -->
r? @bholley
cc @heycam
<!-- Reviewable:start -->
---
This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/servo/12645)
<!-- Reviewable:end -->
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In the Gecko case, this style source would be the style context. In the servo
case, it will be always the computed values.
We could optimise this further in the case of stylo (from three FFI calls to
one) if we use an API of the form CalcAndStore(node, new_cv). But that would
imply borrowing the data twice from Servo (we also have borrow_data_unchecked
fwiw, but...).
|
|/ |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
snapshots, and use it for Gecko.
This is a rewrite for how style interfaces with its consumers in order to allow
different representations for an element snapshot.
This also changes the requirements of an element snapshot, requiring them to
only implement MatchAttr, instead of MatchAttrGeneric. This is important for
stylo since implementing MatchAttrGeneric is way more difficult for us given the
atom limitations. This also allows for more performant implementations in the
Gecko side of things.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Same reasons as the previous patch.
|
|
|
|
|
| |
If this is all the information the caller needs, we can get it from gecko without
worrying about atomization and string conversions.
|
|
|
|
| |
This should just be a helper.
|
| |
|
| |
|
|
|
|
|
| |
This allows removing `#![feature(as_unsafe_cell)]` in geckolib
and make progress towards #11815.
|
| |
|
| |
|
|
|