Re: PSA: Cancel your old Try pushes

On 17/04/2016 22:54, Mike Conley wrote: Generally speaking, Firefox's stability has not been good for me for 2-3 months. I'd like to file a bug, > but I've already used up my quota of unactionable bugs, and if I dug into all of my idiosyncratic issues I'd never get any work done. I seem to do t

Re: Does SSE2 usage still need to be conditional?

On Mon, Feb 1, 2016 at 10:04 PM, Benjamin Smedberg wrote: > It might be worth reconsidering now: I'm not willing to throw away 0.5% of > our users without good cause, but perhaps there is a good cause to be made > here? What would the performance gain be for the remaining 99.5% of users, > realizi

Moving XP to ESR?

XP has now gone for two years without security patches from Microsoft. Additionally, as of its latest release, Chrome no longer supports XP. When 46 ships, it would be a great time to make AUS advertise 45 ESR builds to XP (even on non-ESR) channel. This would keep XP supported through the ESR cyc

Re: Moving XP to ESR?

12% of our users are on Windows XP. - Kyle On Mon, Apr 18, 2016 at 6:04 AM, Henri Sivonen wrote: > XP has now gone for two years without security patches from Microsoft. > Additionally, as of its latest release, Chrome no longer supports XP. > > When 46 ships, it would be a great time to make A

Re: Moving XP to ESR?

Am 18.04.2016 um 15:18 schrieb Kyle Huey: > 12% of our users are on Windows XP. And XP still runs on ~10% of all desktops. That's an opportunity to convert some of the users to Firefox. Best regards Thomas > > - Kyle > > On Mon, Apr 18, 2016 at 6:04 AM, Henri Sivonen wrote: > >> XP has now gone

Re: Moving XP to ESR?

