aboutsummaryrefslogtreecommitdiffstats
path: root/components/script_layout_interface/restyle_damage.rs
Commit message (Collapse)AuthorAgeFilesLines
* Stop using associated types for the concrete TRestyleDamage implementation.Bobby Holley2016-11-071-267/+0
| | | | MozReview-Commit-ID: LfaZFCVlIb1
* layout: Add a `REPOSITION` restyle damage type.Patrick Walton2016-09-261-28/+32
| | | | | | Separating out `REPOSITION` from `REPAINT` allows us to compute stacking-context-relative positions without rebuilding the display list. This saves a lot of time when responding to script-to-layout queries.
* calculate damage for opacity changeAlexandrov Sergey2016-08-231-1/+1
|
* Make RestyleDamage::compute take no optional argument, delegate the handling ↵Emilio Cobos Álvarez2016-08-101-8/+2
| | | | to the caller.
* style: Force to stop computing children if we find the parent has display: none.Emilio Cobos Álvarez2016-08-101-0/+4
|
* style: Refactor TRestyleDamage and TNode to accept/provide a "style source"Emilio Cobos Álvarez2016-08-031-7/+14
| | | | | | | | | | 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...).
* stylo: Allow computing change hints during the traversal.Emilio Cobos Álvarez2016-08-031-2/+3
|
* Remove the ComputedValue traits and style_struct_traitsSimon Sapin2016-07-201-2/+1
|
* Introduce a script_layout_interface crate and move RestyleDamage to it.Ms2ger2016-06-201-0/+258