Re: ARIA implementation plans (was Re: W3C Proposed Recommendations: WAI-ARIA and Core Accessibility API Mappings)

Thanks David Bolter, this helps a lot. On Thu, Nov 30, 2017 at 6:25 PM, David Bolter wrote: > Hi Tantek, > > I spun this off the rec proposals thread as per your suggestion. > > On Thu, Nov 30, 2017 at 8:58 PM, Tantek Çelik > wrote: >> >> On Thu, Nov

PSA: increased chance of new leaks due to delayed shutdown issue

Hi all, I just wanted to send a note about a bug in nightly which is leading to delayed shutdowns. Currently nightly is taking 5 to 10 seconds to shutdown. Bisection has shown this was introduced by my landing in: https://bugzilla.mozilla.org/show_bug.cgi?id=1419536 I have a fix here:

Re: W3C Proposed Recommendations: WAI-ARIA and Core Accessibility API Mappings

Hi Jonathan, On Thu, Nov 30, 2017 at 9:23 PM, Jonathan Kingston wrote: > > *Thoughts* > We should ensure ARIA provides clear justification for any other roles that > already have HTML representation. > I'm pretty sceptical of ARIA helping Accessibility. I think there is more >

ARIA implementation plans (was Re: W3C Proposed Recommendations: WAI-ARIA and Core Accessibility API Mappings)

Hi Tantek, I spun this off the rec proposals thread as per your suggestion. On Thu, Nov 30, 2017 at 8:58 PM, Tantek Çelik wrote: > On Thu, Nov 30, 2017 at 4:10 PM, L. David Baron wrote: > > [snip] > Two things: > > 1. Do we have an Intent to

Re: W3C Proposed Recommendations: WAI-ARIA and Core Accessibility API Mappings

*The changelog might be slightly jumbled.* The only involvement I had was with the password role. I think both lines should be removed from the changelog as they add confusion based on their current placements (it reads as if it was in 1.0 and since removed). *Thoughts* We should ensure ARIA

Re: W3C Proposed Recommendations: WAI-ARIA and Core Accessibility API Mappings

On Thu, Nov 30, 2017 at 4:10 PM, L. David Baron wrote: > Two W3C Proposed Recommendations are available for the membership of > W3C (including Mozilla) to vote on, before it proceeds to the final > stage of being a W3C Recomendation: > > Core Accessibility API Mappings 1.1 >

Re: Please do not use GetNativePath and GetNativeTarget in XP code and Windows-specific code

I think that we don't have any data when user doesn't use non-UTF-8 (and C) locale such as ja_JP.eucJP. We should get data via telemetry. -- Makoto On Thu, Nov 30, 2017 at 9:02 PM, Masatoshi Kimura wrote: > I intentionally ignored non-UTF-8 UNIX locales because our

W3C Proposed Recommendations: WAI-ARIA and Core Accessibility API Mappings

Two W3C Proposed Recommendations are available for the membership of W3C (including Mozilla) to vote on, before it proceeds to the final stage of being a W3C Recomendation: Core Accessibility API Mappings 1.1 https://www.w3.org/TR/core-aam-1.1/

Re: Please do not use GetNativePath and GetNativeTarget in XP code and Windows-specific code

> On Thu, Nov 30, 2017 at 11:09:07AM +1300, Karl Tomlinson wrote: >> The native bytes may not be valid UTF-8, and so if the >> character encoding is UTF-8, then there may not be a valid >> `path` that can be encoded to produce the same `nativePath`. Kris Maglione writes: > I think you

Re: Browser Architecture Newsletter 5

> > We have quite a bit of ongoing activity linked from > https://bugzilla.mozilla.org/show_bug.cgi?id=1147820 focused on APIs > exposed to web content (HTTP cache, cookies, localStorage, Indexed DB, > service worker registrations, etc.) and the associated UI exposed to > users. There should maybe

Re: Browser Architecture Newsletter 5

> On Nov 30, 2017, at 04:40, Anne van Kesteren wrote: > >> On Wed, Nov 29, 2017 at 9:47 PM, Dave Townsend wrote: >> If you’re working on improving storage or syncing of data in any of our >> products or projects, on any platform, or if you’re currently

Re: Intent to Remove: Insecure use of WebCrypto

On Fri, Jul 28, 2017 at 10:15 PM, Jonathan Kingston wrote: > Hey Tim, > > The only questions I have about this our are difference in implementation > over Chrome the more we increase the use of [SecureContext] the greater risk > we put on compat bugs. Good news, the

Re: Please do not use GetNativePath and GetNativeTarget in XP code and Windows-specific code

I intentionally ignored non-UTF-8 UNIX locales because our support for those locales is already half-broken and almost nobody cares about that. For example, OS.File assumes that the filesystem encoding is always UTF-8 on UNIX while nsIFile does not. This discrepancy caused a bug[1] that did not

Re: Intent to ship: CSS Shapes Module Level 1 (partial)

Thank you for all the feedback. I feel the safest plan is to ship the entire module at once. It also saves some work to implement two preferences to exclude the shape-outside: value which we don't render in the first stage. I'm implementing "shape-outside: ", and will do "shape-margin" after

Re: Browser Architecture Newsletter 5

On Wed, Nov 29, 2017 at 9:47 PM, Dave Townsend wrote: > If you’re working on improving storage or syncing of data in any of our > products or projects, on any platform, or if you’re currently struggling to > work with what currently exists, then we’d like to hear from you

Re: Browser Architecture Newsletter 5

Hi, The coherent thinking and communication about Browser Architecture is a really good change from before, thanks for that. On Wed, Nov 29, 2017 at 9:47 PM, Dave Townsend wrote: > We’ll be meeting to talk in more detail about the roadmap, the present, > and the future