This should not affect Firefox for Android the same as Desktop. We do not use Gecko to fetch favicons. We use the Android networking stack.
That said, we could look at finding ways to reduce the priority of the Android networking call, either with a handy-dandy API like the one Gecko supports, or some other way, such as making sure we wait for the Gecko pageload to complete before doing any Android networking. ----- Original Message ----- > Jason Duel called out in the platform engineering meeting that we have the > ability (and should use it) to set priorities on channels. Specifically he > called out bug 802573, where loading favicons was getting in the way of > loading pages, but suggested it be used anywhere where we're loading > something over the network that the user isn't specifically waiting for. > Code for setting it looks like this: > priorityChannel->AdjustPriority(nsISupportsPriority::PRIORITY_LOWEST); > where priorityChannel is an instance of nsISupportsPriority. > -Brad > _______________________________________________ > mobile-firefox-dev mailing list > [email protected] > https://mail.mozilla.org/listinfo/mobile-firefox-dev
_______________________________________________ mobile-firefox-dev mailing list [email protected] https://mail.mozilla.org/listinfo/mobile-firefox-dev
