Pages apparently do this to try to open to native apps, and that on Firefox
causes an error page to be shown if the app is not installed, which is pretty
bad.
Differential Revision: https://phabricator.services.mozilla.com/D68471
--HG--
extra : moz-landing-system : lando
This allows methods operating on the ranges to be moved to that struct.
To see where this leads to, consider the following reviews.
Differential Revision: https://phabricator.services.mozilla.com/D68217
--HG--
extra : moz-landing-system : lando
AudioWorklets are now functional for most use cases, and so it's time to allow
people to experiment.
PaintWorklets are not ready.
Differential Revision: https://phabricator.services.mozilla.com/D68320
--HG--
extra : moz-landing-system : lando
Pages apparently do this to try to open to native apps, and that on Firefox
causes an error page to be shown if the app is not installed, which is pretty
bad.
Differential Revision: https://phabricator.services.mozilla.com/D68471
--HG--
extra : moz-landing-system : lando
This code always intended to force wmode to be one of these modes (bug 1340276) but was not robust to unexpected wmode values (e.g. "default"). Unexpected values are now promoted to "direct".
Differential Revision: https://phabricator.services.mozilla.com/D66477
--HG--
extra : moz-landing-system : lando
As D66857 changes the timing of dispatch notification `main-media-controller-playback-changed`, which was dispatched asynchorously after playback state change via the mechanism of `MediaEventSource`.
Now this notification would be dispatched directly after we change the main controller's playback state, so we have to modify this test to ensure that we receive `main-media-controller-playback-changed` correctly.
Differential Revision: https://phabricator.services.mozilla.com/D67069
--HG--
extra : moz-landing-system : lando
The main controller is the only controller that can receive media control keys among all other controllers registered to the service, and it should always be the last controller which is playing.
Therefore, we would maintain a list which sorts the controllers based on the order of playing controller, and the last one (last playing controller) would be the main controller.
For example, if the controller A starts first, then B starts, B should be the main controller. But if A restarts later then A should become the main controler again.
Differential Revision: https://phabricator.services.mozilla.com/D66857
--HG--
extra : moz-landing-system : lando
When we remove a controller from the list of controllers, which is a `nsTarray`, the array needs to be reconstructed if the removed controller is not the first or last element of the array.
Eg. If we have a list of controllers, [A, B, C, ....., Z] and in some situation we would like to reoroder it to [A, C, D, ......, Z, B]. If we use nsTArray, then doing this kinds of reorder is expensive because it can't arbitrarily move the element back and forth, but the linked list can.
So we replace the `nsTArray` with `LinkedList`, then this operation would become `O(1)` which could improve the performance
Differential Revision: https://phabricator.services.mozilla.com/D66855
--HG--
extra : moz-landing-system : lando
Otherwise the user can select, but if you're in an iframe the iframe won't be
correctly focused.
This also matches other browsers, see:
data:text/html,<input autofocus><input disabled value=abc>
data:text/html,<input autofocus><button disabled>Foo</button>
And so on. This effectively undoes bug 375008. We could make this more targeted
somehow, but I don't think it's worth it.
Differential Revision: https://phabricator.services.mozilla.com/D67597
--HG--
extra : moz-landing-system : lando