aboutsummaryrefslogtreecommitdiffstats
path: root/components/layout/construct.rs
Commit message (Collapse)AuthorAgeFilesLines
* Update rustc to 00b112c45a604fa6f4b59af2a40c9deeadfdb7c6/rustc-1.0.0-dev.Josh Matthews2015-01-281-5/+5
|
* Stop calling deref() and deref_mut() explicitly.Ms2ger2015-01-221-5/+5
|
* Use std::sync::atomic::Ordering explicitly.Ms2ger2015-01-221-2/+2
|
* Move to to_owned rather than into_string.Ms2ger2015-01-201-3/+4
| | | | into_string has been removed from Rust.
* CanvasRenderTask connected to LayoutEdit Balint2015-01-091-1/+6
| | | | Update rust-azure to f4a02f3f621b0a994a20d42e438371a87c62f898.
* Update rustc to revision 2cfb5acb5a2751c759627377e602bac4f88f2d19.Ms2ger2015-01-081-29/+33
|
* layout: Explicitly thread border box dimensions and relative offsetsPatrick Walton2015-01-041-21/+42
| | | | | | | | | | through display list building. The old `flow_origin` concept was ill-defined (sometimes the border box plus the flow origin, sometimes including horizontal margins and sometimes not, sometimes including relative position and sometimes not), leading to brittleness and test failures. This commit reworks the logic to always pass border box origins in during display list building.
* Fix inheritance enums for htmlmediaelement and htmltablecellelementMegha Gupta2015-01-021-3/+2
|
* Add HTMLElementTypeId enum (fixes #3625)Megha Gupta2015-01-021-14/+15
|
* layout: to_string() -> into_string()Manish Goregaokar2014-12-271-3/+3
|
* layout: Implement `caption-side` per CSS 2.1 § 17.4.1.Patrick Walton2014-12-171-15/+30
| | | | `caption-side` is used by 4% of pages by number of loads.
* layout: Implement `empty-cells` per CSS 2.1 § 17.6.1.1.Patrick Walton2014-12-171-4/+15
|
* Update rustc to revision 3dcd2157403163789aaf21a9ab3c4d30a7c6494d.Ms2ger2014-12-171-139/+131
|
* layout: Implement basic lists and the CSS1 list properties.Patrick Walton2014-12-151-28/+107
| | | | | | | | | | The exact rendering is ill-spec'd. Some things are ugly (especially the width and height of list style images) but they are infrequently used and I believe this implementation matches the spec. Numeric lists are not supported yet, since they will require a separate layout pass. The implementation is a subclass of `BlockFlow`, on advice from Robert O'Callahan.
* Updates WPT to expect newly passing testsMatthew Rasmus2014-12-051-2/+1
| | | | | | Addresses reviews More review addressing
* Implements multi line text input for TextAreaMatthew Rasmus2014-12-051-2/+13
|
* Don't categorize HTMLInputElement as a TableCellFragmentCorey Richardson2014-12-031-1/+0
| | | | Closes #4196.
* Remove bitfield! macro in favour of bitflags!Claes 'Letharion' Gyllensvärd2014-11-181-2/+3
|
* Rust upgrade to rustc hash b03a2755193cd756583bcf5831cf4545d75ecb8aJack Moffitt2014-11-131-24/+24
|
* Remove InputFragmentCameron Zwarich2014-11-031-4/+2
| | | | Fixes #3724.
* layout: Make incremental reflow more fine-grained by introducing "reflowPatrick Walton2014-10-311-2/+41
| | | | | | out-of-flow" and "reconstruct flow" damage bits. This is needed for good performance on the maze solver.
* layout: Promote absolute positioning, floatedness, and clearance intoPatrick Walton2014-10-281-5/+4
| | | | | | flags to avoid virtual calls. These were showing up really high in the maze solver profile.
* auto merge of #3841 : pcwalton/servo/removing-whitespace-damage, r=cgaebelbors-servo2014-10-281-18/+6
|\ | | | | | | | | | | | | | | Avoids total reflow of the entire document on the maze solver. I have tested Wikipedia reflow and it still works. r? @cgaebel
| * layout: Stop adding damage when removing whitespace.Patrick Walton2014-10-281-18/+6
| | | | | | | | Avoids total reflow of the entire document on the maze solver.
* | auto merge of #3840 : pcwalton/servo/ib-splits-linked-list, r=glennwbors-servo2014-10-281-5/+5
|\ \ | | | | | | | | | r? @glennw
| * | layout: Put {ib} splits into a linked list so we stop copying them allPatrick Walton2014-10-281-5/+5
| |/ | | | | | | the time.
* / layout: Make some formatting cleanups.Patrick Walton2014-10-281-6/+6
|/ | | | These should have no effect on functionality.
* layout: Shrink fragments down from 448 bytes down to 128 bytes.Patrick Walton2014-10-231-7/+7
| | | | 16% performance improvement in layout (!)
* layout: Rewrite text and inline fragment handling during flowPatrick Walton2014-10-201-45/+93
| | | | | | | construction to avoid cloning and moving flows so much. Besides amounting to a 5%-10% win on a page with a lot of text, this simplifies and refactors the text layout code.
* Fixes the table_percentage_width_a.html reftest with incremental reflow ↵Clark Gaebel2014-10-201-9/+3
| | | | turned on.
* Use opts as a global, to avoid cloning and passing the struct all over the code.Glenn Watson2014-10-201-18/+19
|
* Fix image_dynamic_remove reftest with incremental layout turned outClark Gaebel2014-10-171-7/+13
| | | | | | | | This also adds some extra debugging infrastructure which I found useful tracking this bug down. A regression in the br reftests is also uncovered by this patch, which I'll work on fixing next. r? @pcwalton
* Fix whitespace_pre with incremental reflow turned on.Clark Gaebel2014-10-151-6/+14
| | | | | | This implements fragment merging, in order to incrementally reflow linebroken text. This makes the `whitespace_pre.html` reftest pass with incremental reflow turned on with `-i`.
* Use the Deref traits for FlowRefs.Clark Gaebel2014-10-151-18/+16
| | | | | This patch switches FlowRefs to using the Deref and DerefMut traits, instead of the custom `get` and `get_mut` functions.
* auto merge of #3640 : cgaebel/servo/incremental-flow-construction, r=pcwaltonbors-servo2014-10-141-41/+47
|\ | | | | | | | | | | This also hides the not-yet-working parts of incremental reflow behind a runtime flag. As I get the failing reftests passing, I'll send pull requests for them one by one.
| * try to reset flows which need reflow, since reflow isn't yet idempotentClark Gaebel2014-10-141-41/+47
| |
* | layout: Rewrite intrinsic inline-size and automatic table layout toPatrick Walton2014-10-141-2/+2
| | | | | | | | | | | | | | | | | | | | | | match L. David Baron's work-in-progress specification. http://dbaron.org/css/intrinsic/ Column spans are not yet supported. This effectively adds support for percentage widths, and it also fixes many bugs, improving the layout of Google and Wikipedia.
* | layout: Introduce support for legacy presentational attributes to selectorPatrick Walton2014-10-141-21/+5
| | | | | | | | | | | | | | | | matching, and use it for `<input size>` and `<td width>`. This implements a general framework for legacy presentational attributes to the DOM and style calculation, so that adding more of them later will be straightforward.
* | script: Use atom comparison in more places, especially for attributes.Patrick Walton2014-10-141-2/+2
|/ | | | 75% improvement in style recalc for Guardians of the Galaxy.
* layout: Rewrite clipping to be per-display-item instead of havingPatrick Walton2014-10-131-1/+0
| | | | | | | | | | | | | | | | | | | a separate `ClipDisplayItem`. We push down clipping areas during absolute position calculation. This makes display items into a flat list, improving cache locality. It dramatically simplifies the code all around. Because we need to push down clip rects even for absolutely-positioned children of non-absolutely-positioned flows, this patch alters the parallel traversal to compute absolute positions for absolutely-positioned children at the same time it computes absolute positions for other children. This doesn't seem to break anything either in theory (since the overall order remains correct) or in practice. It simplifies the parallel traversal code quite a bit. See the relevant Gecko bug: https://bugzilla.mozilla.org/show_bug.cgi?id=615734
* removed restyledamageClark Gaebel2014-10-091-14/+4
|
* Incremental Style RecalcClark Gaebel2014-10-091-5/+15
| | | | | | | | | | | | | | | | | | | This patch puts in the initial framework for incremental reflow. Nodes' styles are no longer recalculated unless the node has changed. I've been hacking on the general problem of incremental reflow for the past couple weeks, and I've yet to get a full implementation that actually passes all the reftests + wikipedia + cnn. Therefore, I'm going to try to land the different parts of it one by one. This patch only does incremental style recalc, without incremental flow construction, inline-size bubbling, reflow, or display lists. Those will be coming in that order as I finish them. At least with this strategy, I can land a working version of incremental reflow, even if not yet complete. r? @pcwalton
* layout: Implement `z-index`.Patrick Walton2014-10-081-1/+6
|
* layout: Implement the correct hypothetical box behavior forPatrick Walton2014-10-011-26/+71
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | absolutely-positioned elements declared with `display: inline`. Although the computed `display` property of elements with `position: absolute` is `block`, `position: absolute; display: inline` can still behave differently from `position: absolute; display: block`. This is because the hypothetical box for `position: absolute` can be at the position it would have been if it had `display: inline`. CSS 2.1 § 10.3.7 describes this case in a parenthetical: "The static-position containing block is the containing block of a hypothetical box that would have been the first box of the element if its specified 'position' value had been 'static' and its specified 'float' had been 'none'. (Note that due to the rules in section 9.7 this hypothetical calculation might require also assuming a different computed value for 'display'.)" To handle this, I had to change both style computation and layout. For the former, I added an internal property `-servo-display-for-hypothetical-box`, which stores the `display` value supplied by the author, before the computed value is calculated. Flow construction now uses this value. As for layout, implementing the proper behavior is tricky because the position of an inline fragment in the inline direction cannot be determined until height assignment, which is a parallelism hazard because in parallel layout widths are computed before heights. However, in this particular case we can avoid the parallelism hazard because the inline direction of a hypothetical box only affects the layout if an absolutely-positioned element is unconstrained in the inline direction. Therefore, we can just lay out such absolutely-positioned elements with a bogus inline position and fix it up once the true inline position of the hypothetical box is computed. The name for this fix-up process is "late computation of inline position" (and the corresponding fix-up for the block position is called "late computation of block position"). This improves the header on /r/rust.
* Remove unneeded input type information from layout.Josh Matthews2014-10-011-8/+8
|
* Disallow toggling radio buttons. Use generated content for checkboxes and ↵Josh Matthews2014-10-011-2/+2
| | | | radio buttons. Switching to the glyph 0 for the average advance width.
* Implement simple layout for text, button, radio, and checkbox inputs. ↵Josh Matthews2014-10-011-7/+26
| | | | Implement simple interaction for checkboxes and radio buttons.
* Use string-cache's Namespace typeKeegan McAllister2014-09-291-2/+1
|
* Remove the 'static lifetime parameters from TElement methodsCameron Zwarich2014-09-271-4/+4
| | | | | | This improves the static correctness of layout's use of DOM nodes. Fixes #2595.
* Merge pull request #3492 from pcwalton/clear-generated-content-tablebors-servo2014-09-261-11/+8
|\ | | | | | | | | | | layout: Support any `display` property in generated content, and allow Reviewed-by: glennw
generated by cgit v1.2.3 (git 2.25.1) at 2025-04-27 08:43:43 +0000