summaryrefslogtreecommitdiffstats
path: root/layout
Commit message (Collapse)AuthorAgeLines
...
* Issue #1512 - Improve handling of multiple selections.wolfbeast2020-04-12-1/+1
| | | | | | | | | IsSelectionEditable should check whether the focus node and anchor node aren't null before trying to use them. This also changes the initialization of selections' aOutIndex to the last range in the selection as a fallback in case we don't add a range later (in AddItem) which could also end up with a null selection otherwise if the additional selection nodes are removed.
* [layout] Always move descendants of layout frames if moved.wolfbeast2020-04-10-0/+2
| | | | | If we move the frame then we always need to move any descendant views, not just in case the frame itself has a view.
* Issue #1511 - Bail on orphan situation.wolfbeast2020-04-10-0/+4
| | | | This resolves #1511
* Issue #1507 - Remove nsRefreshDriver's use of high res system timers.wolfbeast2020-04-03-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.
* Issue #1355 - Make addition of cell border display items depend onwolfbeast2020-03-16-4/+112
| | | | | | | | whether they should be drawn. This reduces the size of display lists for tables by only adding display list items that are actually going to be visibly drawn, which will help overall performance of table drawing.
* Issue #1485 - Fix incorrect grid cell sizing to min/max space.wolfbeast2020-03-13-29/+77
| | | | | | | | | | | | | | | | There were actually two separate logical errors in this method: The first part is that "origSizes.isSome()" is simply a bogus requirement for applying min/max-sizes here. I'm still keeping the optimization of not needlessly copying the mSizes array (as originally intended) since it's a quite common case. The second bug is that min/max-sizes were only applied under the "if (fr != 0.0f)" block. This is bogus since the calculated 'fr' value depends on 'aAvailableSize' which might change by applying min/max-sizes and thus 'fr' could become non-zero in the second round. To fix, this patch just moves "applyMinMax" block out one level.
* Issue #1480 - Skip abspos, fixed, float and placeholders for outline.wolfbeast2020-03-11-2/+12
|
* Revert "Issue #1355 - Better way to create display items for column backgrounds"wolfbeast2020-02-26-1054/+830
| | | | This reverts commit 44c47c50388f526c2d134e16d5debebe94a0faf8.
* Revert "Layout\reftests\table-background\reftest.list should have only ↵wolfbeast2020-02-26-15/+15
| | | | | | additions to the end of it." This reverts commit efdc2af8ab06c50b85e584ef15deab73b66bec6d.
* Layout\reftests\table-background\reftest.list should have only additions to ↵win7-72020-02-26-15/+15
| | | | | | the end of it. Layout\reftests\table-background\reftest.list should have only additions to the end of it. Revert incorrect additions.
* Issue #1355 - Better way to create display items for column backgroundswin7-72020-02-25-830/+1054
| | | | | | | | | | | | | | | | | | | | | | 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.
* Merge pull request #1447 from win7-7/optimization-4-prMoonchild2020-02-17-123/+77
|\ | | | | Speed up nsTableColFrame::GetColIndex
| * Issue #1355 - Make nsTableCellFrame::GetColIndex/GetRowIndex fasterwin7-72020-02-16-123/+77
| | | | | | | | We can devirtualize it, remove some branches.
* | [CSS] Only emit non-GC chrome wrapped XUL box warnings in debug builds.wolfbeast2020-02-14-0/+2
| |
* | Fix a whitespace issue in nsComputedDOMStyle.cppwolfbeast2020-02-12-3/+3
| |
* | [CSS] Add stub for font-variation-settingswolfbeast2020-02-11-0/+42
|/ | | | | | | | | | | | This stub is added because websites insist on considering this very hardware-dependent and O.S.-variable low-level font-control as a "critical feature" which it isn't as there is 0 guarantee that font variation settings are supported or honored by any operating system used by the client. On top this is a WD status feature that sites shouldn't be using, and the feature itself is strongly discouraged for use in favor of standard CSS font manipulation keywords like `font-weight`.
* Merge pull request #1393 from win7-7/optimization-3-prMoonchild2020-02-08-12/+26
|\ | | | | Do less work for columns not in the desired set in PaintRowGroupBackgroundByColIdx
| * Issue #1355 - Do less work for columns not in the desired set in ↵win7-72020-02-06-12/+26
| | | | | | | | | | | | | | | | | | | | PaintRowGroupBackgroundByColIdx Do less work in PaintRowGroupBackgroundByColIdx for cells that are not in our desired set of columns. crash fix: Guard against empty column groups when building a display list for a table.
* | Merge pull request #1388 from win7-7/devirtualize-prMoonchild2020-02-07-61/+24
|\ \ | | | | | | Merging this in even without a test performed since the code change looks sane. real-world testing will have to be performed.
| * | fix whitespacewin7-72020-02-05-1/+1
| | | | | | | | | | | | fix whitespace.
| * | Issue #1386 - Devirtualize GetRowSpan/GetColSpanwin7-72020-02-03-61/+24
| |/ | | | | | | It's at ~1.5% on the perf log for the Netflix use case, which seems a bit too much.
* | Issue #1395 - Remove FlyWeb ServiceMatt A. Tobin2020-02-06-11/+0
| |
* | Issue #1390 - Get rid of the Presentation APIMatt A. Tobin2020-02-06-31/+0
|/
* Issue #1355 - Hit testing in large tables has become extremely slowwin7-72020-02-02-7/+30
| | | | Add dirty rect intersection checks so that we don't build unnecessary table part display items.
* Issue #1378 - Follow-up: make sure background items remain table-aligned.wolfbeast2020-02-02-1/+1
|
* Issue #1378 - Align the drawing of table cell backgrounds with the spec.wolfbeast2020-02-02-55/+105
|
* Merge pull request #1376 from win7-7/optimization-1-prMoonchild2020-01-30-28/+27
|\ | | | | Speed up the traversal of a table row frame's child cells
| * Issue #1355 - Speed up the traversal of a table row frame's child cellswin7-72020-01-29-28/+27
| | | | | | | | Speed up getting the first cellframe in a row and the next cellframe after the given one
* | Merge branch 'master' of https://github.com/MoonchildProductions/UXP into ↵athenian2002020-01-27-73/+19
|\| | | | | | | form-disabled-issue
| * Merge branch '1360'wolfbeast2020-01-27-7/+3
| |\
| | * Issue #1360 - Part 2: Update tests for changed preferences.wolfbeast2020-01-26-7/+3
| | |
| * | Bug 1315885 - Part 4: Implement callback reaction for custom element reactions.Gaming4JC2020-01-26-2/+0
| | | | | | | | | | | | | | | | | | Note: Skipped SyncInvokeReactions since it is removed in CE v1, waste of time. Tag UXP Issue #1344
| * | Bug 1271549 - Remove details and summary preference.Gaming4JC2020-01-26-64/+16
| |/ | | | | | | Tag UXP Issue #1344
* / Issue #1356 - Remove -moz-user-input disabled to improve event handling.athenian2002020-01-16-35/+29
|/
* Bug 1322938 - Basic implementation of HTMLDialogElement.Gaming4JC2020-01-07-0/+21
| | | | Tag #1343
* Issue #1345 - Implement non-standard legacy CSSStyleSheet rulesJustOff2020-01-07-0/+29
|
* Issue #1118 - Part 6: Fix various tests that are no longer correct.wolfbeast2019-12-22-1/+0
| | | | | The behavior change of document.open() requires these tests to be changed to account for the new spec behavior.
* 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 #1219 - Align computed DOM styles with mainstream behvior.wolfbeast2019-12-20-37/+42
| | | | | | | | | This updates our behavior for computed DOM styling to no longer return null on elements that have no display, but return a 0-length (empty) style instead and don't throw. For this we stop looking at having a presentation for the style and just look at the document instead. This resolves #1219
* Issue #1328 - Part 3: Add fuzz to reftests and fix misc other tests.Chris Peterson2019-12-18-4/+4
|
* Check if we're already at the end of the frame's content.Jonathan Kew2019-12-06-1/+2
|
* Issue #1309 - Fix handling of display rows where the elements are notwolfbeast2019-12-01-13/+11
| | | | | | | | | | | | | forming a monotonically increasing sequence (e.g. with position:sticky) Relative positioning can cause table parts to move, which can cause issues with the cursor position to know which rows can be skipped. To make this work, use the max difference between the frame's rect and the union of the frame's "normal" position and the overflow rect to cover the area of relatively positioned elements even if they are out of order. This resolves #1309.
* 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.
* Remove unnecessary calls to ReparentFloatsForInlineChild inMats Palmgren2019-11-29-45/+10
| | | | nsInlineFrame.
* Simplify the overflow child frame reparenting inMats Palmgren2019-11-29-7/+2
| | | | nsInlineFrame::DestroyFrom.
* Issue #1288 - Part 4: Update the OpenType Sanitizer component to 8.0.0wolfbeast2019-11-14-0/+0
|
* Issue #1288 - Part 1a: Update brotli to 1.0.7wolfbeast2019-11-14-5/+5
| | | | | This also reorganizes the exports in the build system to use `brotli/` as include directory.
* Merge branch 'table-sticky-work'wolfbeast2019-11-04-1464/+443
|\ | | | | | | This resolves #146.
| * Issue #146 - Part 7: Remove no longer relevant reftest.wolfbeast2019-11-03-62/+0
| |
| * Issue #146 - Part 6: Allow `position: sticky` on table elements.wolfbeast2019-11-03-20/+7
| |
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-24 19:12:17 +0000