On 7/1/15 2:49 AM, Anne van Kesteren wrote:
Platform. There was no strong opposition to the Intent to deprecate:
Insecure HTTP thread and in Whistler everyone attending the
deprecating non-secure HTTP session agreed. Do you think this needs to
be approached differently?
Yes. Because taken at
I'll leave some of your points/questions for Richard.
On Wed, Jul 1, 2015 at 10:30 AM, Boris Zbarsky bzbar...@mit.edu wrote:
We add lots of features without such Intent threads all the time. Just FYI.
I hope that we can get somewhat better on this. It is rather useful to
have a somewhat large
On 7/1/15 4:43 AM, Anne van Kesteren wrote:
I hope that we can get somewhat better on this. It is rather useful to
have a somewhat large set of people have insight as to what goes into
Platform.
Sure. I'm just saying that I suspect people underestimate the number of
features we add, the
On Tuesday 2015-06-30 17:00 -0400, Richard Barnes wrote:
Second, when we implement new web platform features, they will be enabled
only on secure contexts. Exceptions can be granted, but will need to be
justified as part of the Intent to Implement [3] and Intent to Ship process.
I think this
On Wed, Jul 1, 2015 at 11:35 AM, L. David Baron dba...@mozilla.com wrote:
On Tuesday 2015-06-30 17:00 -0400, Richard Barnes wrote:
Second, when we implement new web platform features, they will be enabled
only on secure contexts. Exceptions can be granted, but will need to be
justified as
On Wed, Jul 1, 2015 at 8:16 AM, Boris Zbarsky bzbar...@mit.edu wrote:
we'd need to decide what
https://w3c.github.io/webappsec/specs/powerfulfeatures/#is-origin-trustworthy
step 5 should mean in our particular case
Colloquially: would you show a lock?
Unfortunately, conveying the nuance
On Tue, Jun 30, 2015 at 11:18 PM, Boris Zbarsky bzbar...@mit.edu wrote:
On 6/30/15 5:00 PM, Richard Barnes wrote:
Second, when we implement new web platform features, they will be enabled
only on secure contexts.
Might I ask who this we is (I don't recall general DOM module owner buy-in
on
As a next step toward deprecating non-secure HTTP [1], we are making the
following two changes to how we develop new web platform features,
effective immediately:
First, when we work on developing specifications for new web platform
features, we will make sure that these specifications require
On 6/30/15 5:00 PM, Richard Barnes wrote:
Second, when we implement new web platform features, they will be enabled
only on secure contexts.
Might I ask who this we is (I don't recall general DOM module owner
buy-in on this, but maybe I missed it?) what the definition of new web
platform
9 matches
Mail list logo
