Make LayerViewSupport, NPZCSupport, GeckoEditableSupport, and
SessionAccessibility use the new disposal mechanism to ensure the
disposal is performed safely.
Differential Revision: https://phabricator.services.mozilla.com/D7110
--HG--
extra : moz-landing-system : lando
Add a test for the crash scenario where PZC is used after content
crashes and restarts.
Differential Revision: https://phabricator.services.mozilla.com/D7108
--HG--
extra : moz-landing-system : lando
Fennec will continue to require this. While we're here, also make 'touchscreen' feature optional.
Differential Revision: https://phabricator.services.mozilla.com/D7125
--HG--
extra : moz-landing-system : lando
Don't update the focused node in the node cache during auto-fill focus
events, because we don't necessarily know if the focused node should be
in the node cahce (e.g. the focused node could be from another window
than the one we're handling currently).
Differential Revision: https://phabricator.services.mozilla.com/D6758
This is necessary because the GC root for GeckoEditable is a native
reference, preventing the GC from recognizing that the only reference
to the GeckoEditable is the owning GeckoSession and doing normal
cycle collector stuff. We break the cycle ourselves by using a
WeakReference to hold the GeckoSession within GeckoEditable.
This patch prevents Fennec/GeckoView crash reporters from sending the large,
useless StackTraces field when submitting a report. I've also taken the
liberty of removing an obsolete crash annotate that was being added to
Fennec's reports.
Differential Revision: https://phabricator.services.mozilla.com/D6389
--HG--
extra : moz-landing-system : lando
Add a flag for whether the session should be pinned to the screen. The
app would check the flag and prevent scrolling of the session when it's
pinned.
Differential Revision: https://phabricator.services.mozilla.com/D5190
Hide the selection action toolbar when the session is unfocused, or when
changing the selection action delegate.
Differential Revision: https://phabricator.services.mozilla.com/D5807
--HG--
extra : moz-landing-system : lando
If we're trying to detach and reattach the same compositor object for
whatever reason, we should skip it so we don't inadvertently end up not
attaching the object at all.
Differential Revision: https://phabricator.services.mozilla.com/D5608
--HG--
extra : moz-landing-system : lando
If we're trying to detach and reattach the same compositor object for
whatever reason, we should skip it so we don't inadvertently end up not
attaching the object at all.
Differential Revision: https://phabricator.services.mozilla.com/D5608
--HG--
extra : moz-landing-system : lando
To make the test work properly, there needs two functions. One is just setting
a value for testing and sending the notificaiton for the value changes, the
other one is to reset the state for testing.
The test itself will be introduced in bug 1486971, especially in
https://phabricator.services.mozilla.com/D5004
Depends on D5503
Differential Revision: https://phabricator.services.mozilla.com/D5504
--HG--
extra : moz-landing-system : lando
Because we are going to use it for prefers-reduced-motion media feature which
is tied to a system setting.
Differential Revision: https://phabricator.services.mozilla.com/D5502
--HG--
rename : mobile/android/geckoview/src/main/java/org/mozilla/gecko/GeckoInputDeviceListener.java => mobile/android/geckoview/src/main/java/org/mozilla/gecko/GeckoSystemStateListener.java
rename : widget/android/GeckoInputDeviceListener.h => widget/android/GeckoSystemStateListener.h
extra : moz-landing-system : lando
Though we can't write automation tests for this, I have confirmed that the input
device added/removed are properly notified to 'browser.xul'. Unfortunately the
notifications don't reach to conent documents because of bug 1478212, but I've
also confirmed they did reach to content documents with replacing
MediaFeatureValuesChanged with MediaFeatureValuesChangedAllDocuments in
nsPresContext::RefreshSystemMetrics().
Differential Revision: https://phabricator.services.mozilla.com/D3303
There is no API that we can tell which input device is the primary pointer
device on Android, so we assume that the first pointer-type input device
in the list of InputDevice.getDevice is the primary one.
Test results on L-01F (a variant of LG-G2):
- Normal boot
The touchscreen is the primary device
- Plugged a mouse
The touchscreen is the primary device
- Boot with a plugged mouse
The mouse is the primary device
- Plugged off the mouse
The touchscreen is now the primary device
- Plugged the mouse again
The touchscreen is the primary device
Classification in getPointerCapablities refered to chrome impelementation [1].
In addition to the classification, we add SOURCE_JOYSTICK as a 'COARSE' and
'HOVER_CAPABLE' device.
[1] d4c8983688/ui/android/java/src/org/chromium/ui/base/TouchDevice.java (72)
Differential Revision: https://phabricator.services.mozilla.com/D3302
Summary:
This also moves GeckoDisplay-related things out of LayerSession
and into GeckoSession. Additionally, we try to make sure
GeckoSession has only one attached GeckoDisplay.
Reviewers: jchen, droeh
Tags: #secure-revision
Bug #: 1486778
Differential Revision: https://phabricator.services.mozilla.com/D4449
