Getting visited colors is relatively low priority during page load. GeckoView
was using a 250ms timer, which was somewhat arbitrary.
If this turns out not to be acceptable for desktop, we can change it to a higher
priority timer.
This enables batching queries from the content process. The lesser priority of
the queries, plus the batching that this enables on the content process I hope
will make a dent on the performance regression that bug 1506842 introduces
as-is.
We should probably introduce batching in the other direction too, both of those
are potential follow-up work.
Differential Revision: https://phabricator.services.mozilla.com/D51621
--HG--
extra : moz-landing-system : lando
Uses a tree.json file to configure the tree (will be moved in the yml file)
We also removed the python package doc from the landing page because :
* They are still accessible in the sidebar
* Hardly anyone is going to be looking for them (they are mostly useful to link to from other docs)
* They get in the way of the documentation below
Differential Revision: https://phabricator.services.mozilla.com/D51306
--HG--
extra : moz-landing-system : lando
This uses `Document.hasValidTransientUserGestureActivation` to expose
gesture for use in the `onLoadRequest()` delegate method in GeckoView,
allowing apps to know if a load was initiated by a user.
Differential Revision: https://phabricator.services.mozilla.com/D51729
--HG--
extra : moz-landing-system : lando
Remove mobile/android/extensions/ and /mobile/android/chrome/content from mozilla-central (Fennec leftovers)
Differential Revision: https://phabricator.services.mozilla.com/D51194
--HG--
extra : moz-landing-system : lando
Spoof dom/dom.properties, layout/xmlparser.properties,
layout/MediaDocument.properties to en-US if needed.
Differential Revision: https://phabricator.services.mozilla.com/D46034
--HG--
extra : moz-landing-system : lando
Behind a pref to ensure that we can turn this off pretty easily if it has perf
impact.
I want to leave the repainting stuff to another bug to land separately, to track
potential (though I hope not!) perf regressions more easily.
Differential Revision: https://phabricator.services.mozilla.com/D50704
--HG--
extra : moz-landing-system : lando
Spoof dom/dom.properties, layout/xmlparser.properties,
layout/MediaDocument.properties to en-US if needed.
Differential Revision: https://phabricator.services.mozilla.com/D46034
--HG--
extra : moz-landing-system : lando
The #text-overlay and #image child divs were "position: absolute" under
the main AccessibleCaret div. However, they don't necessary need to be
position:absolute to achieve the desired layout. We can make them normal
in-flow elements to simplify the frame structure. There should not be
any perceivable change to the user.
Also, AccessibleCaret's position can made more accurate by using float
CSS pixels when converting it from app unit.
Differential Revision: https://phabricator.services.mozilla.com/D51349
--HG--
extra : moz-landing-system : lando
The changes in bug 1583575 cause an additonal event to call the `ContentDelegate`,
so the test proceeds without waiting specifically for `onFullScreen` to be called.
This patch annotates the `onFullScreen` overrides to ensure that we're waiting
on the correct event for these test cases.
Differential Revision: https://phabricator.services.mozilla.com/D51195
--HG--
extra : moz-landing-system : lando
Remove some old Fennec documentation, re add in adjust and mma docs as they are still in use.
Examples are being moved to a new location and javadoc is already generated here and so these items are not being moved in this commit
Differential Revision: https://phabricator.services.mozilla.com/D48563
--HG--
extra : moz-landing-system : lando
Remove some old Fennec documentation, re add in adjust and mma docs as they are still in use.
Examples are being moved to a new location and javadoc is already generated here and so these items are not being moved in this commit
Differential Revision: https://phabricator.services.mozilla.com/D48563
--HG--
extra : moz-landing-system : lando
Otherwise a page which appends links with different hrefs fast enough could
never see the visited state updated, for example.
Depends on D50480
Differential Revision: https://phabricator.services.mozilla.com/D50501
--HG--
extra : moz-landing-system : lando
GeckoView does this link clearing stuff (which is somewhat dubious), but always
used to return NS_OK.
The error handling case in Link.cpp was pretty broken anyway (it'd leave the
link marked as registered), so make that infallible, given we fatally assert in
the non-android case.
NotifyVisited is also infallible so make that infallible too.
There's no need to use NS_IMETHOD gunk when not using scriptable XPCOM, and
these functions are not called from script, so make them regular pure-virtual
functions.
Depends on D50478.
Differential Revision: https://phabricator.services.mozilla.com/D50480
--HG--
extra : moz-landing-system : lando
Interestingly the android implementation had a potentially serious bug (was
missing a script blocker).
Differential Revision: https://phabricator.services.mozilla.com/D50263
--HG--
extra : moz-landing-system : lando
Now that there's only one android history implementation we can make it a static
component.
So do the same as toolkit/components/places/components.conf.
Differential Revision: https://phabricator.services.mozilla.com/D50180
--HG--
extra : moz-landing-system : lando
Emilio Cobos Álvarez
Sylvestre Ledru
James Willcox
Elliot Stirling
Thomas Wisniewski
Alex Catarineu
Mihai Alexandru Michis
Ting-Yu Lin
Nihanth Subramanya
Gijs Kruitbosch
Dorel Luca
Cosmin Sabou
Dragana Damjanovic
Aaron Klotz
Christoph Kerschbaumer
Andreea Pavel
Dylan Roeh
Razvan Maries
Daniel Varga
Emily Toop
Itiel
Ehsan Akhgari
Neil Deakin