Re: Intent to ship: Canvas CSS/SVG filters
Awesome and congrats Tobias! -tantek On Thu, May 26, 2016 at 9:40 AM, Tobias Schneiderwrote: > I intend to turn Canvas CSS/SVG filters on by default on all platforms. It > has been developed behind the canvas.filters.enabled preference. Google's > Chrome is already shipping this in version 52. > > Related bugs: > > https://bugzilla.mozilla.org/show_bug.cgi?id=927892 > https://bugzilla.mozilla.org/show_bug.cgi?id=1173545 > > Specification: > > https://html.spec.whatwg.org/multipage/scripting.html#dom-context-2d-filter > ___ > 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: C++11 standard library support enabled on all Tier-1 platforms
On Fri, May 27, 2016 at 6:34 AM, Kurt Roeckxwrote: > On 2016-05-27 03:50, Nathan Froyd wrote: >> Given the standard library's pervasive use of exceptions, and our >> aversion to the same, if you are using a standard library header >> that's not listed here: > > Are there plans to start using C++ exception? The wiki seems to suggest > there are plans, but it was last modified in 2008. There was a discussion about this topic recently that I thought was on dev-platform, but some searching doesn't turn it up. The consensus I remember was that was it was semi-desirable, but auditing all of the existing code for exception safety was a long, tedious task. We'd have to see what the size and runtime penalties looked like as well. I don't think anybody's planning on tackling this anytime soon. -Nathan ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Intent to ship: Canvas CSS/SVG filters
I intend to turn Canvas CSS/SVG filters on by default on all platforms. It has been developed behind the canvas.filters.enabled preference. Google's Chrome is already shipping this in version 52. Related bugs: https://bugzilla.mozilla.org/show_bug.cgi?id=927892 https://bugzilla.mozilla.org/show_bug.cgi?id=1173545 Specification: https://html.spec.whatwg.org/multipage/scripting.html#dom-context-2d-filter ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: C++11 standard library support enabled on all Tier-1 platforms
It used to be that using STL headers not in the approved list would fail to compile. I don't know whether that mechanism is still turned on or works correctly. --BDS On Fri, May 27, 2016 at 8:24 AM, Josh Matthewswrote: > On 2016-05-26 9:50 PM, Nathan Froyd wrote: > >> [CC mobile-firefox-dev and dev-fxos for notes below.] >> >> Bug 1246743 (Mac libc++ support) and bug 1273934 (Android libc++ >> support for local development builds) have landed on mozilla-central. >> This change means that all of our Tier-1 platforms now have a >> more-or-less conformant C++11 standard library. We can therefore >> begin removing a decent amount of code that we required to support >> pre-C++11 standard libraries and use standard facilities instead. You >> are still strongly encouraged to use Gecko-specific data structures >> (nsTArray ns{C,}String, etc.) in preference to the standard library >> ones, unless you need to interface with a third-party library. >> >> Given the standard library's pervasive use of exceptions, and our >> aversion to the same, if you are using a standard library header >> that's not listed here: >> >> http://dxr.mozilla.org/mozilla-central/source/config/stl-headers >> >> you need to ask for review to get that header added to the list, per >> policy in that file. >> >> This change also means that any non-Tier-1 platforms (FxOS, for >> instance) that don't provide a C++11 standard library will probably >> break in very short order as various code is removed from the tree. >> >> Developers who work on the C++ side of Firefox for Android are >> strongly encouraged to upgrade to an r11 NDK; the r10 NDK should work, >> but test results in the presence of crashes might be slightly wonky. >> >> Enjoy! >> -Nathan >> >> > Do we have any automation that prevents using headers that aren't in the > list? > > Cheers, > Josh > > ___ > 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: C++11 standard library support enabled on all Tier-1 platforms
On Thu, May 26, 2016 at 10:08 PM, Mike Hommeywrote: > On Thu, May 26, 2016 at 09:50:56PM -0400, Nathan Froyd wrote: >> This change also means that any non-Tier-1 platforms (FxOS, for >> instance) that don't provide a C++11 standard library will probably >> break in very short order as various code is removed from the tree. > > When do we actively remove support for stlport (which b2g still uses, > and which is still an option of --with-android-cxx-stl)? "Soon"? I'll probably do this next week. -Nathan ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: C++11 standard library support enabled on all Tier-1 platforms
On 2016-05-26 9:50 PM, Nathan Froyd wrote: [CC mobile-firefox-dev and dev-fxos for notes below.] Bug 1246743 (Mac libc++ support) and bug 1273934 (Android libc++ support for local development builds) have landed on mozilla-central. This change means that all of our Tier-1 platforms now have a more-or-less conformant C++11 standard library. We can therefore begin removing a decent amount of code that we required to support pre-C++11 standard libraries and use standard facilities instead. You are still strongly encouraged to use Gecko-specific data structures (nsTArray ns{C,}String, etc.) in preference to the standard library ones, unless you need to interface with a third-party library. Given the standard library's pervasive use of exceptions, and our aversion to the same, if you are using a standard library header that's not listed here: http://dxr.mozilla.org/mozilla-central/source/config/stl-headers you need to ask for review to get that header added to the list, per policy in that file. This change also means that any non-Tier-1 platforms (FxOS, for instance) that don't provide a C++11 standard library will probably break in very short order as various code is removed from the tree. Developers who work on the C++ side of Firefox for Android are strongly encouraged to upgrade to an r11 NDK; the r10 NDK should work, but test results in the presence of crashes might be slightly wonky. Enjoy! -Nathan Do we have any automation that prevents using headers that aren't in the list? Cheers, Josh ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: C++11 standard library support enabled on all Tier-1 platforms
On 2016-05-27 03:50, Nathan Froyd wrote: Given the standard library's pervasive use of exceptions, and our aversion to the same, if you are using a standard library header that's not listed here: Are there plans to start using C++ exception? The wiki seems to suggest there are plans, but it was last modified in 2008. Kurt ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Intent to ship: Unprefixed text-align-last
In Firefox 49 I intent to ship unprefixed text-align-last. It has been shipped prefixed for quite a while, and Chrome has shipped this property unprefixed since about a year ago [1]. Although CSS Text 3 hasn't entered CR stage, this property is considered stable. Also it has been widely-used according usage count from Chrome [2], so breaking change to this property could be risky. Bug to unprefix: https://bugzilla.mozilla.org/show_bug.cgi?id=1039541 Link to standard: https://drafts.csswg.org/css-text-3/#text-align-last-property [1] https://groups.google.com/a/chromium.org/d/msg/blink-dev/3aLXO38uGI0/t9TtzeZInkMJ [2] https://www.chromestatus.com/metrics/css/popularity#text-align-last - Xidorn ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform