Hi, Jim,
Makoto-san and I sometimes work on spellchecker if there are some urgent
bugs because of editor maintainers. However, at least I don't have much
time to work on it aggressively, and honestly, I'm not so familiar with
the detail of the implementation. Additionally, we do not speak
Hey all,
Somewhere along the way I managed to gain triage ownership of Core:Spell
checker. Thing is I've never worked with this code or non-english locale issues
which show up. A number of bugs also seem to be tied to DOM related issues
related to inline spell checking. Is there someone out
On 11/04/2019 18:22, Brian Grinstead wrote:
This has now landed (with initial support for xpcshell, mochitests, and web
platform tests). Thanks to Andrew Halberstadt and James Graham for improving
upon the initial prototype and making it easier to extend to new suites.
Eager users should
This has now landed (with initial support for xpcshell, mochitests, and web
platform tests). Thanks to Andrew Halberstadt and James Graham for improving
upon the initial prototype and making it easier to extend to new suites.
If the suite supports it (currently xpcshell and mochitests), we will
On Thu, Apr 11, 2019 at 7:45 AM Boris Zbarsky wrote:
> On 4/11/19 3:07 AM, Haik Aftandilian wrote:
> > With notarization, Nightly channel builds will not be debuggable unless
> the
> > system is booted with system integrity protection (SIP)[1] disabled.
>
> Do you know whether sampling via
\o/
Thank you for this!
On 2019-04-11 12:11 p.m., Bobby Holley wrote:
> TL;DR - In bug 1543241 (alias 'mach-busted'), we now have a central
> clearinghouse of bugs for broken mozilla-central tooling. You can invoke
> |./mach busted| to get a list of known outstanding issues, and |./mach
> busted
TL;DR - In bug 1543241 (alias 'mach-busted'), we now have a central
clearinghouse of bugs for broken mozilla-central tooling. You can invoke
|./mach busted| to get a list of known outstanding issues, and |./mach
busted file| to report a new one.
Few things burn up productivity quite like broken
On 4/11/19 3:07 AM, Haik Aftandilian wrote:
With notarization, Nightly channel builds will not be debuggable unless the
system is booted with system integrity protection (SIP)[1] disabled.
Do you know whether sampling via Activity Monitor's "Sample Process"
option or via Instruments will
*Summary*: We would like to experiment with Delegated Credentials, a
proposed TLS 1.3 extension. The Delegated Credentials mechanism allows
operators to delegate their own credentials for use in TLS 1.3, without
breaking compatibility with clients that do not support this extension.
Typically,
*Summary*: this allows web-developers to focus an element without scrolling
to it.
*Bug*: https://bugzilla.mozilla.org/show_bug.cgi?id=1374045
*Link to standard*:
https://html.spec.whatwg.org/#dom-focusoptions-preventscroll
*Platform coverage*: all platforms.
*Estimated or target release*:
Could you perhaps tell us more about the corruption? I recently had the
contents of a file corrupted, and after several attempts to fix it myself I
just recloned the repository. I suppose I'm not the only one who
encountered the problem, and most people probably didn't report it.
Yaron
On Fri,
On 2019-04-09 11:00 a.m., Gian-Carlo Pascutto wrote:
On 5/04/19 15:35,jma...@mozilla.com wrote:
Currently linux32 makes up about .77% of our total users. This is
still 1M+ users on any given week.
I asked jmaher what percentage of our Linux users this is. It's 21%.
This doesn't seem small.
Update on our adoption of Notary Service and its debugging impact:
With notarization, Nightly channel builds will not be debuggable unless the
system is booted with system integrity protection (SIP)[1] disabled. In my
earlier mail[2] to dev-platform about our adoption of the Notary Service, I
13 matches
Mail list logo
