This adds a checkbox to the print preview toolbar for simplifying
a document before printing.
This feature is currently disabled by default, hidden behind the
print.use_simplify_page pref.
MozReview-Commit-ID: HOtkuEQnJFg
--HG--
extra : rebase_source : 0423269ff26a4420a05de45cd7ad4ab84458f4f8
extra : amend_source : a340a83dc70c73aed5efcaf84c09503e88301888
Since the UI is now changed in listeners inside the system group, they
are invoked after the listeners added by the content. Because of that,
UI check needs to be asynchronously, otherwise we would be checking the
state before videocontrols update. For the same reason, mouse/keyboard
operations need to be invoked asynchronously as well, otherwise they
would be applied based on the UI before update. This shouldn't change
what is tested here, as user inputs are asynchronous by nature.
MozReview-Commit-ID: 4h9Oa9qMVc5
--HG--
extra : source : ca67bc5ad3a3ddc6cf41dd4c4d6af647d94bc298
Listeners in the system group are invoked after listeners in the default
group, so we can check defaultPrevented synchronously, and we have to
change the play state according to the state of the play button.
Due to the same reason above, we need to check the UI async in tests.
MozReview-Commit-ID: Bs4MZvGefJj
--HG--
extra : source : b28d589bb2675116fc7927381061fb0a03e39369
The size is reduced by making the message only carry the count of blocked popups, and not the full list of popup URLs that were blocked. The parent becomes responsible for retrieving the list from the child when it needs to display it.
MozReview-Commit-ID: DsxLFD8iE3t
There's some reorganization of the code in aboutSupport to support displaying Windows XP as a string without needing to be localized, as this will require an uplift to Aurora.
MozReview-Commit-ID: IqLjEIKq0VI
CLOSED TREE
Backed out changeset 788365ddaf61 (bug 1274520)
Backed out changeset 6c204be833d1 (bug 1274520)
Backed out changeset 4f15271e5488 (bug 1274520)
There was some mistake in patch of bug 694696 which incorrectly added
'skip-if' for some unrelated test. This patch reverts those mistakes in
addition to just moving the test back.
It also attaches the "fullscreen" tag to the test as it triggers that.
MozReview-Commit-ID: 2PMX6PFZWm2
--HG--
extra : source : bd575feaee3d1e434d073f386d4095998f5644db
There was some mistake in patch of bug 694696 which incorrectly added
'skip-if' for some unrelated test. This patch reverts those mistakes in
addition to just moving the test back.
It also attaches the "fullscreen" tag to the test as it triggers that.
MozReview-Commit-ID: 2PMX6PFZWm2
--HG--
extra : source : f51c8dd75753ce5ef7d171b74f3f39fbd55ed38d
There was some mistake in patch of bug 694696 which incorrectly added
'skip-if' for some unrelated test. This patch reverts those mistakes in
addition to just moving the test back.
It also attaches the "fullscreen" tag to the test as it triggers that.
MozReview-Commit-ID: 2PMX6PFZWm2
--HG--
extra : source : f51c8dd75753ce5ef7d171b74f3f39fbd55ed38d
This patch was generated by the command:
find * -type f -exec sed -i -f ../mozpropsub {} \;
in the root of the repository, with the file ../mozpropsub containing:
s/-moz-padding-end\>/padding-inline-end/g
s/-moz-padding-start\>/padding-inline-start/g
s/-moz-margin-end\>/margin-inline-end/g
s/-moz-margin-start\>/margin-inline-start/g
s/-moz-border-end\>/border-inline-end/g
s/-moz-border-end-color\>/border-inline-end-color/g
s/-moz-border-end-style\>/border-inline-end-style/g
s/-moz-border-end-width\>/border-inline-end-width/g
s/-moz-border-start\>/border-inline-start/g
s/-moz-border-start-color\>/border-inline-start-color/g
s/-moz-border-start-style\>/border-inline-start-style/g
s/-moz-border-start-width\>/border-inline-start-width/g
s/\<MozPaddingEnd\>/paddingInlineEnd/g
s/\<MozPaddingStart\>/paddingInlineStart/g
s/\<MozMarginEnd\>/marginInlineEnd/g
s/\<MozMarginStart\>/marginInlineStart/g
s/\<MozBorderEnd\>/borderInlineEnd/g
s/\<MozBorderEndColor\>/borderInlineEndColor/g
s/\<MozBorderEndStyle\>/borderInlineEndStyle/g
s/\<MozBorderEndWidth\>/borderInlineEndWidth/g
s/\<MozBorderStart\>/borderInlineStart/g
s/\<MozBorderStartColor\>/borderInlineStartColor/g
s/\<MozBorderStartStyle\>/borderInlineStartStyle/g
s/\<MozBorderStartWidth\>/borderInlineStartWidth/g
The diffs for the following files:
layout/style/nsCSSPropAliasList.h
layout/style/test/property_database.js
layout/style/test/test_value_computation.html
were then manually removed from the patch.
MozReview-Commit-ID: 8fbYnlZcn9U
(I'm not particularly keen on "Performance" as the label, but I can't
think of anything better right now.)
MozReview-Commit-ID: JrTCFYksX30
--HG--
extra : transplant_source : %00E%9ER%B9%29%D9%D3%01%16%A0%E0%A2N%F9%83%01%E5R%B0
This patch was generated by the command:
find . -name "*.css" -exec sed -i -f mozpropsub {} \;
in the root of a mozilla-central tree, with the file mozpropsub
containing the contents:
s/-moz-padding-end\>/padding-inline-end/g
s/-moz-padding-start\>/padding-inline-start/g
s/-moz-margin-end\>/margin-inline-end/g
s/-moz-margin-start\>/margin-inline-start/g
s/-moz-border-end\>/border-inline-end/g
s/-moz-border-end-color\>/border-inline-end-color/g
s/-moz-border-end-style\>/border-inline-end-style/g
s/-moz-border-end-width\>/border-inline-end-width/g
s/-moz-border-start\>/border-inline-start/g
s/-moz-border-start-color\>/border-inline-start-color/g
s/-moz-border-start-style\>/border-inline-start-style/g
s/-moz-border-start-width\>/border-inline-start-width/g
While I didn't manually review all the changes, I did review the list of
files, and manually reviewed the changes in the files that I thought
were more interesting.
Note that there are a few tests that should be fixed up as well, but
I'll do that in a later patch.
MozReview-Commit-ID: EiQTuuV0MNQ
userTypedClear was used for two cases:
1) to keep track of whether we were in the middle of a loadURI call. This use is replaced by inLoadURI, which is
more sane when using e10s (though it's hard to be precise there because we're sending all web navigation calls to
the content process and this introduces a degree of asynchronousness that we just have to live with...).
2) to keep track of whether we were between a network start and a corresponding network stop, and whether the user
typed since the load properly started. This is now tracked on a small object on the browser binding, which has
appropriately named method so we're not just incrementing some magic number but actually understand what
we're saying, and so the information we get out (did the user type since this load started or not?) makes sense.
Note that we're keeping userTypedClear in session store information in order to remain backwards compatible.
It becomes a simple boolean-stored-as-int (1 or 0) that indicates whether we quit/crashed/stopped while a load
was pending, or not.
MozReview-Commit-ID: 5NbmVueocC7
--HG--
extra : rebase_source : 55cd9f3513c0a985580957a5157d47853a8822bf
extra : source : 386b9c750bd2ed458112acd29eb72e4e1371af9d
userTypedClear was used for two cases:
1) to keep track of whether we were in the middle of a loadURI call. This use is replaced by inLoadURI, which is
more sane when using e10s (though it's hard to be precise there because we're sending all web navigation calls to
the content process and this introduces a degree of asynchronousness that we just have to live with...).
2) to keep track of whether we were between a network start and a corresponding network stop, and whether the user
typed since the load properly started. This is now tracked on a small object on the browser binding, which has
appropriately named method so we're not just incrementing some magic number but actually understand what
we're saying, and so the information we get out (did the user type since this load started or not?) makes sense.
Note that we're keeping userTypedClear in session store information in order to remain backwards compatible.
It becomes a simple boolean-stored-as-int (1 or 0) that indicates whether we quit/crashed/stopped while a load
was pending, or not.
MozReview-Commit-ID: 5NbmVueocC7
--HG--
extra : rebase_source : f87199c77094c24c132e6c88f751a5b5d5aa62f9
