This allows other front-ends to know which permissions they should prompt for,
like GeckoView.
Differential Revision: https://phabricator.services.mozilla.com/D70102
--HG--
extra : moz-landing-system : lando
As long as the nested scrollframe doesn't maintain an anchor itself.
This is important for pages which use overflow: hidden to contain large
parts of their scrollable content, see bug 1629237 for an example.
When calling InvalidateAnchor(), we may invalidate an ancestor anchor
itself, if we're not maintaining an anchor and our scrolled frame is
part of the anchor chain. This is important to maintain our state
properly.
I was going to add some assertion to this effect but it can fail when
fragmenting inlines already, so for now I've commented it out and filed
bug 1629280 for that. It's not great, but it cannot lead to a security
issue so we probably can fix it with time.
Differential Revision: https://phabricator.services.mozilla.com/D70609
--HG--
extra : moz-landing-system : lando
This solves an edge case where tab completing a Python 2 command with global
arguments was using the wrong Python version.
Differential Revision: https://phabricator.services.mozilla.com/D56445
--HG--
extra : moz-landing-system : lando
The DOMFullscreen JSWindowActors, which normally handle this sort of thing,
don't get instantiated for events that fire for a parent process DOM Window.
Differential Revision: https://phabricator.services.mozilla.com/D70420
--HG--
extra : moz-landing-system : lando
And add bug numbers to two of the crashtests.
Differential Revision: https://phabricator.services.mozilla.com/D70712
--HG--
rename : layout/base/crashtests/empty-mask.html => layout/base/crashtests/1516286-empty-mask.html
rename : layout/generic/crashtests/very-large-frameset.html => layout/generic/crashtests/1588955-very-large-frameset.html
extra : moz-landing-system : lando
The `video_location` attribute (which was the URL or path of the video) was
removed from the `Job` type, due to it no longer being possible to be a URL.
This was because videos are now passed in through the browsertime-results.tgz
artifact, instead of specified separately in the job description.
This error message was missed in the refactor and was causing failures due to
visualmetrics.py to appear to be caused by our wrapper script. This will not
fix the underlying error causing the intermittents in the first place, but now
the real cause will appear in the log instead.
Differential Revision: https://phabricator.services.mozilla.com/D70062
--HG--
extra : moz-landing-system : lando
This is a frequent question in #introduction / #developers. I'm not
aware of any page in MDN that documents this kind of stuff.
This is intended to be a catch-all page for stuff that some people may
want to have like auto-completion, debugger/linter integration, etc...
In the future, maybe this should be a sub-section in a more general
"Improving your development environment" section or something like that,
where other stuff like commit hooks / mozconfig managers like [1] could
also be explained, but that seems premature, at least for now.
[1]: https://github.com/emilio/mozconfigs
Differential Revision: https://phabricator.services.mozilla.com/D70659
--HG--
extra : moz-landing-system : lando
PaintMaskSurface shouldn't be applying ImgDrawResult::NOT_READY when we don't have a frame and the mask image hasn't been resolved. ImgDrawResult is only about drawing images, not about waiting for external resources to resolve or frames to get constructed. The only purpose of tracking ImgDrawResult's in painting code is to know which frames we need to invalidate because their rendering might change if we sync decode images during a Draw call. Applying NOT_READY here means we invalidate for every paint with the sync decode images flag (ie reftest paints), and it never changes from NOT_READY. This bites the reftest for this bug 1624532.
To fix it, instead of "overloading" the ImgDrawResult we return a bool to indicate the mask is missing or incomplete.
Differential Revision: https://phabricator.services.mozilla.com/D70595
--HG--
extra : moz-landing-system : lando
Target-switching in RDM will always occur on tab remoteness change with new-RDM enabled.
Differential Revision: https://phabricator.services.mozilla.com/D69389
--HG--
extra : moz-landing-system : lando
This removes the annotation from the following tests:
browser/base/content/test/general:
- browser_bug735471.js by removing the test
- browser_clipboard.js which seems like it's not using CPOWs anyway
- browser_blockHPKP.js which is disabled and isn't using CPOWs anyway
browser/components/customizableui/test:
- browser_934951_zoom_in_toolbar.js as CPOW usage was removed in bug 962248
toolkit/components/reader/test:
- browser_readerMode_with_anchor.js as CPOW usage was already removed in bug 1492482
toolkit/content/tests/browser:
- browser_datetime_datepicker.js as CPOW usage was removed in bug 1492482
- browser_saveImageURL.js which used deprecated CPOW-only APIs that I removed in an earlier cset
It also removes all the test framework code relying on this annotation.
Depends on D70685
Differential Revision: https://phabricator.services.mozilla.com/D70686
--HG--
extra : moz-landing-system : lando
