Intent to ship: XMLHttpRequest parsing errors will yield a null document for web content, not one with a root.

2016-08-02 Thread Thomas Wisniewski
Summary: XMLHttpRequests for web content (and WebExtensions) will now follow the spec and return a null response/responseXML in the event of a parsing error, rather than a document with a root. The web console will also log a more informative error. Non-WebExtension addons and other chrome code

Re: Intent to implement version 4 of the Safe Browsing protocol

2016-08-02 Thread Mike Hommey
On Tue, Aug 02, 2016 at 07:28:32AM -0700, Francois Marier wrote: > The Safe Browsing service we rely on for protection against malware and > deceptive sites is migrating to a new version of the Safe Browsing > protocol. Version 4 will enable Google to quickly send the most relevant > list entries

Usability improvements for Firefox automation initiative - Status update #2

2016-08-02 Thread Armen Zambrano G.
On this update, we will look at the progress made since our initial update. A reminder that this quarter’s main focus is on: * Debugging tests on interactive workers (only Linux on TaskCluster) * Improve end to end times on Try (Thunder Try project) For all bugs and priorities you can check out

Intent to ship: CSS4 :any-link pseudo-class

2016-08-02 Thread Thomas Wisniewski
As of Firefox 50, I intend to unprefix the CSS4 :any-link pseudo-class on all platforms. It has been supported in Firefox for a long time now as :-moz-any-link, and has been aligned with the spec for several years as well (see https://www.w3.org/Bugs/Public/show_bug.cgi?id=21070). Bug to turn on

How useful is the WinSock LSP field in crash reports?

2016-08-02 Thread Nicholas Nethercote
Hi, Crash reports have a field called "WinSock LSP". In a crash report on crash-stats.mozilla.org, this field is shown in both the "Details" tab (which is the most important tab) and the "Metadata" tab (where all raw crash report fields are always shown). I suspect it is rare for this field to

[Firefox Desktop] Issues found: July 18th to 22nd

2016-08-02 Thread Andrei Vaida
Hi everyone, Here's the list of new issues found and filed by the Desktop Release QA Team last week, *July 18 - July 2**2* (week 29). Additional details on the team's priorities last week, as well as the plans for the current week are available at:

Re: Intent to implement and ship: Iterable declarations on NodeList and DOMTokenList

2016-08-02 Thread Boris Zbarsky
On 8/2/16 8:32 AM, masataka.yak...@gmail.com wrote: It looks like WebKit landed support recently. https://trac.webkit.org/changeset/203222 https://trac.webkit.org/changeset/203728 Ah, thanks. I just checked a WebKit nightly, and yes, they support it in a way compatible with our

Re: Intent to implement and ship: Iterable declarations on NodeList and DOMTokenList

2016-08-02 Thread masataka . yakura
On Saturday, July 30, 2016 at 11:41:23 AM UTC+9, Boris Zbarsky wrote: > Summary: The idea is to have keys/entries/values/forEach methods on > these two interfaces, so you can do things like: > >document.querySelectorAll("whatever").forEach(someFunc) > > and > >

Intent to implement version 4 of the Safe Browsing protocol

2016-08-02 Thread Francois Marier
The Safe Browsing service we rely on for protection against malware and deceptive sites is migrating to a new version of the Safe Browsing protocol. Version 4 will enable Google to quickly send the most relevant list entries to clients (based on platform and locale for example) as well as deal

Re: Increased number of e10s related crashes for firefox-ui-tests on mozilla-central and integration branches

2016-08-02 Thread Mike Conley
Might be unexpected fallout from bug 1261842 which landed on central on Monday (July 25th). Does that correspond to your timeline of when this started showing up? I'm seeing this in the log for at least one of these: "JavaScript error: chrome://marionette/content/listener.js, line 1017: