| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| |
|
|
|
|
| |
file which can be viewed in an external tool. It provides a timelapse view of
how the flow tree and fragments changed during the layout process, which makes
it easier to debug layout bugs.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
The code that managed ranges was buggy - failing on edge cases
such as a span within a span. I have refactored the code so that the
context information for inline formatting can optionally be stored
within a fragment. This seems cleaner to me, and fixes the bugs
encountered when making these changes by removing the need for
the fixup() functionality (and ranges).
|
| | |
|
| |
|
|
| |
a hard-coded estimate.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
fns used by seq/parallel code paths).
- LayoutContext is renamed to SharedLayoutContext.
- SharedLayoutContext is immutable.
- LayoutContext is a wrapper around SharedLayoutContext + access to local caches (font, style etc).
- Creating a LayoutContext does a single local_data lookup to fetch the cache information.
- Android shares same implementation of context.rs as other platforms.
- LayoutContext can be used from both green thread (parallel layout) and native thread (sequential layout).
- Removes the need for other types (such as FontContext, StyleSharingCandidateCache etc) to be passed around.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
Whatever rustdoc bug we used to hit was solved by the Rust upgrade.
(The style crate still causes rustdoc to overflow its stack.)
Also use Markdown tables rather than ASCII diagrams in inlines.rs.
Not only does this look nicer, this works around rustdoc trying
(and failing) to parse them as Rust code.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
some layout issues related to #2554.
|
| |
|
