This will allow us to invoke it from nsAttrValueInlines.h, which can't
include ServoStyleSet.h due to circular dependencies.
MozReview-Commit-ID: BgC7ExyWRn7
We sometimes render frames for hit-testing consistency requirements but
those frames don't need compositing. This goes with webrender PR 2358.
MozReview-Commit-ID: D6DRF040D5a
--HG--
extra : rebase_source : fd5dadc35a6f6a54b385f535d4ae9c6e34f3a779
It's a minor change that should align us better with our selection of locales
(Services.intl will use user selection of regional preference locales).
I also removed the western arabic numeral system limitation to allow persian locales
to use eastern arabic numerals correctly.
MozReview-Commit-ID: 8TXX0X9RY9z
--HG--
extra : rebase_source : a7c8f507d841945e47f2d4cc142b4b05bbfab08f
This reduces the side-effects of render (which should ideally be pure) and should improve performance. We already have the mutation observer anyways.
MozReview-Commit-ID: KVhCVEhSvhi
--HG--
extra : rebase_source : 7ed2401be658abcb15bdae3f8545450983904fa8
Programmatic changes don't dispatch the event in order to avoid infinite loops.
MozReview-Commit-ID: 1GYFaSasAZO
--HG--
extra : rebase_source : fb02340c31781c9d16691ff074625d933278f33e
This avoids re-creating elements and getting references via querySelector. It's also a bit cleaner IMO.
MozReview-Commit-ID: 9eUELShq5Yg
--HG--
extra : rebase_source : 8371def08bafaa962df35fd6d1c55cc50b4bfc9d
This avoids the magic of the select automatically making the first option selected without the application state having a good way to know about this.
MozReview-Commit-ID: 1OEsjh2KW1h
--HG--
extra : rebase_source : 49a69af9a49107ea63c308ce9bd945b4868d7485
It's no longer supported to change the selectedness of options directly since that state causes conflicts with the application's own state.
MozReview-Commit-ID: kioot4BXoX
--HG--
extra : rebase_source : 45613b70daa2757f83de5c2fdeaacc596d6ce012
This is useful to ensure that the UI state is properly represented in the store.
If the re-rendering causes visible changes then that means some state is not part
of the store or is not being rendered properly.
MozReview-Commit-ID: 3J5rKWCTMAj
--HG--
extra : rebase_source : d13f35010909a804d496f6da6266cb2fb6e0e56b
<!-- Please describe your changes on the following line: -->
Implements maintaining the current history state. Tracking history state in the session history will be done as a followup.
---
<!-- Thank you for contributing to Servo! Please replace each `[ ]` by `[X]` when the step is complete, and replace `__` with appropriate data: -->
- [X] `./mach build -d` does not report any errors
- [X] `./mach test-tidy` does not report any errors
- [ ] These changes fix #__ (github issue number if applicable).
<!-- Either: -->
- [X] There are tests for these changes OR
- [ ] These changes do not require tests because _____
<!-- Also, please make sure that "Allow edits from maintainers" checkbox is checked, so that we can help you if you get stuck somewhere along the way.-->
<!-- Pull requests that do not address these steps are welcome, but they will require additional verification as part of the review process. -->
Source-Repo: https://github.com/servo/servo
Source-Revision: 469dc84b6ea20b6d378771b008101b49f34e1ad6
--HG--
extra : subtree_source : https%3A//hg.mozilla.org/projects/converted-servo-linear
extra : subtree_revision : ee1b20d80072286a54c216d7153a3d6fcd2239d8
Also comment existing entries at nsWindow::GetCSDSupportLevel().
MozReview-Commit-ID: 1YzZhv7WrQj
--HG--
extra : rebase_source : c1dd1a3452e13e2479afee3c34d396757dae4cfd
In Bug 1393538 I renamed MOZ_STATIC_ASSERT_UNUSED_ATTRIBUTE to MOZ_UNUSED_ATTRIBUTE,
moved it out of it's #define depth, and used it in toolkit. I also orphaned a
comment.
This was wrong. MOZ_UNUSED_ATTRIBUTE was basically identical to MOZ_MAYBE_UNUSED
which exists in Attributes.h (because it is an attribute, not an assertion.)
Undo that wrong thing: restore MOZ_STATIC_ASSERT_UNUSED_ATTRIBUTE to the correct
place, have toolkit use the correct macro, and remove MOZ_UNUSED_ATTRIBUTE.
MozReview-Commit-ID: 5BWWsXgbm9i
--HG--
extra : rebase_source : d07156068c877bf57d400bc6a71e115b7f1aef31
This reverts the change introduced in bug 1394053.
Google has made the download protection lists available to everyone
and so we no longer need to restrict the download protection feature
to official builds.
MozReview-Commit-ID: CQcG5Ip1mDV
--HG--
extra : rebase_source : 55ff4f1e5a09e3c83ad9b24b2eb44789834b2357
pixman-8888-over-565.patch added a call to free(), which is apparently
not included by the other headers when using the new NDK headers.
MozReview-Commit-ID: 9fAuSano36N
--HG--
extra : rebase_source : de9a1f1c4676df9ed724ae7264ca1170b77aac52
Apply Skia upstream commit 592c225b03ca677a1217eabdbc38eede6afcdb14 to
support building with NDK r16.
MozReview-Commit-ID: B6popOoPTni
--HG--
extra : rebase_source : 7d846431f9de12a2ffa270ead93c33cae602c58e
The unified headers already define the keycodes in
GeckoEditableSupport.cpp, so only define them ourselves when not using
unified headers (by checking the __ANDROID_API_X__ macros).
MozReview-Commit-ID: 3Ptakcm0rW
--HG--
extra : rebase_source : c7baf2fc9c02cc891946a197fb17309d3593a610
Modern NDK headers all have <link.h>, so we should always include it,
and still provide shims for anything we need that's not defined in
<link.h>.
MozReview-Commit-ID: GNBDIe73RFm
--HG--
extra : rebase_source : 1246dce8a7ad201cf4f01de8e4912217636f1fc8