On Mon, Apr 18, 2016 at 9:04 AM, Henri Sivonen wrote: > XP has now gone for two years without security patches from Microsoft. > Additionally, as of its latest release, Chrome no longer supports XP. > > When 46 ships, it would be a great time to make AUS advertise 45 ESR > builds to XP (even on n

Re: PSA: Cancel your old Try pushes

Default should probably be fail push rather than auto cancel.. But +1 to opting into parallel push explicitly. I've certainly used that on a few occasions. But the PSA here may be the most important part.. On Apr 15, 2016 3:37 PM, "Jonas Sicking" wrote: We could also make the default behavior be

Re: Why do we still need to include Qt widget in mozilla-central?

I think that in this context we are talking about mozilla/widget/qt/* components and yes we're using those in our Gecko build. We don't use QWidgets for Sailfish Browser. User interface of the Sailfish Browser is written with Qt QML. There is more info in the embedding wiki [1] and Dmitry's blog [

Re: Moving XP to ESR?

On Mon, Apr 18, 2016 at 4:18 PM, Kyle Huey wrote: > 12% of our users are on Windows XP. That's been getting lower all the time, right? With the current trajectory, what's the expected percentage at the time when the 45 ESR would go out of support (assuming normal ESR cycle length)? -- Henri Siv

Re: Intent to ship: Treat cookies set over non-secure HTTP as session cookies

On Fri, Apr 15, 2016 at 5:45 PM, Matthew N. wrote: > On 2016-04-15 7:47 AM, Tantek Çelik wrote: > >> What steps can we take in this direction WITHOUT breaking web compat? >> >> >> E.g. since one of the issues raised is that *every* time a user >> enters/submits a password over HTTP (not secure),

Re: Intent to Ship: HTML5 and tags

On 4/14/16 3:53 AM, Ting-Yu Lin wrote: One major concern in the "intent to implement" discussion is the ability to style the summary disclosure triangle. Currently summary has default style "display: list-item", so we can style the triangle via the pseudo element |summary::-moz-list-bullet| like

Re: Moving XP to ESR?

On 04/18/2016 07:20 AM, Lawrence Mandel wrote: On Mon, Apr 18, 2016 at 9:04 AM, Henri Sivonen wrote: XP has now gone for two years without security patches from Microsoft. Additionally, as of its latest release, Chrome no longer supports XP. When 46 ships, it would be a great time to make AUS

Re: Moving XP to ESR?

What’s the “XP tax”? Graphics usually tries to simplify the playing field as much as possible, but I can’t say that XP has been causing any trouble, or that we have been getting too many XP specific problems (certainly fewer than Windows 10 :) I don’t see XP going away soon, and as mentioned

Intent to ship: ParentNode.prepend(), ParentNode.append(), ChildNode.before(), ChildNode.after(), ChildNode.replaceWith()

As of Firefox 48 I intend to ship ParentNode.prepend(), ParentNode.append(), ChildNode.before(), ChildNode.after(), and ChildNode.replaceWith() on all platforms. These methods would enable web developers to insert a set of nodes or strings into a parent node's children list or before/after a child

Re: Intent to ship: Element.animate

On 04/18/2016 05:12 AM, Brian Birtles wrote: In Firefox 48 I intend to turn Element.animate on by default. We have been developing the Web Animations API behind the dom.animations-api.core.enabled preference and have introduced the dom.animations-api.element-api.enabled preference for the subse

Re: Intent to ship: ParentNode.prepend(), ParentNode.append(), ChildNode.before(), ChildNode.after(), ChildNode.replaceWith()

OK from me. Need to still carefully look for any possible regressions. -Olli On 04/18/2016 08:11 PM, Jocelyn Liu wrote: As of Firefox 48 I intend to ship ParentNode.prepend(), ParentNode.append(), ChildNode.before(), ChildNode.after(), and ChildNode.replaceWith() on all platforms. These met

Re: Moving XP to ESR?

On 4/18/16 6:46 AM, Thomas Zimmermann wrote: Am 18.04.2016 um 15:18 schrieb Kyle Huey: > 12% of our users are on Windows XP. And XP still runs on ~10% of all desktops. That's an opportunity to convert some of the users to Firefox. If we want to convert some Chrome XP users, we could run a sma

Re: Dump frame tree in real time

Hi Botond thanks for replying, I just checked and calling drawWindow() doesn't output the entire page in the display-list dumps. It's as if this operation doesn't trigger the same things a regular render operation does. But your reply got me thinking. If I can force Firefox to always render the

Re: Why do we still need to include Qt widget in mozilla-central?

Where is this work taking place? Would it be possible for you to work directly in mozilla-central? Looking at the hg history of the the widget/qt subdirectory, all the changes I see there are Masayuki updating it for changes elsewhere, and people making tree-wide changes that have nothing to do wi

Re: Moving XP to ESR?

On Mon, Apr 18, 2016 at 2:02 PM, Chris Peterson wrote: > > OTOH, if an XP users doesn't mind running an unpatched OS, then they > probably won't care/know about running an unpatched Chrome browser. > >From data that Chris H-C posted in some previous thread, we know that Firefox users on XP are us

Re: PSA: Cancel your old Try pushes

On 2016-04-16 5:50 AM, Gijs Kruitbosch wrote: On 16/04/2016 01:24, Steve Fink wrote: Doesn't everyone keep a tab open to their try page? eg I have https://treeherder.mozilla.org/#/jobs?repo=try&author=sf...@mozilla.com open all the time. No. Treeherder is too resource-intensive to keep open fo

Re: PSA: Cancel your old Try pushes

On 2016-04-18 2:46 PM, William Lachance wrote: Treeherder did trigger a rather large memory leak which got fixed in the browser a while back (Dec 2015), so please consider revisiting it if you gave up around then: ... If anyone feels like profiling and submitting patches, we'd welcome the help.

Re: One Firefox repository to rule them all

+1. Figuring out why a line of code was added years ago and what bug caused the change takes way too long. On 4/16/16 2:05 AM, Henri Sivonen wrote: On Sat, Apr 16, 2016 at 8:02 AM, Nicholas Nethercote wrote: For me, having the CVS history in the mozilla-central repo would be much more helpfu

Re: Intent to ship: Treat cookies set over non-secure HTTP as session cookies

On 2016-04-18 7:59 AM, Richard Barnes wrote: Could we just disable HTTP auth for connections not protected with TLS? At least Basic auth is manifestly insecure over an insecure transport. I don't have any usage statistics, but I suspect it's pretty low compared to form-based auth. I also don'

Re: Why do we still need to include Qt widget in mozilla-central?

I don't know if Oleg (Romaxa) is still interested in this work. He was doing work for Nokia's MeGo platform when the code was added. MeGo was shut down by Nokia. Sailfish OS is the continuation but I don't know of any attempt to get Firefox running on Sailfish. Wolfgang is a long time Mozilla/SUSE

Re: Dump frame tree in real time

On Mon, Apr 18, 2016 at 2:06 PM, Jip de Beer wrote: > I just checked and calling drawWindow() doesn't output the entire page in the > display-list dumps. It's as if this operation doesn't trigger the same things > a regular render operation does. It worked for me. Here's what I did specifically

Re: Intent to ship: Element.animate

On Tuesday, 19 April 2016 02:23:54 UTC+9, smaug wrote: > On 04/18/2016 05:12 AM, Brian Birtles wrote: > > In Firefox 48 I intend to turn Element.animate on by default. > > > > We have been developing the Web Animations API behind the > > dom.animations-api.core.enabled preference and have introdu

Re: Intent to ship: Element.animate

On Tuesday, 19 April 2016 09:29:02 UTC+9, bbir...@mozilla.com wrote: > Full details are in bug 1245000 from comment 9 onwards > (https://bugzilla.mozilla.org/show_bug.cgi?id=). Err, https://bugzilla.mozilla.org/show_bug.cgi?id=1245000#c9. ___ dev-platf

Re: Intent to Ship: HTML5 and tags

Le 14 avr. 2016 à 18:24, Ting-Yu Lin a écrit : > On Thu, Apr 14, 2016 at 5:03 PM, Xidorn Quan wrote: >> Shouldn't "summary { list-style-type: none; }" be enough? > Yes. With Bug 1258657 > landed, it's enough to hide the triangle by summary {

Re: Intent to Ship: HTML5 and tags

On Tue, Apr 19, 2016 at 12:03 AM, Boris Zbarsky wrote: > On 4/14/16 3:53 AM, Ting-Yu Lin wrote: > >> One major concern in the "intent to implement" discussion is the ability >> to >> style the summary disclosure triangle. Currently summary has default >> style >> "display: list-item", so we can

Re: Dump frame tree in real time

Great to hear you got this working! I'll carefully follow your steps and see if I can get it to work too. The downside of this approach seems that I can't easily filter out the dumps of the entire page. I'm only interested in the dumps from the whole page, not the ones from the viewport. But th