This doesn't really have observable behavior right now, as much as I
tried to trigger some kind of bug. On the other hand, it's just wrong
and is very obvious when you dump the Fragment tree. If you create a
`display: table-cell` that is a child of the `<body>` all parts of the
anonymous table are flagged as if they are the `<body>` element.
These tests don't seem to time out any longer and this mechanism is
probably better served by some sort of adjustment to `RUST_LOG` in the
WPT harness.
* fixed typo in PositioningContext
Signed-off-by: Wepngong Maureen <maureenwepngong@gmail.com>
* fixed unresolved link to unresolved link to adjust_static_position_of_hoisted_fragments function
Signed-off-by: Wepngong Maureen <maureenwepngong@gmail.com>
* fixed unresolved link to unresolved link to len() function of PositioningContext
Signed-off-by: Wepngong Maureen <maureenwepngong@gmail.com>
---------
Signed-off-by: Wepngong Maureen <maureenwepngong@gmail.com>
* fixed a typo in the Android setup command
* Fix typo in documentation for command-line arguments
* Fix style and formatting issues in the Shell Scripts section of the documentation
* Update style.md
* Fixed various inconsistencies
* Fixed various inconsistencies
* Update webxr.md
* Update style.md
* Update COMMAND_LINE_ARGS.md
* Update README.md
Co-authored-by: Martin Robinson <mrobinson@igalia.com>
* Update docs/COMMAND_LINE_ARGS.md
---------
Co-authored-by: Martin Robinson <mrobinson@igalia.com>
* Fixed error in documentation in components>shared>embedder>lib.rs
* fixed documentation warning in compoenents>shared>net>request.rs
* Fixed the documentation (URL issue) in components>shared>script>lib.rs
Anonymous tables should not use legacy pseudos, as the legacy layout
engine had them inherit lots of random properites that lead to bad
layout in the new layout engine.
Co-authored-by: Oriol Brufau <obrufau@igalia.com>
* clippy: fix warnings in components/gfx
* refactor: switched the order of impl so that its intent is clearer
* fix: add font context default in other platforms
When exiting after load or dumping a screenshot, limit the speed that
the compositor sends tick events to the constellation (and on to the
script thread). Previously, these tick messages were sent as fast as the
winit event loop (that's really fast!), until the document was ready to
for its screenshot. rAf is meant to run at more or less the same
frequency as the refresh rate of the screen.
On my system, the massive amount of ticks was overwhelming the router
thread, preventing fonts from loading properly. This change is an attempt
to make tests with requestAnimationFrame less flaky.
* compositor: Improve the way we wait for frames
In the newest version of WebRender it will be harder to make the
distinction between frame queued for scrolling and other kinds of
pending frames. This change makes it so that we queue frames for both
kinds of changes the same way and keeps a counting of pending frames.
This is conceptually a lot simpler.
In addition, do queue a composite even when recomposite isn't necessary
for a WebRender frame when there are active requestAnimationFrame
callbacks. Doing a composite is what triggers the callbacks to actually
run in the script thread! I believe this was a bug, but the WebRender
upgrade made it much more obvious.
These changes are in preparation for the WebRender upgrade.
* Remove spurious println
* Add basic support for enumerating computed styles
The old code was so broken, it was enumerating the style attribute
instead of the computed styles.
So this patch implements a basic enumeration, but not including custom
properties whose computed value is not the guaranteed-invalid value.
* Feedback
