Re: navigator.clipboard

2016-03-11 Thread Jonas Sicking
Generally speaking, I find it really hard to reason about what we should do regarding clipboard events and drag'n'drop events without taking a larger look at the sad story that rich-text-editing on the web is today. It seemed like there was some really promising explorations happening for a while

Re: navigator.clipboard

2016-03-11 Thread Hallvord Reiar Michaelsen Steen
On Fri, Mar 11, 2016 at 8:57 AM, Jonas Sicking wrote: > It seemed like there was some really promising explorations happening > for a while regarding developing a better API than the current > contentEditable behavior. Did that go anywhere? http://w3c.github.io/editing/ ? It's still going strong

Re: Proposed W3C Charter: TV Control Working Group

2016-03-11 Thread L. David Baron
On Thursday 2016-03-10 02:17 -0800, Jonas Sicking wrote: > On Wed, Mar 9, 2016 at 11:53 PM, L. David Baron wrote: > > Although we've participated in the development of this work in the > > community group, this is an area that we're becoming less involved > > in. > > > > We're also concern

Re: Intent to implement: W3C WebAppSec credentialmanagement API

2016-03-11 Thread Axel Nennker
Am Freitag, 11. März 2016 05:27:34 UTC+1 schrieb Martin Thomson: > On Fri, Mar 11, 2016 at 5:56 AM, Axel Nennker wrote: > > no password generation help by the UA > > I agree with MattN here, not doing this eliminates much of the > advantage of having a password manager. Or do you have a plan to

Re: Setting property on the element is no longer working on Firefox 45

2016-03-11 Thread Devan Shah
On Thursday, March 10, 2016 at 2:50:10 PM UTC-5, Kris Maglione wrote: > On Thu, Mar 10, 2016 at 10:44:24AM -0800, Devan Shah wrote: > >This happens in side extension only (works fine on web standalone), i will > >try to extract a simple reproducible scenario. > > > >Is there any way to simulate a

Re: Setting property on the element is no longer working on Firefox 45

2016-03-11 Thread Devan Shah
On Thursday, March 10, 2016 at 2:42:14 PM UTC-5, Ted Mielczarek wrote: > On Thu, Mar 10, 2016, at 01:23 PM, Devan Shah wrote: > > hello > > > > When I set a custom property such as element.listofSomething = [] and > > then build the list and add it back to the same element. Then this > > element i

Re: Intent to implement: W3C WebAppSec credentialmanagement API

2016-03-11 Thread richard . barnes
On Thursday, March 10, 2016 at 11:27:34 PM UTC-5, Martin Thomson wrote: > On Fri, Mar 11, 2016 at 5:56 AM, Axel Nennker wrote: > > no password generation help by the UA > > I agree with MattN here, not doing this eliminates much of the > advantage of having a password manager. Or do you have a p

Re: Intent to deprecate: MacOS 10.6-10.8 support

2016-03-11 Thread Benjamin Smedberg
On 3/10/2016 5:25 PM, Mike Hommey wrote: It's unfair to mention those populations by percentage of the global Firefox population. Why do you think this is unfair? This is about making the best use of our limited engineering/testing/QA resources, and so what really matters is the total impa

Re: Intent to implement: W3C WebAppSec credentialmanagement API

2016-03-11 Thread Anne van Kesteren
On Fri, Mar 11, 2016 at 6:08 PM, wrote: > That does raise the question, however, of how such a credential differs from, > say: > > * A cookie > * A random nonce in localStorage/IDB > * A non-extractable WebCrypto key The idea is that these are all less persistent. When you clear storage/cookies

Re: Intent to deprecate: MacOS 10.6-10.8 support

2016-03-11 Thread Mike Hommey
On Fri, Mar 11, 2016 at 12:20:30PM -0500, Benjamin Smedberg wrote: > We intend to do the following things: > > * add version checking to the builds so that they refuse to run on these > versions of MacOS If we change the macos target version, that's not possible. The resulting binaries can't even

Re: Intent to deprecate: MacOS 10.6-10.8 support

2016-03-11 Thread Terrence Cole
We've had this conversation several times in the last few years and I think I've finally figured out why it has always felt subtly wrong. Our share of users on older platforms is disproportionally high compared to the market in general because of our decline in market share. People who don't want

Re: Intent to deprecate: MacOS 10.6-10.8 support

2016-03-11 Thread Jonas Sicking
On Fri, Mar 11, 2016 at 9:20 AM, Benjamin Smedberg wrote: > On 3/10/2016 5:25 PM, Mike Hommey wrote: >> It's unfair to mention those populations by percentage of the global >> Firefox population. > > Why do you think this is unfair? This is about making the best use of our > limited engineering/te

PSA: GCC 4.8 is now the minimum version required

2016-03-11 Thread Mike Hommey
Hi, Assuming it sticks, GCC 4.8 is now the minimum GCC version required to build Firefox/Gecko. Details in bug 1175546, most notably comment 2. Mike ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-plat

Re: Intent to deprecate: MacOS 10.6-10.8 support

2016-03-11 Thread Chris Hofmann
On Fri, Mar 11, 2016 at 9:20 AM, Benjamin Smedberg wrote: > > > On 3/10/2016 5:25 PM, Mike Hommey wrote: > >> >> It's unfair to mention those populations by percentage of the global >> Firefox population. >> > > Why do you think this is unfair? This is about making the best use of our > limited e