The datepicker is showing incorrect year-month header in some time zones, which
is similar to Bug 1331608. It's now fixed by setting the DateTimeFormat timeZone
to UTC. Also done the same thing to the year display for consistency.
MozReview-Commit-ID: LGghmPfYQ5j
--HG--
extra : rebase_source : f1b512d36f46e1f77537d2a5371f45dec72b625e
Currently mouseover autocomplete item would not change the selectedIndex
of popup but show grey highlight. For form autofill, we don't want
two indicators to represent the selection of keyboard and mouse
separately that might confuse user which profile preview is exactly
being shown. I added a new <field> in formautofill profile item binding
that helps autocomplete to determine whether to change selectedIndex
when mouseover.
MozReview-Commit-ID: LmW8g08V9mf
--HG--
extra : rebase_source : e0af703a4a6291c53995fd00319bf8a6b259109c
Currently mouseover autocomplete item would not change the selectedIndex
of popup but show grey highlight. For form autofill, we don't want
two indicators to represent the selection of keyboard and mouse
separately that might confuse user which profile preview is exactly
being shown. I added a new <field> in formautofill profile item binding
that helps autocomplete to determine whether to change selectedIndex
when mouseover.
MozReview-Commit-ID: LmW8g08V9mf
--HG--
extra : rebase_source : 7589bed96c088919ebbdeb6c87fe6e18a679f657
Redirect the link to about:preferences#privacy-reports
MozReview-Commit-ID: HIq9zpT6Jz9
--HG--
extra : rebase_source : 8393573834367174ef743c09470f74c22e1ccbdd
Allow the use of the subsection render not just for the environment data.
It could help future developer to display subsection for another special
ping data. Also it will help with the redesign of the UI.
MozReview-Commit-ID: DHoS7Zw7IyC
--HG--
extra : rebase_source : a6ca4c0218c5b73c4c3e383886c9e94ec3f7f93d
GenericTable expect an array of array as data where KeyValueTable used to expect an object.
Use explodeObject() to process an object so it can be used by GenericTable.
MozReview-Commit-ID: 6hxxFwF2KXg
--HG--
extra : rebase_source : 29b2636eeea2f980182e5127f1e3f98630188e10
Both provide the same functionality so we only need to keep one of them.
MozReview-Commit-ID: AOiiRiFr1fD
--HG--
extra : rebase_source : 8e3b8d3f80c320f4a40fa4b5ba383fc323d15806
Most of the sections were already in their own object. This fixes the one that are not.
MozReview-Commit-ID: 92lAtwYwbDl
--HG--
extra : rebase_source : 8f1ad8d7e5fe18958858130bde8eb542782ad61a
Introduce the replacement of KeyValueTable by GenericTable.
Both provide the same feature so we only need one.
MozReview-Commit-ID: AyWKPkrlX64
--HG--
extra : rebase_source : 20547cab0a53f2e122f0cebdcac3eb3f24eedde1
This is a Linux-specific feature and other platforms don't have it (see also
the conditional in Troubleshoot.jsm and the ifdef in aboutSupport.xhtml).
MozReview-Commit-ID: IISzOvWXwCp
--HG--
extra : rebase_source : d57c2b42003619ed13a5bb6afe219d16c5d575ae
Disable toolkit/content/tests/widgets/test_popupanchor.xul on linux machines as it permanently fais when running with Ubuntu 16.04.
MozReview-Commit-ID: HSX6xC8dG8k
--HG--
extra : rebase_source : c270b3456c92da2b49daa30cf44308b6880f5ea9
Disable toolkit/content/tests/chrome/test_panel_anchoradjust.xul on linux machines as it permanently fails when running on Ubuntu 16.04.
MozReview-Commit-ID: FOW9zgKYcAU
--HG--
extra : rebase_source : a590ff1dec5abd04ac97efcf03e4bcd61612626a
This patch removes the C++ code used to run the minidump analyzer when a
content process crashes, and replaces it with JS code within the CrashService
object. This removes the need for a separate shutdown blocker in C++ code and
allows end-to-end testing of the crash service functionality. Additionally
the exception handler code can be simplified since it's now only used to run
the crash reporter client.
The test added to test_crash_service.js covers computing the minidump SHA256
hash (bug 1322611) and of the minidump analyzer itself (bug 1280477).
MozReview-Commit-ID: LO5w839NHev
The browser-chrome test suite now detects and reports unhandled rejections of native Promises, in addition to those created by Promise.jsm. The whitelisting mechanism is updated to use primarily the PromiseTestUtils.expectUncaughtRejection function. Tests will fail if a rejection that is not whitelisted occurs, or if a whitelisted rejection does not occur anymore.
MozReview-Commit-ID: 1beGB5GG8Ty
--HG--
extra : rebase_source : 64395c5fdf25deebd60dfbf2cf5df3cbf7ca8abb
extra : amend_source : 0a3f13419c050662680f2bd110d724b3bf991732
extra : source : 8d53be05afc59519c5ce8cfae96d284a972fda71
The browser-chrome test suite now detects and reports unhandled rejections of native Promises, in addition to those created by Promise.jsm. The whitelisting mechanism is updated to use primarily the PromiseTestUtils.expectUncaughtRejection function. Tests will fail if a rejection that is not whitelisted occurs, or if a whitelisted rejection does not occur anymore.
MozReview-Commit-ID: 1beGB5GG8Ty
--HG--
extra : rebase_source : 59e5b84cb431f3ca28287d30a3da8fbea1363ec5
This includes 2 things:
1. Replacing the parts which test the logs for the presence of prefixes by testing
the returned map for `suceeded`.
2. We don't need to wait to observe the topic anymore, we can simply await methods
from `PlacesDBUtils` to know when they are done.
MozReview-Commit-ID: Ct9l9pzUW5x
--HG--
extra : rebase_source : 657e4ac53f8b3785740a5b732d483fad9600f73d
safe
We could also test ping.environment.addons before using it.
MozReview-Commit-ID: 1z6NdLPTBqN
--HG--
extra : rebase_source : c5ec4d189cf0d2d7bb67e335c06f678dd53d335d
randomly firing a 'pause' event when the test isn't expecting it. r=jaws
MozReview-Commit-ID: 65NrpKbIxi7
--HG--
extra : rebase_source : 7e1ec55d5c23b8c0cfa49ca5298d77fef77a2e4b
Previous design allows us calling resume/block from both front-end and back-end,
it's not easy to know who called these operations.
So move all these logic to frond-end side, it's more clear than before.
One important thing is that we should block tab before loading the content.
If we block the tab after loading, the media might not be blocked because it had
already started (that is one situation I observed from test).
The value of block state would be stored in the outer window, before media want
to start, it would check this value to know whether it can start playing or not.
---
In addition, introduce new attribute "media-blocked".
The "media-blocked" attribute indicates that whether the tab is allowed to play autoplay media.
The "activemedia-blocked" attribute indicates whether the tab has blocked the autoplay media.
MozReview-Commit-ID: FnNh3zmItxo
--HG--
extra : rebase_source : cdc890c0c47a4a03ea8dbbdfee24c66b52945c60
The "blocked" attribute is too general to indicate the real usage, so rename it
to "activemedia-blocked".
This attribute indicates that whether the tab has blocked the autoplay media.
MozReview-Commit-ID: EAmq6OuBYjq
--HG--
extra : rebase_source : e8e9321854b80736f0959fbfecbc8bf9a83b0712
The "platform" chrome flag requires an irrelevant "content" chrome
manifest entry, while it's only used for locales. It only has exactly
one use, which can actually be replaced by uses of the "os" flag.
Note, we're doing something similar with the "os" flag for skins in
e.g. browser/extensions/pocket/jar.mn.
Unfortunately, for determinism reasons, the chrome manifest entries from
jar.mn are sorted (per bug 982075), so keeping global-platform/unix
would leave it appearing after /mac, and would override it on mac
because of the lack of "os" flag on the /unix entry (we can't put "os"
flags on that entry because we can't do something like os!=Darwin &&
os!=WINNT). So we move it to /gtk such that it always comes before /mac.
--HG--
extra : rebase_source : aaace8147ea54f74aef8a7b2314ad022e9f9be23
This intentionally allows to set MOZ_INSTALL_TRACKING without
reference to the milestone being release or beta. That is, we
separate the default value (which depends on release or beta) from the
value specified, making life easier for developers.
MozReview-Commit-ID: 3vPF7KO7fEX
--HG--
extra : rebase_source : 8d5764104b5322a32e4a048bfd3222f62fed73bb
This patch uses the new Photon animation curve for notification bars as well
as supporting `toolkit.cosmeticAnimations.enabled` to disable the animations
on notification bars entirely.
MozReview-Commit-ID: AHSQR32g6hf
--HG--
extra : rebase_source : 9b643a758db07791dbda12f7e6383f193f3fa698
__define{Getter,Setter}__ are deprecated, and are not defined on
NonSyntacticVariablesObjects, so these calls get in the way of sharing
globals between different .jsms. Probably only the DownloadUtils.jsm
change is really needed for that.
configurable and enumerable are both set to true to match the existing
behavior. If enumerable is set to false, then tests fail, because some
of the getters overwrite the getter with a regular property.
MozReview-Commit-ID: 1OZF45fIAQ
--HG--
extra : source : 96dd2e2d8d1677fb04c98bb3a063df32478fbc00
Reset button should not be tabbable or focusable.
MozReview-Commit-ID: IboMKl3n0LY
--HG--
extra : rebase_source : 7bec15cfb601cd15a99d26e39b39446ef3ca5601
This patch creates a new print preview browser to host the simplified cloned-document
when Simplify Page option is used on preview. Also, this patch keeps track of what browser
should be presented, based on whether the 'Simplify page' checkbox is checked.
MozReview-Commit-ID: FZSRUyC49Wk
With ideas and code from Oriol <oriol-bugzilla@hotmail.com>.
MozReview-Commit-ID: CjuCAkYaort
--HG--
extra : rebase_source : dd53d1a665a5aba8ef094ee82dffe9c6c010d3d6
This patch creates a new print preview browser to host the simplified cloned-document
when Simplify Page option is used on preview. Also, this patch keeps track of what browser
should be presented, based on whether the 'Simplify page' checkbox is checked.
MozReview-Commit-ID: FZSRUyC49Wk
--HG--
extra : rebase_source : cccc12f17f315089c9e5d05116077b7f87f4053b
The APZ scrolling codepath doesn't do the right thing for <listbox>
without special handling, so have it scroll in JS instead, like we
did in bug 1302736 for <tree>.
MozReview-Commit-ID: LWJCBfhZ3Hc
--HG--
extra : rebase_source : bb8b2f7e713d35822a956e08f4e0eed0557b07b3
Opening pages in a new tab might suffer an extra delay from e10s-multi because
the new process has to start up and then run all the process / frame scripts
before it can react on the request from the parent to load the first page.
There are two code paths. Either we start the tab with a remote browser and
then the RemoteWebNavigation will send the request. Or we start with a non-remote
browser and have to change the remoteness flag on it, and then the SessionStore
will send the request.
In each cases we start the timer on the parent side, send it with the message,
and when the child receives it it stops the timer and reports the measured delay.
We can lower the eslint cyclomatic complexity threshold in some directories without adding eslint suppression comments in any .js source files. We need to specify the complexity rule in accessible/.eslintrc because it doesn't inherit the mozilla/recommended rules. eslint's default complexity threshold is 20.
Also bump the eslint-plugin-mozilla version because we modified the mozilla/recommended rules.
MozReview-Commit-ID: 57T4gAjPH7z
--HG--
extra : rebase_source : 4565abfa722b9459cfb4e006e843da13ed7cffd4
extra : intermediate-source : 658588564c08c9fd5e60633d1457f24087de8570
extra : source : 7e0526e3b943419a80c0cd2fa462cabbf8925eb1
Changlist:
- Added Jim Palmer's well proven natural sort algorithm.
- Added natural sort license (MIT).
- Use natural sort everywhere inside TableWidget.js wherever we use .sort()
- Changed browser_storage_overflow.js so that the test is faster and more maintainable. The test now also tests column sorting (ascending and descending).
- Use natural sort everywhere inside storage.js wherever we need to slice the array. Without natural sort here we get e.g. row-1, row-10, row-100, row-2 etc.
MozReview-Commit-ID: FUY7pcLIYml
--HG--
extra : rebase_source : 6e25cc962a7ab89aeb361e4036af90dcecd24b02
The about:url-classifier supports following functions:
1. Provider section
- Show update status for each provider, update status include
last update time, next update time and last update status
- Update button to manually trigger an update for the provider.
2. Debug section
- Set MOZ_LOG Modules
- Set MOZ_LOG_FILE
MozReview-Commit-ID: AHiveKEHSNC
--HG--
extra : rebase_source : b56e918de7f4eb30ad8eebc6d24ffaf2e76f4f4e
This patch creates a new print preview browser to host the simplified cloned-document
when Simplify Page option is used on preview. Also, this patch keeps track of what browser
should be presented, based on whether the 'Simplify page' checkbox is checked.
MozReview-Commit-ID: 77pLXhdbpPp
--HG--
extra : rebase_source : 7201f230299c571d6c3a86ce650d6852c43e0943
We could register media control related event after the tab has active media.
But we still need to register "audioFocusChange" in the beginning, because it
affect every tab even the tab has no active media.
MozReview-Commit-ID: ErIBUobnxbg
--HG--
extra : rebase_source : bdc8070f2f2a81f847ebb8e0ec87f6efeb86eb80
The scroll destination of the smooth scroller of <scrollbox> can be outside of the actual scrollable range. Therefore, it doesn't make scroll slower even when the end appears.
This patch makes the destination always in the scrollable range.
MozReview-Commit-ID: CfEGzhG7Jh7
--HG--
extra : rebase_source : 87a07140a1ce58752ac264a1e8decb2a8af6d078
