| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
| |
There's considerable cost associated with creating HWA draw targets
which would negate and regress the performance won by it if used for
too small targets (like small spans of text).
This only uses HWA if >= 8K SurfaceAllocationSize to balance HWA draw
target cost with box blur cost.
|
|
|
|
| |
shadows on platforms that accelerate it.
|
|
|
|
|
|
| |
I figured I should include the reftest for the sake of completeness, though I have already verified the feature working from the site mentioned in the forum thread that prompted me to look into this in the first place.
Ref: BZ 1331528
|
|
|
|
|
|
|
|
|
|
|
| |
We previously didn't do this because we relied on our anonymous wrapper
to perform transforms. However, that resulted in only the children
transforming, and the frame's cliprect wouldn't be updated,
giving the impression of the z-ordering being wrong.
Also adds reftests from the relevant BZ bug found later.
Resolves #2355
|
| |
|
|
|
|
| |
I've verified this against Edge-latest.
|
|
|
|
|
|
|
| |
Vim control lines were re-introduced or not entirely cleaned up.
This nukes them again.
Removing from embedding, extensions, gfx, hal, ipc, layout, mailnews,
media and memory. More to come.
|
| |
|
|
|
|
|
|
| |
* Update reftests to use inset-*
* Update property database
* Update logical properties test
|
| |
|
|
|
|
| |
This reverts commit 2fc5e3ad7d2b09a32e79cb201e405f57329c297e.
|
|
|
|
|
|
| |
Almost forgot to do this. This is in case we need to revisit this for
regressions in the future and the tests are not available online. Never know
when they might come in handy again.
|
|
|
|
|
| |
This doesn't change behavior by default but allows authors to remove the padding
previously enforced to align with focus ring padding, if they wish to.
|
| |
|
| |
|
|
|
|
|
|
| |
MOZ_WIDGET_TOOLKIT == 'cocoa’”
This reverts commit 1fe9c19305dadf2d5bcaa0e589fcd250389dfa8a.
|
|
|
|
|
|
| |
base size resolution, so that percent main-sizes can be respected
This is a workaround, based on https://bugzilla.mozilla.org/show_bug.cgi?id=1455976
|
| |
|
| |
|
|
|
|
| |
Based on https://bugzilla.mozilla.org/show_bug.cgi?id=1398492
|
| |
|
| |
|
|
|
|
| |
The removal of this preference was botched, all other surrounding plumbing changes appear to be working okay. The ability to use prefs to control this stylesheet might be useful in the future, so perhaps this is one of those "if it ain't broke, don't fix it" bugs where leaving well enough alone in the first place would have been the best choice.
|
|
|
|
| |
Resolves #1754.
|
|
|
|
|
|
|
|
| |
This feature should not be shipped until the various definitions of addition for
each additive property are properly specified and then implemented accordingly.
Unlike other patches in this series, compositing is not frequently used
internally so there is no need to enable this by default for chrome callers.
|
|
|
|
| |
Also cleans up some other obsolete checks and stylo reftest lists.
|
|
|
|
| |
Closes #1656
|
|
|
|
|
|
|
| |
the image blocking status appropriately.
This is the same status as we do for known no-data protocols and ensures we
treat these two cases the same.
|
| |
|
| |
|
|
|
|
| |
Another S&R run with some smarter matching.
|
|\
| |
| | |
Fix the wrong position when we calculate the position for position:absolute child
|
| |
| |
| |
| |
| |
| | |
position:absolute child and add reftests
Use |GetUsedBorder| instead of |GetComputedBorder| when we calculate the position for position:absolute child.
|
|/
|
|
|
|
| |
* Remove marquee code
* Regenerate HTML Elements/parser code for Removal of Marquee.
Co-authored-by: Gaming4JC <g4jc@hyperbola.info>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
| |
are involved.
Tag #1375
|
|
|
|
|
|
|
|
|
|
| |
* Implementation for assignedNodes
* Include slots in the flat tree
* Fix event get-the-parent algorithm for a node
* Update and add reftests for Shadow DOM v1
* Update web platform tests expectations
Tag #1375
|
|
|
|
| |
Tag #1375
|
|
|
|
|
|
| |
references
Tag #1375
|
|
|
|
| |
Tag #1375
|
|
|
|
|
|
|
| |
* Use inFlowFrame to check the target frame is summary and its parent is details
* Check summary frame instead of summary element on removing the summary
Tag #1375
|
|
|
|
|
|
|
|
|
|
|
| |
with the pseudo type at creation time
* Stop using a node bit for HasExplicitBaseURI
* Move MAY_HAVE_CLASS to mBoolFlags
* Add a flag to indicate that a node is native anonymous content
* Allow tagging of pseudo-implementing native anonymous content with the pseudo type at creation time, and eliminate explicit style contexts in nsIAnonymousContentCreator::ContentInfo
Tag #1375
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|