Intent to implement: accept arbitrary webkit-prefixed pseudo-element in selectors

Summary: Treat "::-webkit-whatever-stuff" as valid CSS selectors. Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1424106 Link to standard: * https://github.com/whatwg/compat/issues/103 * https://github.com/w3c/csswg-drafts/issues/2156 (previous discussion of this topic) Platform coverage:

Re: PSA: nsISimpleEnumerator now works as a JS iterator

Wow, this is a great improvement! Thank you! On Thu, Aug 23, 2018, 6:26 PM Kris Maglione wrote: > Oh, and from C++, there's also now a range iterator wrapper with > similar semantics: > > for (auto& docShell : SimpleEnumerator(docShellEnum)) { > ... > } > > On Thu, Aug 23, 2018 at

Re: PSA: nsISimpleEnumerator now works as a JS iterator

Oh, and from C++, there's also now a range iterator wrapper with similar semantics: for (auto& docShell : SimpleEnumerator(docShellEnum)) { ... } On Thu, Aug 23, 2018 at 03:19:55PM -0700, Kris Maglione wrote: As of bug 1484496, any C++-implemented nsISimpleEnumertor instance can be used

Re: mozilla-inbound backout policy subject to change (become similar to autoland)

The job visibility policy [1] says that tier 2 is observed but unmanaged while the documentation on tier 2 platforms [2] explains that changes causing issue for tier 2 are not immediately backed out but get reverted if no fix is found. The job visibility policy and the classification of jobs

Phlay (Git/Phabricator Commit Series tool) - Now without a PHP/Arcanist Dependency~

Previously I sent an email to this list ( https://groups.google.com/forum/#!topic/mozilla.dev.platform/o9f2S0vO47k) about my |phlay| tool for pushing commit series to phabricator without touching the working directory. (https://github.com/mystor/phlay) I've since rewritten it to avoid the PHP and

Intent to implement: Suppress exception/error reporting when loading an unknown external protocol

Summary: Gecko will report an error when loading an unknown external protocol (by firing an NS_ERROR_UNKNOWN_PROTOCOL event). This could be a privacy threat because the behavior allows websites to enumerate external protocols of users’ platforms, which is a fingerprinting issue. To address this

Re: Soft code freeze for Firefox 63 starts August 23

Hello everyone, August 23rd is now upon us and the soft freeze has begun. It will end on September 4 once the Gecko version number is bumped to 64 on mozilla-central. Thanks, Ryan On Thu, Aug 16, 2018 at 11:14 AM Pascal Chevrel wrote: > Hello, > > This is a reminder that the Nightly Soft