This also updates the link behavior to use the less privileged openWebLink.
MozReview-Commit-ID: HHDQKAQz6hQ
--HG--
extra : rebase_source : d57670983073893be6c67fe0c3dc991cbe1e5eb2
A few years ago in bug 1126274, we added RDP events to the DevTools transport so
that the add-on RDP Inspector could display packets as they flow by.
The add-on no longer works as it is not a WebExtension. Maybe someday we'll
revisit this, but for now this removes some dead code.
MozReview-Commit-ID: AvgQhYWwBUA
--HG--
extra : rebase_source : 45a295cb8b06729a0e3f74a90ce1094633f0f121
nsIX509CertDB.findCertByEmailAddress performs multiple certificate verifications
on the main thread, which is bad because it blocks the main thread and can cause
nested event loop spinning. Firefox doesn't even use this function. Other
products that use this function will either have to re-implement it locally or
find some other workaround.
MozReview-Commit-ID: HShl0H8cgxs
--HG--
extra : rebase_source : 63ee16b600ca7c2867352ee1ad791eb79b82a77c
These functions perform certificate verification on the main thread, which is
already a bad idea. They can also cause OCSP requests to be made from the main
thread, which will cause nested event loop spinning, which is an even worse
idea. Luckily this really only affects tests.
MozReview-Commit-ID: LqDAgDmlyER
--HG--
extra : rebase_source : c86414db0b6d6e7e83b5e3f371506b773813cdbf
This updates existing bits of code (notably one of the GetTargetAPZC
methods) to use the new map for more efficient lookups. Places that
used GetTargetNode with a presshell-ignoring comparator can now use
GetTargetAPZC as well.
MozReview-Commit-ID: GFjO6KigVop
--HG--
extra : rebase_source : 336a7118927bd6c3f0e4edaf15770afb1f6602a9
We are already building an almost-what-we-want map in the
TreeBuildingState, so I modified to be exactly what we want, and then
just move it to the APZCTreeManager once the tree build is done.
MozReview-Commit-ID: 40RVwYv93wR
--HG--
extra : rebase_source : 118b28dfb796f8153d07dfb356eb45a0d8298c8d
This is mostly just moving the existing hash function and introducing
additional helpers to create maps with presshell-ignoring guid keys. We
can use this in one place trivially so I did that as well.
MozReview-Commit-ID: G8nMS1PECT4
--HG--
extra : rebase_source : 4f34da9db77f7ec4b7e5ebaeccd532c8f8c92283
Previously we were checking IsDefined() rather than HasImage(), but
were hitting crashes. This was because Format() can return null if the
attach point is defined but the attached texture level or renderbuffer
aren't themselves defined. HasImage() checks for this case.
MozReview-Commit-ID: 8KY3zPXXAFv
--HG--
extra : rebase_source : 50706ae0903e15e8b299e7417e7e5d829b11aa79
This test tests the original version of the DOMPoint spec. These changes
update it to the current working draft.
MozReview-Commit-ID: AYUz8xks2RE
--HG--
extra : rebase_source : fade2e55d69459830d9768ce9fed4bee69bdfbca
The most recent specification gives DOMPointReadOnly a constructor as well as
a static fromPoint method.
This fixes several failing wpt tests.
MozReview-Commit-ID: 4mPhMm5yhJA
--HG--
extra : rebase_source : d8159b38330c990672f99dbc748a739eced5e6a2
The Web IDL for DOMPoint no longer has this constructor. As far as I can tell,
it is still unused, so let's follow the spec.
MozReview-Commit-ID: 6Lz1BN5YAV5
--HG--
extra : rebase_source : 04b70b673e63d7cea1e528009526285a4af8f472
This makes the optimization rarer, but is significantly simpler, since we should now be guaranteed that all placeholder frames have their out of flow frames in the same stacking context.
MozReview-Commit-ID: 1Nf8Sx1dca7
--HG--
extra : rebase_source : 74856420fdf6108fe749c94418a20bc9faa6fc5e
It isn't supported server side, so make the TRRoff mode instead count
as nativeonly.
MozReview-Commit-ID: 73si3kam6xU
--HG--
extra : rebase_source : 2869fc515ffb23303bdf2fc5e231d0edc62193e7
Note that BinSource-auto.{h, cpp} and BinToken.h are auto-generated from BinSource.{yaml, webidl}.
This patch contains the following changes:
- updates to the webidl specifications;
- adapt BinSource.* to the new tokenizer API;
- split BinASTParser across BinASTParserBase and BinASTParser<Tok>.
The effect is that we may now use the BinASTParser with both the (updated) tester tokenizer
and the (new) multipart tokenizer.
MozReview-Commit-ID: HCF2m3qDTFH
--HG--
extra : rebase_source : 3c88a9dab735ddb9ce4fdaab93c1b1115489e548
BinAST parsers need to perform frequent lookup for string values, e.g. once for each `let`, `var`, `const`,
`+`, `-`, `instanceof` (string enums), as well as a number of startup lookups for string values such as
"LiteralNullExpression", etc. (ast table)
This patch introduces zero-copy lookup tables for both of these. These tables are shared among instances of parsers in a JSRuntime.
MozReview-Commit-ID: 75BasAxLoha
--HG--
extra : rebase_source : 942f7f7849a113e5ce7b1eb420396d4eef194592
As a preliminary step for introducing the BinTokenReaderMultipart, we start by splitting the BinTokenReaderTester in two.
Also, we change a bit the API of the BinTokenReaderTester to uniformize with the BinTokenReaderMultipart.
MozReview-Commit-ID: 4SlHaqEAZMk
--HG--
extra : rebase_source : 3b9574a3d78bcafb961f8db548f6215825b66f82
Changes:
- instead of parsing string enums by string matching, we go through a new `enum class` `BinVariant`, whose handling is part of the tokenizer;
- we now generate this `enum class`.
MozReview-Commit-ID: FnzG772RZam
--HG--
extra : rebase_source : 5da853a36715d04e3d097cbf63749ac1651cd841
This introduces a new tokenizer for the BinAST parser: the multipart tokenizer.
The format used by the multipart tokenizer is described here: https://binast.github.io/binjs-ref/binjs_io/multipart/index.html
While the details of the format may still change, this is the tokenizer we intend to ship.
We only implement the `identity; ` compression scheme. For the moment, there are no plans to implement other compression schemes.
MozReview-Commit-ID: 8WUa3QX5GWt
--HG--
extra : rebase_source : e0bad689b07f9a3d322d2ec81ab1c7e0d3e43b3c
We already rebuild all display items for out-of-flow descendants of a modified frame, but we don't currently mark them modified.
In this case, a scrollframe becomes active, and causes position:fixed descendants to use nsDisplayFixedPosition instead of nsDisplayWrapList.
Not invalidating means that we end up with both versions, instead of removing the old one.
MozReview-Commit-ID: LXjjsQhzxiB
--HG--
extra : rebase_source : e286bad815f2d799ec641e5b2ef6507eb57d22cd
The test invalidates the z-index element, so that we do a partial build with just that and the DAG no longer knows the relative ordering between it and the other blue elements.
We then expand the size of the 'first' elements stacking context, and ensure that we provide enough intersecting items to know that we're on top of the z-index element.
MozReview-Commit-ID: 13aRGm1eucp
--HG--
extra : amend_source : 11d530fbec816b3dbcfa7228625e0ba0e73064d0
