This favors Rust, but there's no way to generate different names in the
bindings, as far as I know.
Differential Revision: https://phabricator.services.mozilla.com/D69395
--HG--
extra : moz-landing-system : lando
TRACE_AUDIO_CALLBACK() and TRACE_AUDIO_CALLBACK_COMMENT(aFmt, ...) log to a hardcoded thread id number. This creates confusion when more than one MTG is running because logs from different threads are depicted to the same thread line and overlapping each other. Those logging commands have been removed and the TRACE* command is used that it logs per thread-id.
Differential Revision: https://phabricator.services.mozilla.com/D69031
--HG--
extra : moz-landing-system : lando
There is no need to use the Git repository, its only change compared to 0.1.6
is that some random tidbit has been fixed in the README file.
Depends on D69805
Differential Revision: https://phabricator.services.mozilla.com/D69806
--HG--
extra : moz-landing-system : lando
This basically allowed managing a bunch of scroll data things in parallel
for all the render roots which we don't need anymore.
Differential Revision: https://phabricator.services.mozilla.com/D69845
--HG--
extra : moz-landing-system : lando
- Added test for html preview
- First pass at damp test for rendering response sidepanel
Differential Revision: https://phabricator.services.mozilla.com/D67831
--HG--
extra : moz-landing-system : lando
CLOSED TREE
Backed out changeset 34ebd6260867 (bug 1550037)
Backed out changeset 7571e5bc19e7 (bug 1550037)
Backed out changeset 71fdead8eecb (bug 1550037)
Actually, current code gets type attribute by `GetAttr`, But this cannot get
valid value. If no type attribute, `mHTMLInputType` will be empty. So if type
has invalid value, we should return `text` value instead.
Depends on D69349
Differential Revision: https://phabricator.services.mozilla.com/D69350
--HG--
extra : moz-landing-system : lando
Actually inputmode attribute exposes <input> element only, current WHATWG spec
allows all HTML element. So inputmode in input context should be always set.
Also, if using contenteditable, this attribute is only used on editing host when
using other browsers (Blink and Webkit). It is
https://github.com/whatwg/html/issues/5322.
Depends on D69348
Differential Revision: https://phabricator.services.mozilla.com/D69349
--HG--
extra : moz-landing-system : lando
`inputmode` attribute controls software keyboard layout like `<input type>`.
Originally this was by B2G (bug 746142) and for `<input>` element only.
WHATWG spec allows this attribute for HTML element and WebKit and Blink have
already implemented this.
Differential Revision: https://phabricator.services.mozilla.com/D69348
--HG--
extra : moz-landing-system : lando
Now that multi-value is code-complete, we enable it on nightly browsers
in addition to shell builds.
Differential Revision: https://phabricator.services.mozilla.com/D68791
--HG--
extra : moz-landing-system : lando
In mozilla::ipc::SharedMemory, the memory() method was virtual, so we cached the address here
(although the compiler would likely have inlined the accessor as the `final` concrete subclass
was known). Anyhow, in base::SharedMemory it's a trivial (non-virtual) accessor, so there's
no sense in shadowing it here.
Differential Revision: https://phabricator.services.mozilla.com/D68789
--HG--
extra : moz-landing-system : lando
The base::SharedMemory class provides APIs to create a "read-only" copy of a shared memory block,
which means it can be shared to a child process without the risk that the child might map it as
writable and corrupt the contents. We want to use this facility for the font list, hence switching
the shared-memory APIs used.
Differential Revision: https://phabricator.services.mozilla.com/D68778
--HG--
extra : moz-landing-system : lando
CLOSED TREE
Backed out changeset f7bda197d6b9 (bug 1627248)
Backed out changeset cc6e408e477c (bug 1627248)
Backed out changeset f6ca42417f92 (bug 1627248)
I wanted to assert that the most derived type of all GC things had standard layout type; sadly this was not true. The restrictions are quite strong, and I don't think this is realistic. However we can assert that the base GC thing type meets the restrictions with one minor change and I think that's most of the way there.
Depends on D69575
Differential Revision: https://phabricator.services.mozilla.com/D69835
--HG--
extra : moz-landing-system : lando
On Mac, ctrl-click will send a context menu event from the widget, so we don't
want to bring up the panel when ctrl key is pressed.
Differential Revision: https://phabricator.services.mozilla.com/D66439
--HG--
extra : moz-landing-system : lando
On Mac, ctrl-click will send a context menu event from the widget, so we don't
want to bring up the panel when ctrl key is pressed.
Differential Revision: https://phabricator.services.mozilla.com/D66414
--HG--
extra : moz-landing-system : lando
On Mac, ctrl-click will send a context menu event from the widget, so we don't
want to bring up the panel when ctrl key is pressed.
Differential Revision: https://phabricator.services.mozilla.com/D66397
--HG--
extra : moz-landing-system : lando
On Mac, ctrl-click will send a context menu event from the widget, so we don't
want to bring up the panel when ctrl key is pressed.
Differential Revision: https://phabricator.services.mozilla.com/D66384
--HG--
extra : moz-landing-system : lando