HTMLEditor::EnableStyleSheet() is an XPCOM method but it's used internally.
Therefore, we should create non-virtual method for internal use.
Differential Revision: https://phabricator.services.mozilla.com/D3456
--HG--
extra : moz-landing-system : lando
HTMLEditor::RemoveOverrideStyleSheet() is an XPCOM method but used internally.
So, we should create non-virtual method for this.
Additionally, it calls GetStyleSheetForURL() and RemoveStyleSheetFromList(),
but they search index of internal override style sheet array redundantly.
Moreover, RemoveStyleSheetFromList() returns error only when given URL is
not found, but RemoveOverrideStyleSheet() which is the only one caller, ignores
the error. Therefore, for saving the redundant cost, this patch makes
RemoveStyleSheetFromList() return removing StyleSheet which is retrieved
with the call of GetStyleSheetForURL(). So, RemoveOverrideStyleSheetInternal()
stops calling GetStyleSheetForURL().
Differential Revision: https://phabricator.services.mozilla.com/D3455
--HG--
extra : moz-landing-system : lando
The test case in this patch fails without the proper fix in the first patch
in this patch series.
In this patch two new nsIDOMWindowUtils APIs are introduced to change the
system font settins in tests. Currently the APIs work only on GTK+ platform.
Also to work the test case properly we need to open a new XUL window because we
don't propagate font changes into descendant documents yet (bug 1478212).
MozReview-Commit-ID: 4OLxEkEuF8d
--HG--
extra : rebase_source : 683e64f07c4d8820e5499d8c15b90975618559b8
Now nsBaseWidget::NotifyThemeChanged properly notifies to the pres shell.
MozReview-Commit-ID: Kmd68ckHanl
--HG--
extra : rebase_source : 9928f3788f34b05ff91d1d2b11e2cd332f00af76
In these days, it's common to not create a child widget, so if there is
GetXULWindow() check the notifications are not propagated to the proper pres
shell. Even in the case there is a child widget, which means both of the parent
and the child widgets notify to the same pres shell, but NotifySizeMoveDone is
fairly cheap, and the other two notifications (SysColorChanged and ThemeChanged)
are queued and will be processed later together, so it will not be a big deal.
MozReview-Commit-ID: 2t23kVZzXgS
--HG--
extra : rebase_source : 79f8a955a70f19812373e219e2cee29f669a528e
HTMLEditor::AddOverrideStyleSheet() is an XPCOM method but it's called
internally. So, we should create non-virtual method for it and call it
for internal use.
Differential Revision: https://phabricator.services.mozilla.com/D3454
--HG--
extra : moz-landing-system : lando
This patch changes the failure condition of all mochitest tests to only take the number of failures (given by self.countfail) into account. With this change, mochitest test chunks will only fail if the failure count is not 0. This fixes a case where the TODO tests were considered as failures when no passing tests were run along side them.
Differential Revision: https://phabricator.services.mozilla.com/D3340
--HG--
extra : moz-landing-system : lando
This mirrors the web-platform-tests change at
6058e914c1
According to that commit, WebKit/Chromium/EdgeHTML all have the behavior
that we're switching to here.
Differential Revision: https://phabricator.services.mozilla.com/D3429
--HG--
extra : moz-landing-system : lando
From what I saw by reproducing it locally (e.g. I've also been able to trigger it locally pretty often on linux64 by using "./mach mochitest --verify"), the select popup may sometimes be still using part of its previous position while switching between the test case for the browserAction and the test case for the pageAction.
On linux64 this test was also (from time to time) sending the mouse event when the select element wasn't yet ready to be clicked in the extension popup.
This patch aims to make the behaviors of this test more stable by applying the following changes:
- disable the cosmeticAnimations while running these tests
- explicitly wait the select element in the popup (using ContentTask.spawn and ContentTaskUtils.waitForCondition) before sending it a mouse event
- explicilty close the select popup (and wait the select popup to be hidden) before proceeding to the next test case
The following push to try seems to confirm that these changes are helping to make the test more stable:
- https://treeherder.mozilla.org/#/jobs?repo=try&revision=086c526724ba409068d679036dd3ef13788535b6&selectedJob=194152144
Differential Revision: https://phabricator.services.mozilla.com/D3438
--HG--
extra : moz-landing-system : lando
Catch the exception if adb pull fails on code coverage file, to avoid task retry.
Differential Revision: https://phabricator.services.mozilla.com/D3503
--HG--
extra : moz-landing-system : lando
This includes a patch to enable ccache support.
MozReview-Commit-ID: 9FzMQ2XX4ca
Differential Revision: https://phabricator.services.mozilla.com/D3363
--HG--
extra : moz-landing-system : lando
This initial implementation does twice the necessary processing for mono input,
but that will be addressed in bug 1474222.
MozReview-Commit-ID: AZQ7Zb8jEtK
--HG--
extra : rebase_source : 9feeb254217dc4e14b78cb03315fb948e3477a16
Using the Manage Extension menu item would try to go back to the list view
to uninstall but there was no previous view so it would fail.
Differential Revision: https://phabricator.services.mozilla.com/D3395
--HG--
extra : moz-landing-system : lando
Automatic update from web-platform-testsMerge pull request #12492 from frivoal/contain-support
[css-contain] Add support file in local directory
--
wpt-commits: 3edda8feaabefddc20f2bb0363841182130564dc
wpt-pr: 12492
Automatic update from web-platform-tests[WIP] Extending the capabilities of the HTTP/2.0 server (#12193)
* Made multithreading more robust, and made it so each stream gets its
own thread
* Created H2Request object
* Improved `write_push` docstring, improved flexibility of `write_push`, the user can now choose wether or not to immediately push.
* Using `six.moves` for python compatibility with Queue
* Added beginning of test suite to test H2 stuff.
* Added ability to create and write bogus HEADER, DATA and CONTINUATION frames
* Vendored the hyper dependency used for testing H2 server
* Changed the way Python handlers work for H2, it now returns a FunctionHandler that has methods for specific frame handling if present in the .py resource. No longer requires a thread to parse the request. Allows things such as handling each frame as it is received.
* Refactored `finish_handling` to be a cleaner split between h1 and h2.
--
wpt-commits: e191c351ac133196a1f28218c5b9ef84b1a82c1b
wpt-pr: 12193
Automatic update from web-platform-testsAdd WPT for :scope selector on shadow trees
This WPT shows that :scope does not work for shadow root.
:scope matches nothing when the direct child element or descendant of shadow root should be selected, while :scope works fine for descendant elements within shadow root.
Link to the spec:
https://drafts.csswg.org/selectors-4/#the-scope-pseudo
Link to related issue:
https://github.com/w3c/csswg-drafts/issues/3016
Bug: 859692
Change-Id: I801706eb7891035dcb900588d5542bd48fa1c12a
Reviewed-on: https://chromium-review.googlesource.com/1158445
Commit-Queue: Momoko Sumida <momon@google.com>
Reviewed-by: Rakina Zata Amni <rakina@chromium.org>
Reviewed-by: Hayato Ito <hayato@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583210}
--
wpt-commits: a48491848fb4e328e6cdd5c4d7a95494f1ff2c6a
wpt-pr: 12252
Automatic update from web-platform-testsMerge pull request #12486 from frivoal/contain-12388
[css-contain] use overflow:hidden on elements where it actually works
--
wpt-commits: 7985ccfee21f815f20a7e8699009f76cebbcea66
wpt-pr: 12486
Automatic update from web-platform-testsfix(resources/testdriver): Fallback to documentElement if no body (#12399)
--
wpt-commits: 4b0175b0252eb4d126be5526ea9a9011e1c41f9d
wpt-pr: 12399
Automatic update from web-platform-tests[wptrunner] Make test skipping explicit
Explicitly report on skipped "jsshell" tests during execution. This
gives users an indication that the behavior is intentional and promotes
parity with the output generated by the `--list-tests` flag of the `wpt
run. command.
--
fixup! [wptrunner] Make test skipping explicit
--
wpt-commits: 7216e51e5adc60147487e5226632696aadb9f677, 68ad8b6ff5226972ee9c5418f931e6b4e03eeac3
wpt-pr: 12360