The .status element is turned into a simple <span> (instead of a <a>),
so it's 1. more semantically correct, and 2. doesn't create a new line.
We also handle null request `totalTime` by not showing the time in the status info,
as that could make the test to fail in chaos mode.
Differential Revision: https://phabricator.services.mozilla.com/D304391
Implements the gecko-parts of Picture In Picture API, to which the various platforms can add their implementation for opening a PIP Window to.
nsIPictureInPictureFunctions.idl shall be implemented by the different platforms. For desktop we already have a "native" PIP implementation and this will be re-used.
Platforms which does not implement nsIPictureInPictureFunctions.idl, will signal that they don't support it (and attempts to request via the API algorithms, will reject accordingly).
Differential Revision: https://phabricator.services.mozilla.com/D286141
Implements the gecko-parts of Picture In Picture API, to which the various platforms can add their implementation for opening a PIP Window to.
nsIPictureInPictureFunctions.idl shall be implemented by the different platforms. For desktop we already have a "native" PIP implementation and this will be re-used.
Platforms which does not implement nsIPictureInPictureFunctions.idl, will signal that they don't support it (and attempts to request via the API algorithms, will reject accordingly).
Differential Revision: https://phabricator.services.mozilla.com/D286141
These are generally cases where the exclusion is no longer necessary, because we've fixed whatever was causing it to be added in the first place.
Differential Revision: https://phabricator.services.mozilla.com/D300083
We use the preference of scroll-driven animation to protect the
attribute (i.e. the getter) and use the preference of CSS Typed OM to
protect the return value of `CSSNumericValue`. If `CSSNumericValue` is
disabled, we return a DOM error.
We don't support ViewTimeline contructor yet so
scroll-animations/view-timelines/duration.html is still failed.
Also, timeline-offset-in-keyframe.html is passed because we enable the
preference of Typed OM for the tests in scroll-animations folder.
Differential Revision: https://phabricator.services.mozilla.com/D301428
This reverts commit f572e49026.
Revert "Bug 1924775 - Use a defined version of the "globals" npm module, and resolved raised issues. r=frontend-codestyle-reviewers,devtools-reviewers,home-newtab-reviewers,flozia,nchevobbe,mossop,thecount"
This reverts commit e0f4d195f8.
These are generally cases where the exclusion is no longer necessary, because we've fixed whatever was causing it to be added in the first place.
Differential Revision: https://phabricator.services.mozilla.com/D300083
This reverts commit 1a90fee5f3.
Revert "Bug 1924775 - Use a defined version of the "globals" npm module, and resolved raised issues. r=frontend-codestyle-reviewers,devtools-reviewers,home-newtab-reviewers,flozia,nchevobbe,mossop,thecount"
This reverts commit 9b2da35aba.
These are generally cases where the exclusion is no longer necessary, because we've fixed whatever was causing it to be added in the first place.
Differential Revision: https://phabricator.services.mozilla.com/D300083
Bug 2033191 made sure we only call ownerGlobal on nodes.
As per the discussion in dev-platform, the front-end ~always wants
.documentGlobal. This removes ownerGlobal from the bindings. Following
patch will rename internal GetOwnerGlobal in gecko to GetRelevantGlobal
as per the HTML spec terminology.
Differential Revision: https://phabricator.services.mozilla.com/D297183
Bug 2033191 made sure we only call ownerGlobal on nodes.
As per the discussion in dev-platform, the front-end ~always wants
.documentGlobal. This removes ownerGlobal from the bindings. Following
patch will rename internal GetOwnerGlobal in gecko to GetRelevantGlobal
as per the HTML spec terminology.
Differential Revision: https://phabricator.services.mozilla.com/D297183
Bug 2033191 made sure we only call ownerGlobal on nodes.
As per the discussion in dev-platform, the front-end ~always wants
.documentGlobal. This removes ownerGlobal from the bindings. Following
patch will rename internal GetOwnerGlobal in gecko to GetRelevantGlobal
as per the HTML spec terminology.
Differential Revision: https://phabricator.services.mozilla.com/D297183
Bug 2033191 made sure we only call ownerGlobal on nodes.
As per the discussion in dev-platform, the front-end ~always wants
.documentGlobal. This removes ownerGlobal from the bindings. Following
patch will rename internal GetOwnerGlobal in gecko to GetRelevantGlobal
as per the HTML spec terminology.
Differential Revision: https://phabricator.services.mozilla.com/D297183
This patch adds the autocomplete package to leverage the closeBrackets extension.
The autocomplete paackage will also be benefical in the future when we want to migrate
to using the full auto complete feature in codemirror 6.
Differential Revision: https://phabricator.services.mozilla.com/D279497
In part 2, the way that the principal for a blob: URI is computed was changed,
such that it is no longer pointer-identical to the creating document. This had
an impact on the behaviour of `importScripts` requests from dedicated worker
with a blob: URL scheme.
Previously, there was an oversight in the code for importScripts, where, due to
the principal being pointer-identical, we would treat script imports from blob:
URI dedicated workers as subresource requests from the creator document. As the
principal is no longer pointer-identical, we no longer hit this codepath, and
the request is no longer created as a document subresource request.
As a result of this, the script error which this web console test was looking
for is emitted, but is not directly associated with the document being
observed, leading to the test timing out.
It's not clear to me how to observe the correct console in this case, but if
this is pointed out, I can update the test to do that instead.
Differential Revision: https://phabricator.services.mozilla.com/D276057
This reverts commit 47367770c3.
Revert "Bug 2005247 - Part 3: Always read BlobURL info over IPC, r=asuth"
This reverts commit df37ac38f8.
Revert "Bug 2005247 - Part 2: Validate BlobURL ContentLength header during channel fetch, r=asuth,necko-reviewers,valentin"
This reverts commit 45e63e6920.
Revert "Bug 2005247 - Part 1: Get the BlobImpl from the BlobURLChannel, r=asuth,media-playback-reviewers,padenot"
This reverts commit 440a33211b.
Revert "Bug 2005002 - Part 5: sec-fetch-storage-access not implemented for workers, r=manuel"
This reverts commit 5654faf8a0.
Revert "Bug 2005002 - Part 4: Fix devtools tests for blob: URL dedicated worker changes, r=devtools-reviewers,ochameau"
This reverts commit 9c9c197990.
Revert "Bug 2005002 - Part 3: Extension content scripts for Blob URLs no longer match with full paths, r=extension-reviewers,robwu"
This reverts commit 55f399175f.
Revert "Bug 2005002 - Part 2: Infer Blob URL principal from URL when possible, r=asuth,extension-reviewers,necko-reviewers,home-newtab-reviewers,robwu,mconley,kershaw,bvandersloot"
This reverts commit d3022ec470.
Revert "Bug 2005002 - Part 1: Support do_QueryObject for nsSimpleURI and subclasses, r=necko-reviewers,valentin,asuth"
This reverts commit 3d1199b4d4.
In part 2, the way that the principal for a blob: URI is computed was changed,
such that it is no longer pointer-identical to the creating document. This had
an impact on the behaviour of `importScripts` requests from dedicated worker
with a blob: URL scheme.
Previously, there was an oversight in the code for importScripts, where, due to
the principal being pointer-identical, we would treat script imports from blob:
URI dedicated workers as subresource requests from the creator document. As the
principal is no longer pointer-identical, we no longer hit this codepath, and
the request is no longer created as a document subresource request.
As a result of this, the script error which this web console test was looking
for is emitted, but is not directly associated with the document being
observed, leading to the test timing out.
It's not clear to me how to observe the correct console in this case, but if
this is pointed out, I can update the test to do that instead.
Differential Revision: https://phabricator.services.mozilla.com/D276057
This reverts commit 85b2d0d3dd.
Revert "Bug 2022763 - Propagate owner global from input element to DOM files properly. r=dom-core,win-reviewers,smaug,gstoll"
This reverts commit ff40c521b2.
This patch adds the autocomplete package to leverage the closeBrackets extension.
The autocomplete paackage will also be benefical in the future when we want to migrate
to using the full auto complete feature in codemirror 6.
Differential Revision: https://phabricator.services.mozilla.com/D279497
Expose a new cropDimensionsIfNeeded helper from ScreenshotUtils and reuse this in devtools capture-screenshot directly.
This will ensure the implementation remains in sync with the screenshot one.
Differential Revision: https://phabricator.services.mozilla.com/D262533
Hubert B Manilla