| Commit message (Collapse) | Author | Age | Lines |
|---|
| |
|
|
| |
layout/base/PositionedEventTargeting.cpp
|
| |
|
|
|
|
| |
no optimizations in layout/
(and fix a typo for cs fs)
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
| |
If we move the frame then we always need to move any descendant views,
not just in case the frame itself has a view.
|
| |
|
|
| |
This resolves #1511
|
| |
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
| |
This reverts commit 44c47c50388f526c2d134e16d5debebe94a0faf8.
|
| |
|
|
|
|
| |
additions to the end of it."
This reverts commit efdc2af8ab06c50b85e584ef15deab73b66bec6d.
|
| |
|
|
|
|
| |
the end of it.
Layout\reftests\table-background\reftest.list should have only additions to the end of it. Revert incorrect additions.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
| |
We can devirtualize it, remove some branches.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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`.
|
| |
|
|
|
|
|
|
|
|
| |
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 whitespace.
|
| |
|
|
| |
It's at ~1.5% on the perf log for the Netflix use case, which seems a bit too much.
|
| | |
|
| | |
|
| |
|
|
| |
Add dirty rect intersection checks so that we don't build unnecessary table part display items.
|
| |
|
|
| |
This reverts commit f7b2f0a66536e8e74a0b2dc071a098b7693acecb.
|
| |
|
|
| |
Add dirty rect intersection checks so that we don't build unnecessary table part display items.
|
| | |
|
| | |
|
| |
|
|
| |
Speed up getting the first cellframe in a row and the next cellframe after the given one
|
| | |
|
| | |
|
| |
|
|
| |
Tag #1343
|
| | |
|
| |
|
|
|
| |
The behavior change of document.open() requires these tests to be
changed to account for the new spec behavior.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
| |
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
|
| | |
|
