Re: Better download security through browsers

On 27.03.2017 16:21, Daniel Veditz wrote: > On Mon, Mar 27, 2017 at 1:22 AM, Frederik Braun > wrote: > > UI hooks, for the SafeBrowsing > ​ ​ > malicious file checks, where we really, > ​ ​ > really discourage you from using > ​ ​ > the down

firefox-dev posting [was Re: unowned module: Firefox::New Tab Page, help me find an owner]

Justin and I did some investigation and weren't able to reproduce the problems people were encountering last year. We confirmed that it is not necessary to subscribe before posting. If the sender is not whitelisted, then messages receive an immediate reply with the subject "Your message to firefo

Re: Proper way to return nsresult from Rust before Stylo is mandatory?

On 2017-03-27 5:10 PM, Michael Layzell wrote: > I don't think it would be too hard. At one point I had a WIP patch which > implemented it, but I would have to dig it up again. > > I'll see if I can get a patch up for the crate in my spare time. Thank you! > On Sun, Mar 26, 2017 at 11:26 PM, Ehsa

Re: Proper way to return nsresult from Rust before Stylo is mandatory?

I don't think it would be too hard. At one point I had a WIP patch which implemented it, but I would have to dig it up again. I'll see if I can get a patch up for the crate in my spare time. On Sun, Mar 26, 2017 at 11:26 PM, Ehsan Akhgari wrote: > On 2017-03-17 10:08 AM, Michael Layzell wrote:

Re: Switching to async/await from Task.jsm/yield

On Mon, Mar 27, 2017 at 12:42:46PM -0700, Dave Townsend wrote: It looks like the main concern raised about switching over to async/await where possible is bug 1242505. I personally wouldn't consider this a blocker. I'm all for it being fixed, but the benefit of not having Promise.jsm noise in

Re: Switching to async/await from Task.jsm/yield

It looks like the main concern raised about switching over to async/await where possible is bug 1242505. We're going to try to get some resources for fixing that bug and it probably blocks doing a mass rewrite of existing code but I don't think it blocks people starting to use async/await right now

Re: Proper way to return nsresult from Rust before Stylo is mandatory?

On Fri, Mar 17, 2017 at 4:27 AM, Emilio Cobos Álvarez wrote: > Fedora didn't have libclang 3.9 packages IIRC, but that could've > changed. clang 3.9.1 in now in the fedora 25 updates repo. https://koji.fedoraproject.org/koji/packageinfo?packageID=21848 -r __

Re: Async Iteration is available on non-release-only, for testing purpose

Let's make sure to add a test that's expected to fail as well for this so we can verify that we don't accidentally ship this enabled in chrome. Not that we've had any recent instances of thinking we'd disabled a feature only for it to get unknowingly shipped :) -Ryan On 3/27/2017 12:31 PM, Sh

Re: Async Iteration is available on non-release-only, for testing purpose

I agree that disabling for chrome is the right thing here over prefs. I want Nightly and DevEdition to have stage 3+ TC39 proposals unflagged and ready to play with -- asking folks to turn on prefs to do that is not the way to go here from my perspective. Benjamin's concern is legit, though, so le

Re: Async Iteration is available on non-release-only, for testing purpose

Cross-posting to firefox-dev. TL;DR: arai has done truly excellent feature work implementing the ECMAScript Async Iteration proposal. It is gated to Nightly/DevEd only for content code. We will also be turning off the feature in chrome code to prevent accidental dependence. Both these restriction

Re: Async Iteration is available on non-release-only, for testing purpose

I think disabling in chrome code is a good idea. We have done these kinds of non-release-only features in the JS engine in the past, and it hasn't always gone well precisely for the reasons that have you concerned. OTOH, adding a pref is annoyingly complicated for JS engine features (we should prob

Re: Upcoming C++ standards meeting in Kona, Hawaii

If you're interested in what happened at this meeting, my blog post has details: https://botondballo.wordpress.com/2017/03/27/trip-report-c-standards-meeting-in-kona-february-2017/ Cheers, Botond On Fri, Feb 24, 2017 at 1:53 PM, Botond Ballo wrote: > Hi everyone! > > The next meeting of the C++

Re: Async Iteration is available on non-release-only, for testing purpose

That's super exciting! The new localization resources registry module is being written with async generators in mind. I have the patch ready in the bug, which can be flipped to go async with 8 lines of code. I know we're not planning to make it ride trains just yet, but if you need a real-worl

Re: Async Iteration is available on non-release-only, for testing purpose

I am concerned about the accidental consequences of turning this on for nightly/aurora. What if we start writing browser code that relies on these features which unexpectedly starts failing in beta? I presume the value of enabling this in nightly/aurora is that we can get web developers to experim

Async Iteration is available on non-release-only, for testing purpose

I just landed the initial implementation of Async Iteration proposal (async generator and for-await-of syntax), as non-release-only feature. https://bugzilla.mozilla.org/show_bug.cgi?id=1331092 The implementation is only for the testing purpose (for finding spec bug etc), and the semantic chang

Re: Better download security through browsers

On Mon, Mar 27, 2017 at 1:22 AM, Frederik Braun wrote: > UI hooks, for the SafeBrowsing > ​ ​ > malicious file checks, where we really, > ​ ​ > really discourage you from using > ​ ​ > the downloaded file but you can still click around that with lots of > ​ ​ > left-clicking. > ​"Not known to be

Re: Better download security through browsers

On 24.03.2017 18:24, Mike Hoye wrote: > My 2006 proposal didn't get any traction either. > > https://lists.w3.org/Archives/Public/public-whatwg-archive/2006Jan/0270.html > > > FWIW I still think it'd be a good idea with the right UI. I think we already have _related_ UI hooks, for the SafeBrows

Re: Future of out-of-tree spell checkers?

On Fri, Mar 24, 2017 at 3:20 PM, Ehsan Akhgari wrote: > On 2017-03-24 4:20 AM, Henri Sivonen wrote: >> On Fri, Mar 24, 2017 at 2:38 AM, Ehsan Akhgari >> wrote: >>> On Wed, Mar 22, 2017 at 11:50 AM, Jeff Muizelaar >>> wrote: On Wed, Mar 22, 2017 at 11:08 AM, Henri Sivonen wrote: