summaryrefslogtreecommitdiffstats
path: root/layout/base
Commit message (Collapse)AuthorAgeLines
* Issue #80 - Include nsIContentInlines.h in ↵adeshkp2020-05-06-0/+1
| | | | layout/base/PositionedEventTargeting.cpp
* Issue #80 - De-unify layout/baseMoonchild2020-05-06-15/+42
|
* Issue #1507 - Remove nsRefreshDriver's use of high res system timers.wolfbeast2020-04-14-103/+0
| | | | | | | Since we are using vsync for timing anyway in the layout refresh driver, there is no need to bump the system timer resolution down to 1 ms. This resolves #1507.
* Revert "Issue #1355 - Better way to create display items for column backgrounds"wolfbeast2020-04-14-159/+76
| | | | This reverts commit 44c47c50388f526c2d134e16d5debebe94a0faf8.
* Issue #1355 - Better way to create display items for column backgroundswin7-72020-04-14-76/+159
| | | | | | | | | | | | | | | | | | | | | | 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.
* [CSS] Only emit non-GC chrome wrapped XUL box warnings in debug builds.wolfbeast2020-04-14-0/+2
|
* Issue #1356 - Remove -moz-user-input disabled to improve event handling.athenian2002020-04-14-3/+2
|
* Issue #1360 - Part 2: Update tests for changed preferences.wolfbeast2020-04-14-1/+1
|
* Issue #1118 - Part 5: Change the way document.open() workswolfbeast2019-12-22-0/+5
| | | | | | | | | | | | This changes the work we do for document.open() in the following ways: - We no longer create a new Window when doing document.open(). We use the same Window but remove all the event listeners on the existing DOM tree and Window before removing the document's existing children to provide a clean slate document to use for .write(). - We no longer create a session history entry (previously would be a wyciwyg URI). We now replace the current one, effectively losing the entry for the original document. - We now support document.open() on windowless documents.
* Issue #1308 - Create nsDisplayTableBackgroundColor to avoid displaywolfbeast2019-12-01-3/+37
| | | | | | | | 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 6: Allow `position: sticky` on table elements.wolfbeast2019-11-03-9/+0
|
* Issue #146 - Part 3: Create nsDisplayTableBackgroundImage to avoidwolfbeast2019-11-03-7/+75
| | | | display list collisions when processing the background image of a table.
* Issue #146 - Part 3: Create nsDisplayTableFixedPosition to avoid displaywolfbeast2019-11-03-5/+103
| | | | list collisions when processing the background image of a table.
* Issue #146 - Part 2: Remove custom table painting component.wolfbeast2019-11-02-3/+0
| | | | | | Since we're now putting table borders and backgrounds properly in the display lists, we no longer need this custom component to do this work for us.
* Issue #146 - Part 1: Draw each table's background on their own displaywolfbeast2019-11-02-3/+10
| | | | | | | | | | | | | | 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 #1230 - Part 1: Fix Back-computing percentages for intrinsic sizing in ↵Gaming4JC2019-09-28-73/+133
| | | | | | | | | | | | | | | | | | | | | | Layout CSS-Grid List of relevant patches applied: 1398537 part 2 - [css-multicol] Implement percentages for 'column-gap' (Gecko part). 1434478 part 1 - [css-grid] Stop back-computing percentage grid gaps when the percentage basis is indefinite. Treat them as zero sized instead. 1434478 part 2 - Stop back-computing percentage padding/margin when the percentage basis is indefinite. Treat them as zero sized instead. 1434478 part 3 - Remove IntrinsicISizeOffsetData::hPctPadding/hPctMargin members since they are now unused. 1434478 part 4 - Factor out constants like NS_UNCONSTRAINEDSIZE so they can be used in headers without needing nsIFrame.h (idempotent patch). 1434478 part 5 - Create nsLayoutUtils::ResolveToLength for resolving CSS <length-percentage> (idempotent patch). 1434478 part 6 - Propagate a percentage basis to nsIFrame::IntrinsicISizeOffsets for resolving padding/margin. This is needed only for CSS Grid since in other cases we're only using IntrinsicISizeOffsets in the inline-axis and the percentage basis is always indefinite for *intrinsic sizing*. When calculating the intrinsic size of grid items in the grid container's block axis however, we do have a definite size for the grid area in the inline-axis and it should be used per: https://drafts.csswg.org/css-grid/#algo-overview "2. Next, the track sizing algorithm resolves the sizes of the grid rows, using the grid column sizes calculated in the previous step." (Percentage padding/margin for grid items is always resolved against the grid area's inline-size nowadays.)
* 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.
* Outdated comment removal (no code changes)win7-72019-08-02-1/+0
| | | | No code changes.
* Revert "Capture delayed events and cancel as necessary."wolfbeast2019-07-18-16/+0
| | | | | | | | | Tag #1052 (backout). Backed out for creating issues like #1191 and other issue-less problems with e.g. losing the caret from text boxes. Of note: this was also backed out from m-c for similar reasons in Bug 1332433. This fixes #1191. This reverts commit 3424afccaebc71c4acd4fa9eadf519c408c5965b.
* Fix comments for Framepropertieswin7-72019-07-12-1/+1
| | | | | | | | | | https://bugzilla.mozilla.org/show_bug.cgi?id=1373884 Fixes comments for Frameproperties. These comments went unnoticed earlier. No code changes.
* Iterate the frame property list once to collect which child list properties ↵win7-72019-07-08-0/+27
| | | | | | we have Look into optimizing out the hashtable lookups from nsContainerFrame
* Avoid multiple hashtable lookups in DisplayItemData destructorwin7-72019-07-07-2/+7
| | | | | | | | | | | UXP has: MOZ_RELEASE_ASSERT(sAliveDisplayItemDatas && sAliveDisplayItemDatas >Contains(this)); sAliveDisplayItemDatas->RemoveEntry(this); and this gets hit during frame destruction. Combine these checks.
* Attach FrameProperties to each frame instead of using a shared hashtablewin7-72019-06-26-526/+285
| | | | Dispense the shared hashtable and instead attach the frame property list directly to nsIFrame.
* Revert "Improve origin-clean algorithm"wolfbeast2019-06-04-5/+3
| | | | This reverts commit e69b3f567c4b8957cc09ba4359e84939f77781c5.
* Improve origin-clean algorithmwolfbeast2019-05-27-3/+5
|
* 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
* Merge pull request #1071 from win7-7/nsDisplayListBuilderMoonchild2019-05-03-2/+2
|\ | | | | nsFrameList::GetLength() calls in nsDisplayListBuilder::MarkFramesForDisplayList() are slow
| * patch to Bug 1377329win7-72019-05-02-2/+2
| |
* | unnecessary space at the end removedwin7-72019-05-02-1/+0
| |
* | patch to Bug 1363423win7-72019-05-02-0/+5
|/
* Capture delayed events and cancel as necessary.wolfbeast2019-04-26-0/+16
| | | | Tag #1052
* Grab caching capturing content with local variable.wolfbeast2019-03-23-5/+5
|
* The result of adding any percentage factor to a size that is zero should ↵JustOff2019-03-21-4/+5
| | | | also be zero
* Add nullcheck for frames in FindNearestCommonAncestorFramewolfbeast2019-02-18-0/+4
| | | | This resolves #978.
* issue #908 - implement missing parts of CSS maskyami2019-02-02-58/+319
|
* Telemetry: Remove stubs and related codeadeshkp2019-01-12-183/+0
|
* Only disallow lazy frame construction for direct children of display: ↵trav902018-12-09-6/+10
| | | | contents elements
* Make caret width normal/thick behind CJK char configurable.wolfbeast2018-10-07-1/+7
| | | | Fixes #820 (regression).
* Clean up a number of unused variables.wolfbeast2018-09-29-6/+0
| | | | Tag #21.
* Bug 1470260 - Part 2: Make RefreshDriverTimer ref-counted and hold a strong ↵wolfbeast2018-09-10-20/+21
| | | | ref on it on the stack when nsRefreshDriver::Tick can be reached.
* Bug 1470260 - Part 1: Ensure that 'this' stays alive for the duration of the ↵wolfbeast2018-09-10-0/+4
| | | | TickRefreshDriver call.
* Remove all C++ telemetry autotimerswolfbeast2018-09-04-9/+2
|
* Remove all C++ Telemetry Accumulation calls.wolfbeast2018-09-03-66/+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.
* Avoid using memset on a not-trivial type like nsTabSizestrav902018-08-18-1/+6
| | | | | | nsTabSizes is non-trivial only because of the user-defined constructor. The idea desired here is certainly to zero all the members without listing them -- but the very act of doing so with a user-defined constructor, makes the idea impossible. Arguably this is something that is permissible in the language, and that the warning should be tailored to permit. I don't think this falls afoul of any of the issues flagged in https://gcc.gnu.org/ml/gcc-patches/2017-06/msg01527.html for example. In the meantime, just explicitly zeroing the three member fields is easy and fixes the warnings.
* Add pref to control CanOptimizeToImageLayer for large downscale factors.wolfbeast2018-07-14-0/+5
| | | | This resolves #626
* Fix Build Bustage - with "--enable-debug"janekptacijarabaci2018-07-12-1/+1
|
* Remove SPS profiler.wolfbeast2018-05-24-47/+0
| | | | | - Conditionals and code blocks. (MOZ_ENABLE_PROFILER_SPS) - Stub out several profiler-only functions.
* Bug 1379762 part 2. Use a more reliable test to figure out when we can skip ↵janekptacijarabaci2018-05-15-1/+14
| | | | | | firing onload in nsDocumentViewer::LoadComplete Issue #357
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-27 07:08:53 +0000