Seeing an NSVO in CreateObjectsForEnvironmentChain indicates the shared
global namespace is about to be polluted, so fix those bugs and turn
this to a diagnostic.
MozReview-Commit-ID: 7OUef76geJL
--HG--
extra : rebase_source : 07d826101a498c54faab5c99dc475818cad58c4b
When using the subscript loader with JSM global sharing, it was possible
that subscript would pollute the global of all JSMs in the sharing.
MozReview-Commit-ID: 1ah5JUAZwBA
--HG--
extra : rebase_source : 202904e30b582c788ec440c406607ba98b8836e6
We want to be able to store scripts compiled with or without
non-syntactic support in cache when we toggle JSM global sharing. In
current code this script is cloned on execution, but with JSM global
sharing we have would hit assertions.
MozReview-Commit-ID: 2pVTTxLpx6S
--HG--
extra : rebase_source : 5913a43a2dfddf74187f08ab9c53babe377bd706
This allows js::ExecuteInJSMEnvironment to take a target object argument
as used by the subscript loader. This adds WithEnvironments with a
corresponding lexical on top of the ordinary NonSyntacticVariablesObject
environment chain.
MozReview-Commit-ID: JhHEfV92Zpv
--HG--
extra : rebase_source : d1ef9564d30a25fd9e1cf1ca7e95bf40c780dcdf
The excluded directories aren't being properly handled in the py2/py3 compat
linters. In order for FileFinder to apply the exclusions properly they need
to either be relative to or contained by the base.
This means that currently the following will work:
./mach lint -l py2 <topsrcdir>
./mach lint -l py2 testing/mochitest
But this is broken:
./mach lint -l py2 testing
This change fixes the compat linters so exclude paths will be made relative
to the FileFinder base before passing them in. Any exclude not contained by
the base is simply discarded as it won't be relevant to that FileFinder
instance anyway.
MozReview-Commit-ID: LJx97TvKlSa
--HG--
extra : rebase_source : b8f0cb20ec5a88a33c26ace699ed9216b070f443
This is fallout from the servo patch mentioned in this bug.
578381b9e7
MozReview-Commit-ID: FNkaSkRnafr
--HG--
extra : amend_source : 4eca7400c5fccb0417e93fabed3e51138c95f5d5
Take into account that a weak referenced element might have been destroyed
in the element staleness check.
An error is thrown when the reference object has been destroyed when
getting a weakrefs' pointer. We catch this, but element.isStale does
not take into account that the el argument in this case can be null,
or in this revision of the patch, undefined.
MozReview-Commit-ID: 7sr4YGhAotS
--HG--
extra : rebase_source : 995eeef4ec1b19bf100cb95c4dd343e947b1cf52
This is the desired behavior but as per comment 8, it breaks a few existing
distributions' titles so we'll display two lines for those distributions in
the upcoming changesets.
MozReview-Commit-ID: CKFbHXbs3HT
--HG--
extra : rebase_source : 90c3a58b05c1a6fcaff56e7524b3d0f6c851e9cd
This test causes both a failure and an error and we need to investigate
how to reuse the wptrunner session configuration when implicitly starting
a session.
MozReview-Commit-ID: 5k7nfevamZY
--HG--
extra : rebase_source : 6c00bf4505bd7da0b97dccd3eda61adc9efa874e
The WindowProxy screenX/screenY/outerWidth/outerHeight fields are
platform-independent longs, meaning the bitness of the system is not
taken into account. This is defined in WebIDL as "a signed integer type
that has values in the range [−2147483648, 2147483647]". This can be
represented with an i32 internally.
Additionally, the WebDriver specification says that we should accept
JSON Numbers as input. This means the input value can be either a float
or an integer. rustc_serialize handles this very badly and we first
need to extract the input as f64 because this is the most liberal type
(i.e. an integer can be coerced to a float without problem).
We then we cast the number to an i64 which trims off any decimals without
worrying that the number wraps. We then run bounds checks of an i32
and error if the number will not fit within the set range.
This patch expects the output from Marionette to be conforming.
MozReview-Commit-ID: CVdUZWh2t8X
--HG--
extra : rebase_source : 6780985703d5d5291eae508f9eb2fdec16c261cc
When maximizing the window we must restore it from iconified state or
exit fullscreen first. Likewise for minimizing the window, we must
exit fullscreen. For fullscreening the window we need to also restore
the window.
MozReview-Commit-ID: AOQX2cV2C75
--HG--
extra : rebase_source : 53f310cc261a9a411bc46a04dd50a160a930b5af
Mobile code now loads LoginManagerParent lazily, similar to
nsBrowserGlue on desktop, so we no longer need LoginManagerParent.login.
MozReview-Commit-ID: 8tnWnev344
--HG--
extra : rebase_source : f2e9d5e2be13156032d827ee67f960f96c87345c
Move the form fill event listeners out of browser.js and into
BrowserCLH.js, and update them to support chrome windows, so we can
handle form fill events for Fennec, custom tabs, and PWAs.
MozReview-Commit-ID: Fb5gWmGvxfE
--HG--
extra : rebase_source : 8c2d2086e8f612bd823a9b227c9a6b0a0fecee78
Use the BrowserCLH for PromptService startup, to consolidate startup
handling code and also to delay loading PromptService.
MozReview-Commit-ID: 25UgVH7wrrs
--HG--
extra : rebase_source : a47a50f81cbc21ba0aaee714fb1de8099d778450
Move `addLazyGetter` and `addLazyEventListener` utility functions from
GeckoViewStartup.js into GeckoViewUtils.jsm, so they can be used for
both Fennec and standalone GeckoView.
Also switch to "chrome-document-loaded" for loading
DownloadNotifications because that's later in the startup sequence.
MozReview-Commit-ID: 1caMtufkHGR
--HG--
extra : rebase_source : 0c3d92ee2426026d9ec2ad78d77b2c03aa247811
If the browser process is not running it doesn't make sense to try to
connect to it for another 60s. Instead error out immediately.
MozReview-Commit-ID: 64DTZfEfzQj
--HG--
extra : rebase_source : 9951b1a64cbd8b387c2bc5e1152de0a975dbbe77
Remove the last remaining references to the now-removed style editor
actor.
MozReview-Commit-ID: Kl5YJ5JR4vS
--HG--
extra : rebase_source : 5db2f7a53d865ee9b4099733d3916667f257d024
Our shutdown code needs this, so it can wait for sanitising to have actually finished before continuing further.
MozReview-Commit-ID: DGNgFrvYIXV
--HG--
extra : rebase_source : 7ec07f52f2b6dc619042233049f12cc722adb9dd
We don't actually support the find API on Android but we already have permission
strings for other desktop-only APIs under mobile/ (eg bookmarks and history).
Keeping these lists in sync with each other is going to be enough hassle as it
is, lets avoid trying to sync them with what's actually supported on each platform
and just keep the same list of permission strings.
MozReview-Commit-ID: 1A0jhtbMZiG
--HG--
extra : rebase_source : e26bf0f4add077422a8f1a3f1d4c89ce2ac2c3a7
Makes it easier to change the value should our detection be broken.
MozReview-Commit-ID: KXMjZVLXNg5
--HG--
extra : rebase_source : 3b9e9dc97d16df83d4d8a35320966b210cf71fca
It will allow to blacklist all NVidia Tesla and AMD UVD3 GPU.
MozReview-Commit-ID: LaJqyIj0Yau
--HG--
extra : rebase_source : aa93c4379181e2cb09733f0053de55bf64787ef6
This patch fixes a light height problem in records to align with the visual spec. Another issue is that on Linux the country warning message in edit address dialog is pushed to the next line, where it should be wrapped.
MozReview-Commit-ID: FZiBVKWLeMU
--HG--
extra : rebase_source : 97ac4cfba1042be01f9cba5e51b5831fef8b59c5
