summaryrefslogtreecommitdiffstats
path: root/layout/base/nsDisplayList.cpp
Commit message (Collapse)AuthorAgeLines
* Issue #1656 - Part 8: Devtools and misc.Moonchild2020-09-24-1/+0
|
* Issue #1355 - Fix the nit, remove nsPoint offset in nsFrame.cpp and change ↵win7-72020-05-10-2/+1
| | | | PresShellState member order
* Issue #1355 - Better way to create display items for column backgroundswin7-72020-05-08-12/+17
| | | | | | | | | | | | | | | | | | | | | | Part 1: Remove current table item, as it's never set. Part 2: Get rid of generic table painting code, and handle each class separately. Part 4: Hoist outline skipping into col(group) frame code. Part 5: Skip box-shadow for table column and column groups. Part 6: Store column and column group backgrounds separately, and then append them before the rest of the table contents. Part 7: Pass rects in display list coordinates to AppendBackgroundItemsToTop. Part 8: Create column and column group background display items as part of the cell's BuildDisplayList. Part 9: Used cached values instead of calling nsDisplayListBuilder::ToReferenceFrame when possible, since it can be expensive when the requested frame isn't the builder's current frame. Part 10: Make sure we build display items for table parts where only the normal position is visible, since we may need to create background items for ancestors at that position. Part 11: Create an AutoBuildingDisplayList when we create background items for table columns and column groups, so that we initialize the invalidation state correctly.
* Issue #1355 - Avoid unnecessary work in ↵win7-72020-05-08-8/+15
| | | | | | | | | | nsIFrame::BuildDisplayListForStackingContext() and nsIFrame::BuildDisplayListForChild() and Cleanup DescendIntoChild Bug 1441796 - Part 1: Optimize the (pseudo)-stacking context conditions Bug 1441796 - Part 3: Reuse the results in nsIFrame::BuildDisplayListForStackingContext() for ChildrenHavePerspective(), IsTransformed(), and Combines3DTransformWithAncestors() Bug 1512244 - Part 1: Cleanup DescendIntoChild
* Issue #1355 - Store the dirty rect on the display list builder rather than ↵win7-72020-05-08-9/+7
| | | | | | passing it as a parameter to BuildDisplayList Also fix build bustage for De-unified layout/xul in nsRootBoxFrame.cpp
* Revert "Issue #1355 - Better way to create display items for column backgrounds"wolfbeast2020-02-26-78/+42
| | | | This reverts commit 44c47c50388f526c2d134e16d5debebe94a0faf8.
* Issue #1355 - Better way to create display items for column backgroundswin7-72020-02-25-42/+78
| | | | | | | | | | | | | | | | | | | | | | Part 1: Remove current table item, as it's never set. Part 2: Get rid of generic table painting code, and handle each class separately. Part 4: Hoist outline skipping into col(group) frame code. Part 5: Skip box-shadow for table column and column groups. Part 6: Store column and column group backgrounds separately, and then append them before the rest of the table contents. Part 7: Pass rects in display list coordinates to AppendBackgroundItemsToTop. Part 8: Create column and column group background display items as part of the cell's BuildDisplayList. Part 9: Used cached values instead of calling nsDisplayListBuilder::ToReferenceFrame when possible, since it can be expensive when the requested frame isn't the builder's current frame. Part 10: Make sure we build display items for table parts where only the normal position is visible, since we may need to create background items for ancestors at that position. Part 11: Create an AutoBuildingDisplayList when we create background items for table columns and column groups, so that we initialize the invalidation state correctly.
* Issue #1308 - Create nsDisplayTableBackgroundColor to avoid displaywolfbeast2019-12-01-3/+16
| | | | | | | | list collisions when processing the background color of a table. This is effectively #146 Part 3c to go along with the other 2 there. This resolves #1308.
* Issue #146 - Part 3: Create nsDisplayTableBackgroundImage to avoidwolfbeast2019-11-03-7/+38
| | | | display list collisions when processing the background image of a table.
* Issue #146 - Part 3: Create nsDisplayTableFixedPosition to avoid displaywolfbeast2019-11-03-3/+60
| | | | list collisions when processing the background image of a table.
* Issue #146 - Part 1: Draw each table's background on their own displaywolfbeast2019-11-02-2/+7
| | | | | | | | | | | | | | list items. This patch does the following things: 1. Creates nsDisplayTableBorderCollapse that draws all collapse border of tables. 2. Stops the use of nsDisplayTableBorderBackground. 3. Lets column and column group frames generate display items. 4. When traversing the table, also traverses the column and column group frames. 5. For each type of table frame (col group, col, row group, row and cell), draws their own background.
* Issue #438: Rename coord/coords to originValue/transformOrigin.wolfbeast2019-08-14-13/+13
| | | | For clarity and to prevent typoes.
* Issue #438: Pixel-snap subpixel value for outer SVG and anon child.wolfbeast2019-08-14-2/+7
| | | | This doesn't solve the blurriness yet, but is part of the problem.
* Issue #438: Do not round the translation of an SVG frame.wolfbeast2019-08-14-2/+8
| | | | This doesn't solve the blurriness yet, but is part of the problem.
* Attach FrameProperties to each frame instead of using a shared hashtablewin7-72019-06-26-5/+3
| | | | Dispense the shared hashtable and instead attach the frame property list directly to nsIFrame.
* Lots of time spent maintaining nsDisplayLayerEventRegions (#1116)win7-72019-05-24-0/+4
| | | | | | | | * Simplify the dispatch-to-content region Simplify the dispatch-to-content region in nsDisplayLayerEventRegions::AddFrame() and AddInactiveScrollPort() if it starts to get large. * tabs to spaces
* patch to Bug 1377329win7-72019-05-02-1/+1
|
* issue #908 - implement missing parts of CSS maskyami2019-02-02-11/+11
|
* Telemetry: Remove stubs and related codeadeshkp2019-01-12-99/+0
|
* Remove all C++ Telemetry Accumulation calls.wolfbeast2018-09-03-6/+0
| | | | | This creates a number of stubs and leaves some surrounding code that may be irrelevant (eg. recorded time stamps, status variables). Stub resolution/removal should be a follow-up to this.
* Add pref to control CanOptimizeToImageLayer for large downscale factors.wolfbeast2018-07-14-0/+5
| | | | This resolves #626
* Add m-esr52 at 52.6.0Matt A. Tobin2018-02-02-0/+7553