On 10/2/18 1:38 PM, James Graham wrote:
Experimental (i.e. nightly/dev) builds of Firefox and Chrome are run on
Linux using Taskcluster after each commit to web-platform-tests.
Would a commit to Firefox that fixes some tests and just touches wpt
.ini files to mark those tests as passing
Summary:
`max-content` and `min-content` are sizing values for width, min-width,
max-width, height, min-height, max-height, inline-size, min-inline-size,
max-inline-size, and flex-basis. We support these two keywords with -moz-
prefix for many years, and Google Chrome has shipped them for 3 years.
https://wpt.fyi is a dashboard containing the results of the full
web-platform-tests suite in multiple versions of current browsers.
The default view shows test results in the latest stable releases of
desktop Firefox/Chrome/Edge/Safari. There are several alternative views
that are likely to
On Tue, Oct 02, 2018 at 09:29:51AM -0700, Andrew McCreight wrote:
This is a step towards bug 1493226, which is going to statically ban
trivial do_QueryInterface calls like this:
\o/
___
dev-platform mailing list
dev-platform@lists.mozilla.org
On Tue, Oct 2, 2018 at 9:33 AM Bobby Holley wrote:
> This is awesome - great papercut fix. Thanks Andrew!
>
> Any chance of fixing it for RefPtr too?
>
That should already work:
https://searchfox.org/mozilla-central/rev/6ddb5fb144993fb5de044e2e8d900d7643b98a4d/mfbt/RefPtr.h#142
> On Tue, Oct
This is awesome - great papercut fix. Thanks Andrew!
Any chance of fixing it for RefPtr too?
On Tue, Oct 2, 2018 at 9:30 AM Andrew McCreight
wrote:
> I've landed bug 1494765, which allows you to do assignments between
> nsCOMPtrs for classes that are related by subtyping.
>
> For instance:
>
>
I've landed bug 1494765, which allows you to do assignments between
nsCOMPtrs for classes that are related by subtyping.
For instance:
class A { ... ];
class B : public A { ... };
nsCOMPtr b = ...;
nsCOMPtr a = b; // this works now
This is a step towards bug 1493226, which is going to
(Sorry, I polled #jsapi about this issue back when you first posted and
then forgot to reply with the response.)
It doesn't seem like any SM devs use --enable-shared-js for their own
development but we do know that various embedders (e.g. GNOME) use the JS
shared library and so we'd like to keep
Neat! I took a quick peek at your addon source and the stuff it's
relying on seems ok for now. At least, it's not anything we plan to
change anytime soon. If there are changes to searchfox that would make
your life easier in terms of expanding your addon, let me know and we
can discuss
I've built an (experimental) WebExtension to integrate some of the
Searchfox features into Phabricator.
I find it very useful to be able to search code while reviewing, but I
have to resort to opening a new
Searchfox tab and looking for the code that is being modified. This
extension makes my
On Mon, Sep 24, 2018 at 3:24 PM, Boris Zbarsky wrote:
> On 9/24/18 4:04 AM, Henri Sivonen wrote:
>>
>> How important is --enable-shared-js? I gather its use case is making
>> builds faster for SpiderMonkey developers.
>
>
> My use case for it is to be able to use the "exclude samples from library
Hi
On 2/10/2018 5:05 AM, Aaron Klotz wrote:
For various reasons we don't want to put escape hatches into any
builds that we ship.
For local builds, if it would ease developer concerns over this
feature, we can look into it. I have filed bug 1495628 for that purpose.
Seems that we can
12 matches
Mail list logo