There hasn't been any traction on this feature, and we keep
paying the maintenance and code size and memory usage penalty
of having this implementation.
We can revive this from VCS history in the future if we decide
to start working on it again. In the mean time, it's better
to remove it.
This patch adds a pref to control whether we dispatch the selection
events for changes in the contents of input and textarea text controls.
The spec for this feature hasn't been written yet, and we need to exclude
this part of the selection API from the part we want to ship.
If "media.libavcodec.allow-obsolete" is set to true, the checks for older
libavcodec library versions are ignored.
MozReview-Commit-ID: HBhHfFomsrr
--HG--
extra : rebase_source : 6bfe06bd4354fcda90d7d33bedcbd176663cab31
If libavcodec is present but cannot be used, Decoder Doctor sends a distinct
notification to better help the user find the issue.
MozReview-Commit-ID: IGXPIY1b8AS
--HG--
extra : rebase_source : e2884e442f611464bd995e0b2d8b32bec05a148a
This patch adds a new pref, which controls the minimum velocity required on a fling
for it to accelerate a previous fling. This makes it so that a fast fling followed
by a very slow fling doesn't get accelerated. Also, update the AndroidAPZ code
to respect the pre-existing fling acceleration interval pref, which disallows
fling acceleration/flywheel if the two flings are too far apart in time.
MozReview-Commit-ID: 7sn57CufPZ4
This patch adds a new pref, which controls the minimum velocity required on a fling
for it to accelerate a previous fling. This makes it so that a fast fling followed
by a very slow fling doesn't get accelerated. Also, update the AndroidAPZ code
to respect the pre-existing fling acceleration interval pref, which disallows
fling acceleration/flywheel if the two flings are too far apart in time.
MozReview-Commit-ID: EfBUx5UV6VG
If "media.libavcodec.allow-obsolete" is set to true, the checks for older
libavcodec library versions are ignored.
MozReview-Commit-ID: HBhHfFomsrr
--HG--
extra : rebase_source : 2f42348018b19d20be64001df737b342e1813274
If libavcodec is present but cannot be used, Decoder Doctor sends a distinct
notification to better help the user find the issue.
MozReview-Commit-ID: IGXPIY1b8AS
--HG--
extra : rebase_source : 101937fe8786296443b04d32983ccf260b23742a
On Windows, the contextmenu event is fired when the finger is lifted after a
long-press. However, there are various bits of code, such as the AccessibleCaret
or potential fixes for bug 1147335, which would benefit from knowing when the
long-press gesture was detected. By moving eMouseLongTap event up we can satisfy
that need. An alternative approach considered was to fire the eMouseLongTap
before the contextmenu on all platforms unconditionally, but that makes it harder
to implement platform-specific text selection behaviour the way we want. In
particular we would have to add an extra message or notification for non-Windows
platforms that initiated text selection if the contextmenu event was not
consumed.
MozReview-Commit-ID: 2lmwxmmGrVD