| Commit message (Collapse) | Author | Age |
|
|
|
| |
dom.webcomponents.enabled.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
key combination doesn't input any character
Currently, we dispatch keypress event when Enter is pressed without
modifiers or only with the Shift key (line break).
However, other browsers dispatch keypress events for Ctrl + Enter also
even if it doesn't cause any text input.
So, we should fire keypress events for Ctrl + Enter, even in strict
keypress dispatching mode. Note that with other modifiers, it depends on
the browser and/or platform and we can't dispatch the event for
consistent behavior.
This means web developers shouldn't rely one keypress events to catch
Alt + Enter, Meta + Enter and two or more modifiers + Enter.
Based on BZ 1438133
Resolves #2161
|
|
|
|
| |
This fixes a potential crash caused if restyleElement is null.
|
|
|
|
| |
attribute changes
|
|
|
|
| |
slottable
|
|
|
|
| |
instead of the slottable when matching ::slotted()
|
|
|
|
|
|
|
| |
- Check against all selector parts and not the leftmost selector only for ::slotted()
- Walk rules for ::slotted() regardless if the shadow root is opened/closed
- Ensure that ::slotted() rules are walked in the right order
- Fix ::slotted inheritance from topmost shadow root
|
|
|
|
| |
Resolves #2171
|
|
|
|
| |
This is likely inefficient, but I haven't found a way other than this to ensure that the host frame is updated if the inserted/removed content isn't slotted. I'm assuming that Firefox is handling this somewhere else (and may have been even moved to Stylo), but was mentioned in an m-c bug we haven't seen yet. In fact, this is actually similar to how we handled elements passed to ContentInserted before landing e31ed5b07466d4a579fe4b025f97c971003fbc3f.
|
|
|
|
| |
nsImageLoadingContent::BindToTree
|
|
|
|
| |
Resolves #2146
|
| |
|
|\
| |
| |
| |
| |
| | |
FranklinDM/UXP-contrib:work_wc-incremental-1 into master
Reviewed-on: https://repo.palemoon.org/MoonchildProductions/UXP/pulls/2139
|
| | |
|
| | |
|
| |
| |
| |
| | |
aNodesWithProperties parameter
|
| |
| |
| |
| |
| |
| | |
ContentEventHandler
* Unlike the original patch, I went with just getting a reference to the document rather than replacing mPresShell with mDocument.
|
| | |
|
| |
| |
| |
| | |
ContentEventHandler
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
ErrorResult
* Bug 1393806 (Part 4) landed as part of Issue #1118.
* Account for ReparentWrappersInSubtree, introduced in 1466991
|
| |
| |
| |
| |
| |
| | |
non-XPCOM version of document.AdoptNode
* Unlike the original patch, this does not remove the XPCOM version of Document.adoptNode/importNode to avoid breaking other applications that might be using those functions.
|
| |
| |
| |
| |
| |
| | |
to use an ErrorResult for errors
This will allow us to propagate out more informative errors in some cases.
|
| |
| |
| |
| | |
across documents
|
| |
| |
| |
| | |
ShadowRoot
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This covers the following:
Bug 1413834 Implement sequential focus navigation regarding shadow DOM
> Bug 1430020 Let sequential focus navigation in shadow DOM enter iframes
> Bug 1430701 Handle focus navigation on frameless shadow hosts in light DOM
> Bug 1430692 Handle focus navigation on NAC in shadow DOM
> Bug 1453693 Ensure sequential focus navigation works in Shadow DOM and add some tests
> Bug 1466581 Handle sequential focus also in nested shadow DOM
> Bug 1481079 Shadow DOM hosts should be focusable
> Bug 1507101 Use StyleChildrenIterator instead of custom frame tree walking code to handle NAC inside shadow dom
> Bug 1512043 Ensure traverse all nodes owned by the top level shadow host
> Bug 1512457 Fix various cases that focus navigation doesn't work well with frameless shadow host
> Bug 1513141 Really minor nsFocusManager cleanup
> Bug 1519090 Keyboard focus is trapped inside <slot>
> Bug 1528034 Make IsHostOrSlot null-safe
> Bug 1544826 Wrong focus navigation behavior when the root element is a shadow root
>> Bug 1500273 Ensure backward focus navigation works in Shadow DOM
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
Shadow DOM
|
| |
| |
| |
| | |
ShadowRoot.elementFromPoint/elementsFromPoint
|
| | |
|
| |
| |
| |
| |
| |
| | |
with MouseEvent.relatedTarget
* This incorporates changes from Bug 1413102.
|
| |
| |
| |
| |
| |
| | |
shadow DOM retargeting
Based on https://bugzilla.mozilla.org/show_bug.cgi?id=1466581
|
| |
| |
| |
| |
| |
| |
| | |
in event handling
* RE: BasicEvents.h - our WidgetEvent is not movable (yet), so the change that requires that wasn't included.
* Parts of this use code that was introduced in bug 1427511. For now, they were replaced with their equivalents.
|
| | |
|
| | |
|
|/
|
|
|
|
|
|
| |
Based on a patch from Mozilla bug 1598164.
Needed due to identifier collision between NSS and IDBTransaction.
Co-authored by: Simon Giesecke <simon.giesecke@gmail.com>
Co-authored by: Matt A. Tobin <email@mattatobin.com>
|
|
|
|
|
|
| |
shadow-including tree order
Based on https://bugzilla.mozilla.org/show_bug.cgi?id=1326028
|
|
|
|
| |
convert
|
| |
|
|
|
|
| |
Required for upcoming libyuv update
|
|
|
|
| |
https://hg.mozilla.org/integration/autoland/rev/6f4c7904cda8
|
|
|
|
| |
https://hg.mozilla.org/mozilla-central/rev/be342c90755d11551623362f2058c0326f63bbb3
|
|
|
|
|
| |
Just in case someone forces the wrong key type and misuses WebCrypto.
It won't be usable anyway so better to throw.
|
|
|
|
|
|
| |
RestrictedSelectorListMatches
This is in preparation for merging the logic of RestrictedSelectorListMatches and AnySelectorInArgListMatches.
|
| |
|
| |
|
| |
|
|
|
|
| |
attribute
|