The multiplage version of the spec (for folks with slower machines):
https://html.spec.whatwg.org/multipage/interaction.html#dom-focusoptions-preventscroll
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/d
I think it's not easy to do that for some modules. E.g., starting from
Firefox 57, we removed a lot of XPCOM interfaces/objects. That caused
redesigning some implementation around them (for making simpler and
faster). Additionally, some refactoring must have been done in the
period. For exampl
Hi,
I know this sounds like a strange questions. However, we have a very large
customer who is using our old OS which the last successful build of Firefox ESR
was 52.9. But because of the massive updates to FF 60 we have been unable to
get FF 60+ to build on that old OS. This customer has deman
./mach python-test testing/xpcshell/selftest.py
-hb-
On 2019-04-12 20:48, Honza Bambas wrote:
After I installed all the necessary packages (mozinfo, mozunit,
pytest, mozbuild, which, mach, mozversioncontrol) I'm getting:
`mozbuild.base.BuildEnvironmentNotFoundException: Could not find
Mozilla
On 12/04/2019 10:04, Makoto Kato wrote:
But I am already triage owner of some components (editor, i18n and
GeckoView's input), so I hope that anyone takes ownership of spellchecker
for triage/module. If no one handles it, I can handle triage process as
temporary due to low volume until new owner
After I installed all the necessary packages (mozinfo, mozunit, pytest,
mozbuild, which, mach, mozversioncontrol) I'm getting:
`mozbuild.base.BuildEnvironmentNotFoundException: Could not find Mozilla
source tree or build environment.`
mozinfo.json is missing in my tree, here I got stuck.
Thanks
This came up in
https://groups.google.com/d/msg/mozilla.dev.platform/eptWENSn4wM/sjCWfj1LBwAJ:
> On Apr 1, 2019, at 12:38 PM, Brian Grinstead wrote:
>> On Apr 1, 2019, at 12:15 PM, Boris Zbarsky wrote:
>> I do have one other question on the templates: for mochitest-plain, add_task
>> is a pret
There have been a few recent changes related to wpt that may be of
interest to a wider audience; for brevity I'm coalescing them into a
single email:
* New wpt dashboard focused on interop problems
* Support for fuzzy annotations in reftests
* Better support for debugging failing reftests on wp
Several spellchecker issues are related to editor and input, so I sometimes
look spellchecker issue since it is related to editor.
But I am already triage owner of some components (editor, i18n and
GeckoView's input), so I hope that anyone takes ownership of spellchecker
for triage/module. If no
9 matches
Mail list logo