I filed
https://github.com/httpwg/http-extensions/issues/155
https://github.com/httpwg/http-extensions/issues/156
/ Jonas
On Thu, Mar 10, 2016 at 3:07 PM, wrote:
> Hey Jonas,
>
> Please feel free to raise issues:
> https://github.com/httpwg/http-extensions/labels/client-hints
>
> Cheers,
> _
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 rely
on sites doing that with CredentialContainer.store()? That doesn't
so
On 10/03/16 06:17 PM, Trevor Saunders wrote:
> given they haven't upgraded from 10.6 - 10.8 why do you believe they are
> likely to in the future?
1. their machine can die and they'll replace it with a new one that will
come with the latest MacOS, and restore their data from a Time Machine
backup.
I'm not making any claims other than pointing out that the upgrade is
possible for some users, and its a workaround we can give in SUMO. I
have no other irons in this fire, just making sure we know the
workarounds (and how accessible they are) is an important piece of
this decision.
As has been s
On Fri, Mar 11, 2016 at 07:49:26AM +0800, Kyle Huey wrote:
> On Fri, Mar 11, 2016 at 2:03 AM, Benjamin Smedberg
> wrote:
>
> > This is notice of an intent to deprecate support within Firefox for the
> > following old versions of MacOS: 10.6, 10.7, and 10.8
> >
> > The motivation for this change i
On Fri, Mar 11, 2016 at 2:03 AM, Benjamin Smedberg
wrote:
> This is notice of an intent to deprecate support within Firefox for the
> following old versions of MacOS: 10.6, 10.7, and 10.8
>
> The motivation for this change is that we have continued failures that are
> specific to these old operat
That brings up a point, if a user is on 10.8, gets moved to ESR 45, and
later moves to 10.11, will they be stuck on ESR still?
On Thu, Mar 10, 2016 at 4:01 PM, Tyler Downer wrote:
> The other thing to note is many of those users can still update to 10.11,
> and I imagine that over the next year
The linked document seems only concerned with one usecase of the
clipboard, that of adding a 'copy to clipboard' type button to a page,
but doesn't address any other cases, namely the more common case of
copy/paste using the browser UI (edit menu, keyboard shortcuts), for
which the existing eve
On 3/10/2016 6:38 PM, Nils Ohlmeier wrote:
Excuse my ignorance, but what means “deprecate support” exactly?
I’m only asking because of the opposing reply’s so far. I’m assuming it means
we stop testing and building/releasing for these. Would it be a possible
alternative to turn of the tests, b
> On Mar 10, 2016, at 10:03, Benjamin Smedberg wrote:
>
> This is notice of an intent to deprecate support within Firefox for the
> following old versions of MacOS: 10.6, 10.7, and 10.8
Excuse my ignorance, but what means “deprecate support” exactly?
I’m only asking because of the opposing re
On Thu, Mar 10, 2016 at 05:20:41PM -0600, Syd Polk wrote:
> I do, however, think that supporting 10.6 is a heavy, heavy burden, as its
> C++ compiler is truly ancient.
We build Firefox targetting 10.6 with a development version of clang 3.8
(that is, a clang build from a svn revision during the 3
10.6 is the last version with Rosetta. Given how old the machines are that can
run 10.6, and given how old 10.6 itself is, it is highly likely that 10.6
customers still have PowerPC apps that they run and they cannot/will not
upgrade.
Also, the perception of the Mac community in general is that
On 3/10/16 5:17 PM, Trevor Saunders wrote:
On Thu, Mar 10, 2016 at 04:01:15PM -0700, Tyler Downer wrote:
The other thing to note is many of those users can still update to 10.11,
and I imagine that over the next year that number will continue to go down.
given they haven't upgraded from 10.6 -
On Thu, Mar 10, 2016 at 04:01:15PM -0700, Tyler Downer wrote:
> The other thing to note is many of those users can still update to 10.11,
> and I imagine that over the next year that number will continue to go down.
given they haven't upgraded from 10.6 - 10.8 why do you believe they are
likely to
On 3/10/16 4:50 PM, Ryan VanderMeulen wrote:
25% is pretty close for 10.6-10.8 combined. However, the current
proposal includes security patches for nearly a year still (putting
them on the ESR45 train), so construing this as abandoning those users
seems like it's going a bit far.
I'm not sur
Hey Jonas,
Please feel free to raise issues:
https://github.com/httpwg/http-extensions/labels/client-hints
Cheers,
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
On 3/10/2016 5:47 PM, Masatoshi Kimura wrote:
Some fullscreen tests are enabled only on 10.6:
https://dxr.mozilla.org/mozilla-central/source/dom/tests/mochitest/chrome/chrome.ini#40
This proposal will virtually disable the fullscreen tests on OS X.
|skip-if = os != 'mac' || os_version == '1
The other thing to note is many of those users can still update to 10.11,
and I imagine that over the next year that number will continue to go down.
This also provides a decent workaround that our support community can
recommend in documentation and the forums.
On Thu, Mar 10, 2016 at 3:50 PM, Ry
Hi Gabor! Thanks for starting this thread.
On 2016-03-10 5:07 AM, Gabor Krizsanits wrote:
While the other thread about fuzzing friendly Gecko is an interesting
option I would like to go back to the original topic, and start another
thread to collect other ideas too, that might help getting bette
25% is pretty close for 10.6-10.8 combined. However, the current proposal
includes security patches for nearly a year still (putting them on the
ESR45 train), so construing this as abandoning those users seems like it's
going a bit far.
On Thu, Mar 10, 2016 at 5:25 PM, Mike Hommey wrote:
> On Th
On 2016/03/11 3:03, Benjamin Smedberg wrote:
> The motivation for this change is that we have continued failures that
> are specific to these old operating systems and don't have the resources
> on engineering teams to prioritize these bugs. Especially with the
> deployment of e10s we're seeing int
On Thu, Mar 10, 2016 at 5:25 PM, Mike Hommey wrote:
> On Thu, Mar 10, 2016 at 01:03:43PM -0500, Benjamin Smedberg wrote:
> > This will affect approximately 1.2% of our current release population.
> Here
> > are the specific breakdowns by OS version:
> >
> > 10.6
> > 0.66%
> > 10.7
> >
On Thu, Mar 10, 2016 at 01:03:43PM -0500, Benjamin Smedberg wrote:
> This is notice of an intent to deprecate support within Firefox for the
> following old versions of MacOS: 10.6, 10.7, and 10.8
>
> The motivation for this change is that we have continued failures that are
> specific to these ol
On Thu, Mar 10, 2016 at 10:29 AM, Aaron Klotz wrote:
> I'm looking forward to this!
>
> On 3/10/2016 9:14 AM, Gregory Szorc wrote:
>
>>
>> A host of new C++ features should be available after the switch. Although,
>> we may have to drop support for VS2013 before those can be fully realized.
>> I
Thanks for taking this on Alex!
I had some initial concerns with the API from a fetch/SW perspective, but
Mike seems open to addressing them:
https://github.com/w3c/webappsec-credential-management/issues/11
I believe Matthew Noorenberghe had some concerns about the necessity of the
API given r
People kindly pointed out to me that the plain-text forwarded message
had lost the link to Lucas's draft. Here it is:
https://docs.google.com/document/d/1QI5rKJSiYeD9ekP2NyCYJuOnivduC9-tqEOn-GsCGS4/edit#
On Thu, Mar 10, 2016 at 3:57 PM, Hallvord Reiar Michaelsen Steen
wrote:
> Hi dev-platform-peo
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 extension env on web?
If your problem is happening in an extension, then filing
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 is passed to a function, now in that function I am no longer to
> access this proper
Summary: This API is enabling a website to request a user's credentials from a
user agent, and helps the user agent to correctly store user credentials for
future use. It helps the LoginManager to get rid of most of the heuristics.
Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1156047
Link to
On 2016-03-10 1:44 PM, 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 extension env on web?
Thanks
I do not believe so.
___
Devan,
I did a quick search and it looks like you'd be a new bugzilla contributor,
so thank you!
These have not been edited in a while, but if you're looking for guidance
on writing a bug
https://developer.mozilla.org/en-US/docs/Mozilla/QA/Bug_writing_guidelines
(nudge to the community, have a l
On Thursday, March 10, 2016 at 1:32:41 PM UTC-5, Josh Matthews wrote:
> Hi Devan! This is an interesting bug report, but it's lacking some
> useful information to help triage it. Does this problem occur in a web
> page, or extension, or some other environment? Can you create a minimal
> example
Hi Devan! This is an interesting bug report, but it's lacking some
useful information to help triage it. Does this problem occur in a web
page, or extension, or some other environment? Can you create a minimal
example of the issue that anyone else could use to reproduce the problem
you're obser
I'm looking forward to this!
On 3/10/2016 9:14 AM, Gregory Szorc wrote:
A host of new C++ features should be available after the switch. Although,
we may have to drop support for VS2013 before those can be fully realized.
I defer to others to determine when VS2013 will be dropped.
There's e
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 is passed
to a function, now in that function I am no longer to access this property that
I added to the function.
Was there any sort of chang
This is notice of an intent to deprecate support within Firefox for the
following old versions of MacOS: 10.6, 10.7, and 10.8
The motivation for this change is that we have continued failures that
are specific to these old operating systems and don't have the resources
on engineering teams to
Visual Studio 2015 has been out for a while. Many people have put in work
to make Firefox build on it. The time has come to officially transition
release builds from Visual Studio 2013 to Visual Studio 2015.
This email serves as an intent to switch automation to Visual Studio 2015
Update 1 (latest
Hi dev-platform-people,
while editing the clipboard API spec [1] it's sometimes been suggested
to forget about the old slightly cranky API and start fresh. I haven't
had much response from implementors when such ideas came up on
public-webapps, but here's an interesting E-mail from Lucas Garron at
On 2016-03-09 22:17, Boris Zbarsky wrote:
On 3/9/16 3:47 PM, decoder...@googlemail.com wrote:
Actually no. I adapted our gtests in less than an hour.
Does this have to do with the set of things they're testing, or the
style the tests are written in?
I think the point is that some tests make
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 concerned about the general applicability of this work
> to the Web. Our
While the other thread about fuzzing friendly Gecko is an interesting
option I would like to go back to the original topic, and start another
thread to collect other ideas too, that might help getting better on the
performance front. Here are some of my thoughts after spending some time
with the pr
On 10.03.2016 08:53, L. David Baron wrote:
> On Tuesday 2016-03-01 09:32 +0800, L. David Baron wrote:
>> The W3C is proposing a charter for:
>>
>> TV Control Working Group
>> https://www.w3.org/2016/02/tvcontrol.html
>> https://lists.w3.org/Archives/Public/public-new-work/2016Feb/0005.html
>>
42 matches
Mail list logo
