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

2016-07-29 Thread Boris Zbarsky
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

  document.body.classList.forEach(someFunc)

Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1290636

Standard: https://dom.spec.whatwg.org/#interface-nodelist and 
https://dom.spec.whatwg.org/#interface-domtokenlist


Platform coverage: all.

Estimated release: Firefox 50.

Devtools bug: none needed.

Other browsers: Chrome is shipping this in stable; no signals from 
Safari or Edge.


-Boris

___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Intent to implement: Dynamic blocklist to disallow plugins triggered from specified 3rd-party domains

2016-07-29 Thread Felipe G
Summary:

This intent covers adding a dynamic blocklist (to be stored/updated through
Shavar)
to disallow plugins running on specific domains when they are in a
3rd-party context
(e.g. a 3rd party iframe).

Motivation:

Flash and other plugins are still a primary target for malware authors and
distributors. In order to mitigate the risk of large-scale attacks, we're
going
to ask sites that are commonly loaded across the internet to disallow
any plugins running from their domain.

Bugs:
https://bugzilla.mozilla.org/show_bug.cgi?id=1277876

Link to standard: -

Platform coverage: all

Estimated or target release: Firefox 50

Preference behind which this will be implemented: no pref.
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


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

2016-07-29 Thread Ting-Yu Chou
Never mind, I just found the command on MDN. However I can't reproduce,
will update to bug 1290186 if I find anything.

Ting

On Fri, Jul 29, 2016 at 3:17 PM, Ting-Yu Chou  wrote:

> It seems that they're crashed with the test case
> firefox-ui/tests/puppeteer/test_windows.py:test_open_close, how can I run
> it locally?
>
> Ting
>
> On Fri, Jul 29, 2016 at 1:50 PM, Henrik Skupin  wrote:
>
>> Hi,
>>
>> Over the last couple of days I noticed a spike of crashes specifically
>> for our firefox-ui-tests as run on Taskcluster (Linux64, Ubuntu 12.04
>> docker image). The crashes are completely related to our e10s jobs.
>> There are a lot of different crash signatures, but mostly these are:
>>
>> [@ libpthread-2.15.so + 0xbd84]
>> [@ libc-2.15.so + 0xe7993]
>>
>>
>> https://treeherder.mozilla.org/#/jobs?repo=autoland&filter-searchStr=firefox%20ui%20e10s
>>
>> Does anyone know if there were related changes for e10s which might have
>> caused those crashes to appear? I'm afraid that we might have some
>> unknown top crashers which would go to aurora by the merge early next
>> week.
>>
>> Thanks
>>
>> --
>> Henrik
>> ___
>> dev-platform mailing list
>> dev-platform@lists.mozilla.org
>> https://lists.mozilla.org/listinfo/dev-platform
>>
>
>
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


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

2016-07-29 Thread Ting-Yu Chou
It seems that they're crashed with the test case
firefox-ui/tests/puppeteer/test_windows.py:test_open_close, how can I run
it locally?

Ting

On Fri, Jul 29, 2016 at 1:50 PM, Henrik Skupin  wrote:

> Hi,
>
> Over the last couple of days I noticed a spike of crashes specifically
> for our firefox-ui-tests as run on Taskcluster (Linux64, Ubuntu 12.04
> docker image). The crashes are completely related to our e10s jobs.
> There are a lot of different crash signatures, but mostly these are:
>
> [@ libpthread-2.15.so + 0xbd84]
> [@ libc-2.15.so + 0xe7993]
>
>
> https://treeherder.mozilla.org/#/jobs?repo=autoland&filter-searchStr=firefox%20ui%20e10s
>
> Does anyone know if there were related changes for e10s which might have
> caused those crashes to appear? I'm afraid that we might have some
> unknown top crashers which would go to aurora by the merge early next week.
>
> Thanks
>
> --
> Henrik
> ___
> dev-platform mailing list
> dev-platform@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-platform
>
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform