| Commit message (Collapse) | Author | Age | Lines |
| |
|
|
|
|
|
|
| |
This was added as part of the WebExtension sec issue CVE-2017-5389.
Since we no longer have this interface, it needed to be removed to
prevent errors in the WebRequest channel callback.
|
|\
| |
| | |
Forms: Click() isn't executing properly when elements are defined disabled
|
| |
| |
| |
| | |
Forgot to include these before.
|
| |\
| |/
|/|
| | |
form-disabled-issue
|
| | |
|
| |
| |
| |
| | |
Intended to be bumped to 4.6.x once CE/sDOM is landed completely.
|
|\ \ |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This gets rid of platform-dependent hard-coded defaults, but keeps
build-time blocking if there is no GL provider (in which case layers
acceleration almost certainly won't work because it needs a GL
compositor and would likely crash without)
New prefs are
- layers.acceleration.enabled to enable HWA
- layers.acceleration.force to force it enabled (requires .enabled to be
set as well)
This is the platform part of this issue. The rest will be front-end work
(Preference UI integration and pref migration)
|
| | | |
|
|\ \ \
| | | |
| | | | |
Custom Elements v1
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
LookupCustomElementDefinition
Since we are dealing with the element (nodeInfo->LocalName() and NameAtom() are the same value), we could use nodeInfo->NameAtom() instead.
Tag UXP Issue #1344
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
when the attribute value is an empty string;
Tag UXP Issue #1344
|
| | | |
| | | |
| | | |
| | | | |
Tag UXP Issue #1344
|
| | | |
| | | |
| | | |
| | | | |
Tag UXP Issue #1344
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
the constructor.
Tag UXP Issue #1344
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
even if some of elements are already unlinked
Tag UXP Issue #1344
|
| | | |
| | | |
| | | |
| | | | |
Tag UXP Issue #1344
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
MutationObserver to use them
Tag UXP Issue #1344
|
| | | |
| | | |
| | | |
| | | | |
Tag UXP Issue #1344
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
non-custom element
Tag UXP Issue #1344
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
elements reactions;
The spec was unclear on how CEReactions interact with thrown exceptions; see https://github.com/whatwg/html/issues/3217. The spec is now being clarified in https://github.com/whatwg/html/pull/3235.
Tag UXP Issue #1344
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
prototype swizzling for custom element
Tag UXP Issue #1344
|
| | | |
| | | |
| | | |
| | | | |
Tag UXP Issue #1344
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
CustomElements feature
Tag UXP Issue #1344
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
validation checks
Tag UXP Issue #1344
|
| | | |
| | | |
| | | |
| | | | |
Tag UXP Issue #1344
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
removing parts of v0.
Tag UXP Issue #1344
|
| | | |
| | | |
| | | |
| | | | |
Tag UXP Issue #1344
|
| | | |
| | | |
| | | |
| | | | |
Tag UXP Issue #1344
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
sending callback.
Tag UXP Issue #1344
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
"create an element for a token".
With fixup for missing header due to unified builds.
Tag UXP Issue #1344
|
| | | |
| | | |
| | | |
| | | | |
Tag UXP Issue #1344
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
See Bug 1173199 / 1216893
Tag UXP Issue #1344
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Fallout from 483155
Tag UXP Issue #1344
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Since we want to keep this element, it has to be adapted to the parser changes in 483155
Tag UXP Issue #1344
|
| | | |
| | | |
| | | |
| | | | |
Tag UXP Issue #1344
|
| | | |
| | | |
| | | |
| | | | |
Tag UXP Issue #1344
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This is all the manual work for Bug 483155, minus the added functionality to disable SVG and MathML which can be done at any time and are out of scope.
Tag UXP Issue #1344
|
| | | |
| | | |
| | | |
| | | | |
Tag UXP Issue #1344
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
with hyphen).
Regen.
Tag UXP Issue #1344
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
(ones with hyphen).
Tag UXP Issue #1344
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Per spec, document objects have a throw-on-dynamic-markup-insertion counter, which is used in conjunction with the create an element for the token algorithm to prevent custom element constructors from being able to use document.open(), document.close(), and document.write() when they are invoked by the parser.
Tag UXP Issue #1344
|
| | | |
| | | |
| | | |
| | | | |
Tag UXP Issue #1344
|
| | | |
| | | |
| | | |
| | | | |
Tag UXP Issue #1344
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
CustomElementData::SetCustomElementDefinition and GetCustomElementDefinition;
This is a follow-up patch for bug 1392970. Since we only set CustomElementDefinition on a custom element which is custom, we could add more assertion to ensure that.
Tag UXP Issue #1344
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
in HTML parser from sorted to level order BST in order to take advantage of cache during lookup.
HTML Regen.
Tag UXP Issue #1344
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
from sorted to level order BST in order to take advantage of cache during lookup.
Java Regen.
Tag UXP Issue #1344
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
from sorted to level order BST in order to take advantage of cache during lookup.
Tag UXP Issue #1344
|