Intent to remove pcast and feed protocols

2017-12-12 Thread Jonathan Kingston
We have a two feed handling protocols that were never standardised and aren't implemented in other browsers. These protocols have been subject to various security bugs and also contribute to some technical debt. The protocols are used to route URLs in Firefox to the feed reader. The feed reader

Re: Intent to Ship: Set document.URL (location) to url of active document when navigation started for javascript:-generated documents

2017-12-12 Thread James Graham
On 12/12/17 14:49, Samael Wang wrote: The current behavior that Firefox would set document.URL to the javascript: URL on navigating to the javascript:-generated document doesn't fit HTML5 standard: https://html.spec.whatwg.org/#javascript-protocol We're going to fix that in bug 836567, and

Intent to Ship: Set document.URL (location) to url of active document when navigation started for javascript:-generated documents

2017-12-12 Thread Samael Wang
The current behavior that Firefox would set document.URL to the javascript: URL on navigating to the javascript:-generated document doesn't fit HTML5 standard: https://html.spec.whatwg.org/#javascript-protocol We're going to fix that in bug 836567, and ship it to 59. That would also indicate

Re: ARM performance testing on GNU/Linux instead of Android?

2017-12-12 Thread Makoto Kato
It is too hard to check performance issue on Android/arm now since autophone doesn't run default try server parameters. I sometimes fix cross compiling issue for Linux/arm and aarch64 since it is tier-3 platform. So if it runs this on arm cloud, Linux/arm has to raise to tier-1 or 2. -- Makoto