Re: Proposed W3C Charter: Web Payments Working Group

On 1/8/18 10:17 PM, mcace...@mozilla.com wrote: > > >> On Jan 9, 2018, at 4:29 AM, L. David Baron wrote: >> >> Please reply to this thread if you think there's something we should >> say as part of this charter review, or if you think we should >> support or oppose it.

Intent to Unship: Application Cache over Insecure Contexts

AppCache is a powerful feature on the web that permits a web page to be viewed offline. This increases the risk that a user is unaware of the source of the web page content when browsing over HTTP. Besides fundamental issues with AppCache, which are summarized in this article

Re: Password autofilling

It seems we are in a bad position here. There's two vectors: The browser and the website are collaborating to mitigate tracking by a third party. The third party makes an invisible login form - well we can restrict autofill to only visible elements. Or make a write-only form field that prevents

Re: [dev-servo] PSA: Avoid invoking Debug formatters in release-mode Rust

That being said, looking at nsCSSParser.cpp in Gecko, I just realised you never had similar code (printing values when some invariant is broken). Given how old Gecko is, I guess that means this is not even useful to begin with (I mean the printing you removed was not useful to begin with, just

Re: Password autofilling

I wanted to follow up to make it clear what the change would look like. Here is what autofill population looks like: ​ Here is what the it looks like after autofill is disabled: This then becomes consistent with Private Browsing mode and HTTP sites already work. This is also consistent with how

Re: Proposed W3C Charter: Web Payments Working Group

> On Jan 9, 2018, at 4:29 AM, L. David Baron wrote: > > Please reply to this thread if you think there's something we should > say as part of this charter review, or if you think we should > support or oppose it. (Given our involvement, we should almost > certainly say

Reminder: Nightly 59 Soft Code Freeze: Jan 11th - Jan 22nd 2018

Hello, This is a reminder that *Soft Code Freeze for Nightly 59 starts (this week) on Jan 11th, 2018*. It will end on Jan 22nd, 2018. We have been using the soft code freeze milestone since Fx55 to help minimize disruptions to Nightly quality and to increase the likelihood of shipping a high

Re: Please stop using keypress event to handle non-printable keys

On 18/01/2018 17:36, Mark Banner wrote: On 18/01/2018 16:56, Nicholas Alexander wrote: On Wed, Jan 17, 2018 at 6:34 PM, Masayuki Nakano > wrote: Hello, everyone. Please stop using keypress event for handling non-printable keys

Re: Please stop using keypress event to handle non-printable keys

On 18/01/2018 16:56, Nicholas Alexander wrote: On Wed, Jan 17, 2018 at 6:34 PM, Masayuki Nakano > wrote: Please stop using keypress event for handling non-printable keys in new code when you write new code and new automated tests.

Re: Please stop using keypress event to handle non-printable keys

On Wed, Jan 17, 2018 at 6:34 PM, Masayuki Nakano wrote: > Hello, everyone. > > Please stop using keypress event for handling non-printable keys in new > code when you write new code and new automated tests. Firefox will stop > dispatching keypress events for non-printable

Intent to Unship: Application Cache over Insecure Contexts

AppCache is a powerful feature on the web that permits a web page to be viewed offline. This increases the risk that a user is unaware of the source of the web page content when browsing over HTTP. Besides fundamental issues with AppCache, which are summarized in this article