summaryrefslogtreecommitdiffstats
path: root/layout
Commit message (Collapse)AuthorAgeLines
* [permissions] Fix build bustage with --disable-permissionsMoonchild2020-05-23-0/+2
|
* [printing] Fix build bustage with --disable-printingMoonchild2020-05-23-0/+2
|
* Revert "Merge pull request #1357 from athenian200/form-disabled-issue"athenian2002020-05-23-29/+35
| | | | | This reverts commit ed88b99849156004c04e4a0c87ea9b2360ef19b6, reversing changes made to c4b0715baaffc541670fd1158557aa7e61e521d3.
* Issue #1538 - remove speech recognition engineMoonchild2020-05-20-38/+0
| | | | | | | | | | | | | | | This removes speech recognition, pocketsphinx, training models and the speech automated test interface. This also re-establishes proper use of MOZ_WEBSPEECH to work for the speech API (synthesis part only) that was a broken mess before, with some synth parts being always built, some parts being built only with it enabled and recognition parts being dependent on it. I'm pretty sure it'd be totally busted if you'd ever have tried building without MOZ_WEBPEECH before. Tested that synthesis still works as-intended. This resolves #1538
* issue #1547 - Correct z-ordering for some table parts and add reftestswin7-72020-05-20-2/+164
|
* Issue #1545 - Fix border-radius on table row groups, rows, column groups, or ↵win7-72020-05-20-18/+275
| | | | | | | | | | columns Before issue #146, border-radius on row groups, rows, column groups, or columns don't apply to the background of each cell, yet the border-radius on the cell itself does. After issue #146, the behaviors changed. In this patch, I tried to revert the behaviors of border-radius on table row groups, rows, column groups, or columns back to what happened before issue #146. Also: Don't override GetBorderRadii in nsBCTableCellFrame.
* Issue #1543 - Follow-up: avoid displaying the Alt text if an image is loading.Moonchild2020-05-20-18/+9
| | | | | This prevents the Alt text from briefly being shown before being replaced with the image.
* Issue #1543 - Align <img> with no src to the updated spec.Moonchild2020-05-20-58/+63
|
* Issue #1355 - Fix the nit, remove nsPoint offset in nsFrame.cpp and change ↵win7-72020-05-20-5/+3
| | | | PresShellState member order
* Issue #1355 - Better way to create display items for column backgroundswin7-72020-05-20-340/+488
| | | | | | | | | | | | | | | | | | | | | | 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 - SetNeedToCalcHasBCBorders to true when initialize nsTableFramewin7-72020-05-20-0/+3
| | | | In the printing preview, we create continuous table frame if table is too long to containing in a page. But the default value of NeedToCalcHasBCBorders is false which means we don't calculate HasBCBorders for continuous table frame. Thus, the border collapse is not shown when printing preview.
* Issue #1355 - Avoid unnecessary work in ↵win7-72020-05-20-57/+80
| | | | | | | | | | 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 - Preemptively fix build bustage for 1409114win7-72020-05-20-22/+23
|
* Issue #1355 - Store the dirty rect on the display list builder rather than ↵win7-72020-05-20-430/+259
| | | | | | passing it as a parameter to BuildDisplayList Also fix build bustage for De-unified layout/xul in nsRootBoxFrame.cpp
* Issue #80 - Fix additional deprot in /layout (redwood)Moonchild2020-05-20-0/+5
|
* Issue #80 - Include nsIContentInlines.h in ↵adeshkp2020-05-06-0/+1
| | | | layout/base/PositionedEventTargeting.cpp
* Issue #80 - Resolve issues with compiling on insane gcc configurations with ↵Moonchild2020-05-06-1/+4
| | | | | | no optimizations in layout/ (and fix a typo for cs fs)
* Issue #80 - De-unify layout/xul and tree, gridMoonchild2020-05-06-4/+14
|
* Issue #80 - De-unify layout/tablesMoonchild2020-05-06-1/+9
|
* Issue #80 - De-unify layout/svgMoonchild2020-05-06-1/+12
|
* Issue #80 - De-unify layout/style (redwood)Moonchild2020-05-06-14/+38
|
* Issue #80 - De-unify layout/printingMoonchild2020-05-06-4/+11
|
* Issue #80 - De-unify layout/PITA... I mean layout/genericMoonchild2020-05-06-8/+21
|
* Issue #80 - De-unify layout/baseMoonchild2020-05-06-15/+43
|
* Issue #80 - De-unify layout/mathmlMatt A. Tobin2020-04-24-2/+3
|
* Issue #80 - De-unify layout/formsMatt A. Tobin2020-04-24-1/+5
|
* Issue #80 - De-unify /layout/inspectorMatt A. Tobin2020-04-24-2/+2
|
* Issue #80 - De-unify /layout/tools/layout-debug/srcMatt A. Tobin2020-04-24-1/+1
|
* Issue #80 - De-unify /layout/ipcMatt A. Tobin2020-04-24-4/+1
|
* Issue #80 - De-unify /layout/buildMatt A. Tobin2020-04-24-1/+3
|
* Fix deprot in /layoutwolfbeast2020-04-14-0/+1
|
* Issue #1512 - Improve handling of multiple selections.wolfbeast2020-04-14-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-14-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-14-0/+4
| | | | This resolves #1511
* 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.
* Issue #1355 - Make addition of cell border display items depend onwolfbeast2020-04-14-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-04-14-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-04-14-2/+12
|
* Revert "Issue #1355 - Better way to create display items for column backgrounds"wolfbeast2020-04-14-1054/+830
| | | | This reverts commit 44c47c50388f526c2d134e16d5debebe94a0faf8.
* Revert "Layout\reftests\table-background\reftest.list should have only ↵wolfbeast2020-04-14-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-04-14-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-04-14-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.
* Issue #1355 - Make nsTableCellFrame::GetColIndex/GetRowIndex fasterwin7-72020-04-14-123/+77
| | | | We can devirtualize it, remove some branches.
* [CSS] Only emit non-GC chrome wrapped XUL box warnings in debug builds.wolfbeast2020-04-14-0/+2
|
* Fix a whitespace issue in nsComputedDOMStyle.cppwolfbeast2020-04-14-3/+3
|
* [CSS] Add stub for font-variation-settingswolfbeast2020-04-14-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`.
* Issue #1355 - Do less work for columns not in the desired set in ↵win7-72020-04-14-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.
* fix whitespacewin7-72020-04-14-1/+1
| | | | fix whitespace.
* Issue #1386 - Devirtualize GetRowSpan/GetColSpanwin7-72020-04-14-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-04-14-11/+0
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-24 11:12:32 +0000