Intent to ship: new syntax of rgb(), rgba(), hsl(), and hsla() functions in CSS

Summary: The change we are shipping includes: * making rgb() and hsl() accept an optional alpha value * making rgb() and hsl() accept new whitespace-separated syntax e.g. rgb(0 0 0 / 100%) * making rgba() and hsla() alias of rgb() and hsl() correspondingly (Please correct me if I was wrong, since I

Re: Intent to ship: support "basic shapes" for the CSS 'clip-path' property

On Tue, Feb 7, 2017, at 08:00 PM, Boris Zbarsky wrote: > On 2/7/17 3:03 AM, Ku(顧思捷)CJ wrote: > > https://drafts.fxtf.org/css-masking-1/#the-clip-path > > https://drafts.csswg.org/css-shapes-1/#supported-basic-shapes > > How stable are these specs? They don't seem to be anywhere near CR, and

test

This is for testing purpose, and should not be published to the list. ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform

Re: test

Sorry for the noisy... It was meant to test whether the mailing list works again... But I picked the wrong email address so it got published. Please ignore this one. - Xidorn On Fri, Feb 10, 2017, at 01:44 PM, Xidorn Quan wrote: > This is for testing purpose, and should not be published to

Re: Intent to implement and ship: only allow Flash on HTTP/HTTPS sites

On Fri, Feb 10, 2017, at 04:29 AM, Benjamin Smedberg wrote: > Will this also prevent loading downloaded .swf files into Firefox? This > is > > useful for running Flash games, which tend to work best in the browser > > (some media players also support loading Flash files, but their hotkeys > > tend

Re: Intent to implement: CSS text-justify property

On Fri, Feb 10, 2017, at 12:33 AM, Patrick Brosset wrote: > > > > DevTools bug: It's not yet clear to me whether specific DevTools work will > > be needed. > > > > I don't think we need anything now, the property should work in the > inspector's Rules panel just like other properties. > Although w

Intent to unship: xml:base attribute

Tracking bug: https://bugzilla.mozilla.org/show_bug.cgi?id=903372 Summary: * It has been removed from the spec years ago. * No other browser supports it. * We pay performance penalty for it. * It makes things trickier for stylo to handle URL values. The tricky thing is that nsParserUtils::ParseFr

Re: Intent to unship: xml:base attribute

On Thu, Feb 16, 2017, at 10:25 PM, Gijs Kruitbosch wrote: > On 16/02/2017 06:51, Xidorn Quan wrote: > > Tracking bug: https://bugzilla.mozilla.org/show_bug.cgi?id=903372 > > > > Summary: > > * It has been removed from the spec years ago. > > * No other browser supp

Re: Intent to unship: xml:base attribute

On Fri, Feb 17, 2017, at 01:36 AM, Boris Zbarsky wrote: > On 2/16/17 7:12 AM, Xidorn Quan wrote: > > The perf penalty of xml:base is basically that we have to dynamically > > construct a URL from bottom to top along the tree whenever we need a > > base URL of an element. And

Re: Intent to unship: xml:base attribute

On Fri, Feb 17, 2017, at 01:38 AM, Ehsan Akhgari wrote: > On 2017-02-16 1:51 AM, Xidorn Quan wrote: > > Tracking bug: https://bugzilla.mozilla.org/show_bug.cgi?id=903372 > > > > Summary: > > * It has been removed from the spec years ago. > > * No other

PSA: Putting at the start of header / source file may break Windows build

There is an issue [1] in our STL wrappers that, when is the first include in a source file, build would fail inside system header with MSVC. It doesn't always show up immediately when you do so because of unified source. But things may start being broken weirdly when someone tries to add new file

Intent to unship: "-moz-table-border-non-zero" pseudo-class outside UA stylesheet

Currently this prefixed pseudo-class is accessible everywhere, but it is actually only used in our UA stylesheet so far. In bug 1341925 [1], I'd like to restrict this pseudo-class to only be usable inside UA stylesheet. [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1341925 - Xidorn __

Re: Editing vendored crates

On Mon, Feb 27, 2017, at 09:10 AM, Bobby Holley wrote: > On Sun, Feb 26, 2017 at 9:51 AM, Henri Sivonen > wrote: > > > I tried to add some panics to a vendored to create (rust-encoding) to > > see if the code in question runs. However, I didn't get to the running > > part, because the edited code

Re: Should cheddar-generated headers be checked in?

On Mon, Feb 27, 2017, at 02:33 AM, Henri Sivonen wrote: > On Thu, Feb 23, 2017 at 4:37 PM, Ted Mielczarek > wrote: > > On Thu, Feb 23, 2017, at 06:40 AM, Emilio Cobos Álvarez wrote: > >> On Thu, Feb 23, 2017 at 08:25:30AM +0200, Henri Sivonen wrote: > >> > On Wed, Feb 22, 2017 at 5:49 PM, Ted Miel

Re: Heads Up: /storage upgraded from version 1.0 to 2.0

On Wed, Mar 8, 2017, at 09:59 AM, Jan Varga wrote: > On 07/03/17 23:43, Robert Strong wrote: > > Are there any problems experienced by clients that downgrade to an > > older version after their profile has been upgraded? > > > This major version change is downgrade-incompatible, so IndexedDB and

Intend to unship: -moz-force-broken-image-icon property

I intend to remove the prefixed CSS property -moz-force-broken-image-icon in bug 1348208 [1], and add a new "browser.display.force_show_broken_image_placeholder" pref to replace it. This property is for forcing showing the image placeholder for broken images. It is initially added for making Gecko

Intent to unship: Window.getDefaultComputedStyle

In bug 1355683 [1], I intent to unship Window.getDefaultComputedStyle function. This function is only implemented in Gecko. The corresponding spec added, then renamed, then removed this API. >From the investigation, this API is only used by jQuery [2], and jQuery uses feature detection since they

Intent to unship: -moz-prefixed CSS gradient functions

In bug 1337655 [1], I'm going to disable -moz-prefixed CSS gradient functions by default. We would still have -webkit-prefixed version of those functions which is part of the Compat spec [2]. The assumption is that there wouldn't be too many pages which depend on -moz-prefixed ones without also ha

Re: Intent to unship: xml:base attribute

On Wed, May 24, 2017, at 11:30 AM, Jet Villegas wrote: > xml:base (bug 1349024) has been removed in Nightly 55 for 2 months > now, and we haven't sen any reports of ill effects. Let's have this > testing expand to Beta 55, and on to Release if all goes well. Bug > 1350521 tracks this change riding

Re: How can I run Firefox programatically in fullscreen?

On Tue, Jun 27, 2017, at 07:12 AM, Armen Zambrano Gasparnian wrote: > Asking around, looking on dxr or MDN did not yield something easily. > > I don't want to have to use Marionette in this specific automation > context. Firefox cannot / shouldn't start in full screen mode because it is tricky to

Intent to unship: tree pseudo-element selectors from web content (::-moz-tree-*)

I intent to unship tree pseudo-element selectors from web content in bug 1379031 [1]. This includes the following pseudo-elements: ::-moz-tree-column ::-moz-tree-row ::-moz-tree-separator ::-moz-tree-cell ::-moz-tree-indentation ::-moz-tree-line ::-moz-tree-twisty ::-moz-tree-image ::-moz-tree-cel

Re: Intent to unship: tree pseudo-element selectors from web content (::-moz-tree-*)

On Fri, Jul 7, 2017, at 01:42 PM, Jet Villegas wrote: > Thanks for cleaning this up. > > On Thu, Jul 6, 2017 at 8:29 PM, Xidorn Quan wrote: > > > Although they don't currently match anything on web content, there is > > still some risk for unshipping them. Specif

Re: Intent to unship: tree pseudo-element selectors from web content (::-moz-tree-*)

On Fri, Jul 7, 2017, at 02:24 PM, Jet Villegas wrote: > It looks like there may be a lot more of these: > https://stackoverflow.com/a/25397485 > > How about we just stub out the Stylo impls instead of unshipping the pseudo > in content? I'm not unshipping this for Stylo... I just don't feel this

Re: Intent to unship: tree pseudo-element selectors from web content (::-moz-tree-*)

On Fri, Jul 7, 2017, at 03:55 PM, Frank-Rainer Grahl wrote: > Not using it but will this break remote XUL? XUL shouldn't be usable in content at all. Chrome document which have access to XUL should not be affected. - Xidorn ___ dev-platform mailing list

Re: More Rust code

On Mon, Jul 10, 2017, at 08:29 PM, Nicholas Nethercote wrote: > Firefox now has multiple Rust components, and it's on track to get a bunch > more. See https://wiki.mozilla.org/Oxidation for details.> > I think this is an excellent trend, and I've been thinking about how to > accelerate it. Here'

Re: Coding style question: Meaningless argument names in declarations

On Fri, Sep 8, 2017, at 01:16 AM, Emilio Cobos Álvarez wrote: > This is very context dependent, I'd never omit a name in a function that > takes (Element& aParent, Element& aChild), but it seems reasonable to > omit it in the case where there's no better name, like (InsertionKind > aInsertionKind)

Re: Intent to unship: :-moz-system-metric pseudo-class and media queries in content pages.

On Sat, Sep 2, 2017, at 06:06 AM, Emilio Cobos Álvarez wrote: > Hi dev-platform@, > > I'd like to unship access to the :-moz-system-metric pseudo-class, and > the system metric media queries, from content pages. I just filed > for that. > > T

Re: Visual Studio 2017 coming soon

On Thu, Oct 26, 2017, at 12:24 PM, Ted Mielczarek wrote: > On the other hand, it's easier to > justify dropping support if VS is the last compiler holding us back from > being able to use new C++ features. FWIW, it's not at the moment. Currently we are really only blocked on GCC for new C++ featur

Re: Intent to require Python 3 to build Firefox 59 and later

I'm happy hearing this. I would be interested on whether we are going to drop Python 2 at some point, or are we stuck with that forever? Also I'm curious what modern features are the team looking forward to? - Xidorn On Sat, Nov 11, 2017, at 10:27 AM, Gregory Szorc wrote: > For reasons outlined

Re: Intent to unship: mozmm CSS unit.

On Mon, Nov 13, 2017, at 02:11 AM, Emilio Cobos Álvarez wrote: > Hi, > > In bug 1416564 I intend to remove the mozmm CSS unit. > > This unit is Mozilla-only, has no spec, and is unused in all our > codebase (except for two tests, one of those which tests the unit > itself). > > This unit was in

Late Intent to unship: several internal CSS properties with Stylo

There are several CSS properties, which are supposed to be internal, unintentionally unshipped from web content with Stylo. We didn't notice that until we started looking at internal properties support in chrome. The properties already unshipped in Firefox 57 are: -moz-window-opacity -moz-window-t

Re: Hiding 'new' statements - Good or Evil?

On Tue, Nov 28, 2017, at 11:45 AM, Eric Rescorla wrote: > On Mon, Nov 27, 2017 at 4:07 PM, smaug wrote: > > And auto makes code reading harder. It hides important information like > > lifetime management. > > It happens easily with auto that one doesn't even start to think whether > > nsCOMPtr/Ref

Re: Hiding 'new' statements - Good or Evil?

On Wed, Nov 29, 2017, at 12:56 AM, Eric Rescorla wrote: > On Mon, Nov 27, 2017 at 6:41 PM, Xidorn Quan wrote: >> On Tue, Nov 28, 2017, at 11:45 AM, Eric Rescorla wrote: >> > On Mon, Nov 27, 2017 at 4:07 PM, smaug wrote: >> > > And auto makes code read

Re: Intent to unship: @-moz-document from content pages.

On Thu, Nov 30, 2017, at 03:53 AM, Emilio Cobos Álvarez wrote: > Hi again, > > In bug 1035091 I intend to remove support for the @-moz-document CSS > rule in content pages (more exactly in author stylesheets). > > The reasoning for this, apart from it being a non-standard mozilla-only > CSS featu

Re: Intent to ship: CSS Shapes Module Level 1 (partial)

On Thu, Nov 30, 2017, at 07:16 AM, Mats Palmgren wrote: > I think supporting only a subset of the valid values for a property > is problematic. > > CSS conformance rules says: > "[...] the user agent must parse the value according to the property > definition. This means that the user agent must a

Re: Intent to ship: Do not allow a http-auth prompt requested by an image resource loaded from a cross-origin

On Wed, Dec 6, 2017, at 01:25 AM, Dragana Damjanovic wrote: > Hi all, > > We have implemented this for a log time, but the pref was turned off. > I intend to switch on the pref for this in bug 1423146. > After the pref is switched a http-authentication dialog prompt will not > be > shown if it is

Re: New prefs parser has landed

On Fri, Feb 2, 2018, at 10:40 AM, Nicholas Nethercote wrote: > [*] One tricky question is what to do with syntax errors. The current > behaviour is here: > https://searchfox.org/mozilla-central/source/modules/libpref/Preferences.cpp#1000-1011. > It writes the error to the browser console, but if th

Re: Why do we track bidiness on text nodes?

On Tue, Feb 6, 2018, at 12:09 AM, Henri Sivonen wrote: > We appear to track bidiness on the document and on the text nodes. The > document-level comment says: > /** >* Indicate the document contains bidi data. >* Currently, we cannot disable bidi, because once bidi is enabled, >* it aff

Re: Intent to require Node to build Firefox 61 and later

On Thu, Mar 1, 2018, at 11:23 AM, Nicholas Alexander wrote: > The requirement will likely be Node v8.9.4, the current LTS release. MozillaBuild currently provides Node v8.9.0. If you are going to require a version higher than that, probably it'd be better to coordinate with the A-team to release

Re: FYI: Short Nightly Shield Study involving DNS over HTTPs (DoH)

It's fine to embed this experiment in the product, and blog about it, but it's definitely not fine to have it enabled by default and send every DNS request to a third-party. I can understand that the intent must be good, and for better privacy, but the approach of doing so is not acceptable. Us

Re: Hey! Can you please briefly try this test build...

FWIW, I always find that the easiest way to run some build is using mozregression's "Run a single build", which would take care of downloading, unpacking, and creating a new profile for it. In this case, you'd want to choose "try" and input changeset "b5a512aaef49". - Xidorn On Fri, Apr 20, 20

Re: Intent to implement: AudioWorklet

On Wed, May 2, 2018, at 11:34 PM, Tom Ritter wrote: > On Wed, May 2, 2018 at 5:11 AM, Robert O'Callahan > wrote: > > On Wed, May 2, 2018 at 9:21 PM, Karl Tomlinson wrote: > > > >> It seems that Chrome works around this by choosing to garbage > >> collect input nodes even when their presence is s

Re: Removing tinderbox-builds from archive.mozilla.org

Would removing those files affect the ability of mozregression to locate pushes of old regressions? - Xidorn On Wed, May 9, 2018, at 4:49 PM, ntho...@mozilla.com wrote: > We have approximately 400 TB of old files in the two directories > firefox/tinderbox-builds and mobile/tinderbox-builds on >

Re: Update on rustc/clang goodness

On Fri, May 11, 2018, at 10:35 AM, Anthony Jones wrote: > I have some specific requests for you: > > Let me know if you have specific Firefox related cases where Rust is > slowing you down (thanks Jeff [7]) > Cross language inlining is coming - avoid duplication between Rust > and C++ in

Re: Intent to unship: CSSStyleDeclaration.getPropertyCSSValue

Given that you are unshipping this... probably we should uplift a pref switch to beta to make it unship in 61 directly, and then remove in 62. I think that's probably safer than not unshipping it in 61 but removing directly in 62. - Xidorn On Sat, May 12, 2018, at 7:30 PM, Emilio Cobos Álvarez

Intent to unship: DOMAttrModified and DOMSubtreeModified event for changes via CSSOM

In bug 1460295[1], I intend to stop triggering DOMAttrModified event as well as the general event DOMSubtreeModified for changes on style attribute via CSSOM by default. This behavior will be controlled by a pref "dom.mutation-events.cssom.disabled" so that we can revert it if necessary. Blink

Re: Launch of Phabricator and Lando for mozilla-central

On Thu, Jun 7, 2018, at 12:57 AM, Mark Côté wrote: > Phabricator is a suite of applications, but we are primarily using the > code-review tool, called Differential, which will be taking the place of > MozReview and Splinter. Bug tracking will continue to be done with > Bugzilla, which is integra

Re: Rust crate approval

On Mon, Jul 2, 2018, at 9:03 AM, Eric Rescorla wrote: > On Sat, Jun 30, 2018 at 9:35 AM, Lars Bergstrom > wrote: > > > On Fri, Jun 29, 2018 at 8:33 AM, Tom Ritter wrote: > > > > > > > > I know that enumerating badness is never a comprehensive solution; but > > > maybe there could be a wiki page

Intent to implement: Scrollbar color properties

Summary: Two CSS properties scrollbar-{face,track}-color to style scrollbars in a color by author. These properties intends to provide a more restricted feature set for controlling scrollbar styling than ::-webkit-scrollbar-* pseudo-elements shipped in WebKit and Blink, so that authors can get

Re: Intent to implement: Scrollbar color properties

On Tue, Jul 10, 2018, at 7:36 AM, Tantek Çelik wrote: > >> Platform coverage: Desktop > > > > Why not on mobile? > > Requires platform specific code that just hasn't been written (yet) > for mobile platforms. Actually I don't really have a plan to support the rendering part of scrollbar color pr

Re: Fission MemShrink Newsletter #1: What (it is) and Why (it matters to you)

On Fri, Jul 13, 2018, at 7:08 AM, smaug wrote: > One thing to remember that some of the child processes will be more > important than others. For example all the processes used for browsing > contexts in > the foreground tab should probably prefer performance over memory (in > cases that is som

Re: Intent to implement: Scrollbar color properties

On Wed, Jul 25, 2018, at 6:29 PM, Karl Tomlinson wrote: > Is there a plan to avoid the contrast problems we have mixing > document colors with system colors in other widgets? > > e.g. If one scrollbar color is specified by the document, then what ensures > that other parts of the scrollbar are vis

Re: Intent to implement: Scrollbar color properties

On Thu, Jul 26, 2018, at 7:44 AM, Karl Tomlinson wrote: > Thanks very much for answering some of my questions for me. > > Xidorn Quan writes: > > > On Wed, Jul 25, 2018, at 6:29 PM, Karl Tomlinson wrote: > >> Is there a plan to avoid the contrast problems we have mixin

Intent to implement: CSS property scrollbar-width

Summary: scrollbar-width is a property to control the width (thickness) of scrollbars of an element. In my current implementation plan, it accepts three keywords: auto | thin | none. "thin" would generate a thinner scrollbar suitable for narrow container, and "none" would hide the scrollbar with

Intent to unship: overflow: -moz-scrollbars-* values

In bug 1481125[1], I'm going to put some moz-prefixed values of overflow shorthand property behind pref, and disable them by default on all channel. The values being unshipped are: * -moz-scrollbars-none * -moz-scrollbars-horizontal * -moz-scrollbars-vertical Their functionality can be fully rep

Re: Selectors to Standardize

On Thu, Aug 20, 2015 at 6:33 AM, fantasai wrote: > > :-moz-full-screen > :-moz-full-screen-ancestor :-moz-full-screen has been standardized as :fullscreen in Fullscreen API Standard [1], and that spec also introduces a new pseudo-element ::backdrop which has been implemented in Blink and Trid

Re: API request: MutationObserver with querySelector

On Sat, Sep 19, 2015 at 5:19 PM, Cameron McCormack wrote: > We could probably use the same mechanism that we do for restyling, > effectively modelling any registered selector observers as an additional > style sheet rule (that doesn’t have any properties set in it). All of > the data we store in

Intent to implement and ship ::backdrop pseudo-element for Fullscreen API

Summary: This pseudo-element is rendered immediately below every fullscreen element, and covers the other part of the document by default. This is part of the effort to update our Fullscreen API implementation to the latest spec. And it is the last non-trivial part before I'm going to unprefix the

Re: Intent to implement and ship ::backdrop pseudo-element for Fullscreen API

On Sun, Oct 18, 2015 at 12:59 AM, Jean-Yves Perrier wrote: > On 16/10/2015 02:39, Xidorn Quan wrote: > >> Blink has shipped this pseudo-element unprefixed for modal >> element (but not yet for fullscreen) >> > I have a side question here: do we plan to support ::b

Re: Questions about how to land stuff etc ?

On Tue, Oct 20, 2015 at 6:51 PM, Carsten Book wrote: > Hi, > > we as Sheriffs get sometimes questions what to take care of when you want > to set the checkin-needed keyword and how the process goes etc ? Or what do > if you want/need to do a security bug checkin? > > So when you anytime any questi

Re: Date, time, week, month and datetime attributes in the in Firefox

On Fri, Oct 30, 2015 at 10:25 AM, Ehsan Akhgari wrote: > On 2015-10-29 7:21 PM, Carlos Valim Coragem wrote: >> >> It seems that this problem only happens in the desktop version and not >> in >> mobile, I just did a test with the same webpage in version 34.0.1 of >> Firefox to Android and it wor

Re: Date, time, week, month and datetime attributes in the in Firefox

On Fri, Oct 30, 2015 at 3:57 PM, Jonas Sicking wrote: > On Thu, Oct 29, 2015 at 9:38 PM, Xidorn Quan wrote: >> On Fri, Oct 30, 2015 at 10:25 AM, Ehsan Akhgari >> wrote: >>> On 2015-10-29 7:21 PM, Carlos Valim Coragem wrote: >>>> >>>> It see

Re: Date, time, week, month and datetime attributes in the in Firefox

On Fri, Oct 30, 2015 at 6:57 PM, Jonas Sicking wrote: > On Fri, Oct 30, 2015 at 12:36 AM, Xidorn Quan wrote: >> Authors sometimes just want something usable. It doesn't matter if it >> is not stylable, or it doesn't fit in the UI. When they really need to >> start

Re: Intent to ship: Web Speech API - Synthesis

On Tue, Nov 3, 2015 at 9:42 AM, Eitan Isaacson wrote: > As of this week, I intend to turn on the speech synthesis API on by default > for the desktop browser. It has been enabled in b2g for the last few years. > Thanks to work by Makoto Kato, and Yash Girdhar, we now have support for > speech in a

Re: Error of OS X build (c-c TB)

Have you checked your log here: https://treeherder.mozilla.org/logviewer.html#?job_id=11934&repo=try-comm-central - Xidorn On Sat, Nov 14, 2015 at 1:05 PM, ISHIKAWA,chiaki wrote: > Hi, > > I am trying to test my patches by building C-C TB under OS X using try > server. > However, the build fails

Re: Error of OS X build (c-c TB)

On Sun, Nov 15, 2015 at 1:05 PM, ISHIKAWA,chiaki wrote: > On 2015/11/14 12:31, Xidorn Quan wrote: >> >> Have you checked your log here: >> >> https://treeherder.mozilla.org/logviewer.html#?job_id=11934&repo=try-comm-central >> >> - Xidorn > > >

Intent to implement and ship: text-emphasis

Summary: It implements emphasis marks which are symbols next to each character to emphasize a piece of text. It is mainly used in East Asian documents. Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1225012 Link to standard: https://drafts.csswg.org/css-text-decor-3/#emphasis-marks Platform c

Re: Intent to ship: unicode-range

On Thu, Nov 19, 2015 at 5:16 PM, John Daggett wrote: > We intend to ship unicode-range in Firefox 44. It has been implemented for > non-Linux platforms for over a year now behind the > "layout.css.unicode-range.enabled" pref. The pref has been enabled by > default for Nightly and Developer builds

Re: Intent to Implement: HTML and tags

On Fri, Nov 20, 2015 at 6:22 AM, Jonas Sicking wrote: > I'll give the same feedback here as I did for . > > I don't think authors will use this very much unless they can style it. This pair of tags has been widely used on the web. The first example is experimental CSS specs like https://drafts.c

Re: Faster Windows builds on Try

That's a great news. Hopefully Windows builds would no longer be a significant backlog anymore. On Fri, Nov 20, 2015 at 7:23 AM, Chris AtLee wrote: > Over the past months we've been working on migrating our Windows builds > from the legacy hardware machines into Amazon. > > I'm very happy to anno

Re: TIFU by using Math.random()

According to the article, SpiderMonkey's PRNG is not much better than V8's. It seems we are using a even older algorithm, although ironically have a better result. After reading this article as well as some introduction from the wikipedia, it seems to me that "xorshift+" is probably the best algor

Re: Why do we flush layout in nsDocumentViewer::LoadComplete?

On Fri, Nov 27, 2015 at 6:15 PM, Axel Hecht wrote: > On 11/27/15 4:09 AM, Robert O'Callahan wrote: >> >> On Fri, Nov 27, 2015 at 3:59 PM, Boris Zbarsky wrote: >> >>> On 11/26/15 9:24 PM, Robert O'Callahan wrote: >>> We've always done it, but I can't think of any good reasons. >>> >>> I'

Re: Improving blame in Mercurial

On Fri, Dec 11, 2015 at 6:17 PM, Gregory Szorc wrote: > If you have ideas for making the blame/annotate functionality better, please > capture them at https://www.mercurial-scm.org/wiki/BlamePlan or let me know > by replying to this message. Your feedback will be used to drive what > improvements

Re: Too many oranges!

On Tue, Dec 22, 2015 at 6:16 AM, Kartikaya Gupta wrote: > So, I propose that we create an orangefactor threshold above which the > tree should just be closed until people start fixing intermittent > oranges. Thoughts? I think oranges on try is somehow different than oranges on integration trees,

Re: unowned orange by team

On Wed, Dec 23, 2015 at 12:15 PM, Ben Kelly wrote: > dom: > 14) https://bugzilla.mozilla.org/show_bug.cgi?id=1197786 > layout: > 19) https://bugzilla.mozilla.org/show_bug.cgi?id=1204897 These two intermittents are actually the same issue, which is https://bugzilla.mozilla.org/show_bug.cgi?id=1223

Re: "-Moz-Element" -like API by extending WEBGL_dynamic_texture

On Tue, Jan 5, 2016 at 8:46 AM, Kearwood "Kip" Gilbert wrote: > Hello All, > > In WebVR, we often present UI as a Head's Up Display (HUD) that floats > in front of the user. Additionally, we often wish to show 2d graphics, > video, and CSS animations as a texture in 3d scenes. Creating these > t

Re: nsThread now leaks runnables if dispatch fails

On Wed, Jan 6, 2016 at 3:53 AM, Kyle Huey wrote: > On Mon, Jan 4, 2016 at 4:10 PM, Randell Jesup wrote: >> >> Yup. In cases where we anticipate a possible Dispatch failure (which is >> supposed to become impossible, but isn't currently) you can use the >> (still-existing) raw ptr interface and h

Re: nsThread now leaks runnables if dispatch fails

On Thu, Jan 7, 2016 at 6:47 AM, Karl Tomlinson wrote: > Xidorn Quan writes: > >> On Wed, Jan 6, 2016 at 3:53 AM, Kyle Huey wrote: >>> On Mon, Jan 4, 2016 at 4:10 PM, Randell Jesup wrote: >>>> >>>> Yup. In cases where we anticipate a possible Dispa

Re: GTests are now running on test machines

On Thu, Jan 14, 2016 at 10:22 AM, Christopher Manchester wrote: > GTests are now run from their own job on Treeherder instead of during the > build in "make check'. They can be found under the "GTest" symbol on > treeherder on all integration branches, and can be added to try pushes with > "-u gte

Re: Does SSE2 usage still need to be conditional?

On Tue, Feb 2, 2016 at 7:04 AM, Benjamin Smedberg wrote: > > > On 1/29/2016 2:05 PM, Cameron Kaiser wrote: >> >> On 1/29/16 9:43 AM, Ashley Gullen wrote: >>> >>> FWIW, the Steam Hardware Survey says 99.99% of users have SSE2 (under >>> "other settings"): http://store.steampowered.com/hwsurvey >> >

Re: Does SSE2 usage still need to be conditional?

On Tue, Feb 2, 2016 at 10:42 AM, Milan Sreckovic wrote: > >> On Feb 1, 2016, at 18:00 , Xidorn Quan wrote: >> ... >> >> It seems to me if we do, whether enabling SSE2 on x86 doesn't really >> matter unless we have a good reason. Fewer and fewer people would

Re: Does SSE2 usage still need to be conditional?

On Tue, Feb 2, 2016 at 11:09 AM, Nicholas Nethercote wrote: > On Tue, Feb 2, 2016 at 10:55 AM, Xidorn Quan wrote: >>> >>> Surprisingly, perhaps, there are a lot of people using Firefox on 32-bit >>> Windows. If I’m reading the data correctly, more than half. A

Re: Does SSE2 usage still need to be conditional?

On Tue, Feb 2, 2016 at 11:31 AM, Chris Peterson wrote: > On 2/1/16 3:56 PM, Mike Hommey wrote: >> 64-bits Firefox was only officially released recently, and AFAIK, we're not >> offering 32-bits Firefox users an upgrade to 64-bits Firefox if their >> system permits. How about we started doing that?

Re: APNG and Accept-Encoding

On Mon, Feb 22, 2016 at 10:26 PM, Gervase Markham wrote: > On 21/02/16 14:30, maxste...@gmail.com wrote: >> Here's interesting live example, this website provides lots of >> animated cursors to download, and they show them online as APNGs in >> Firefox and Safari, and as GIFs in other browsers. Cu

Re: APNG and Accept-Encoding

On Tue, Feb 23, 2016 at 10:14 PM, Anne van Kesteren wrote: > On Tue, Feb 23, 2016 at 12:37 AM, Mike Lawther > wrote: >> I'm testing the water here :) Is this at all likely to fly? > > I think the problem with APNG, as opposed to other image formats, > e.g., WebP, is that we already support it. I

Re: Proposing preferring Clang over GCC for developer buidls

On Thu, Mar 3, 2016 at 6:50 AM, Gregory Szorc wrote: > Over in bug 1253064 I'm proposing switching developer builds to prefer > Clang over GCC because the limited numbers we have say that Clang can build > mozilla-central several minutes faster than GCC (13 minutes vs 17.5 on my > I7-6700K). I'm n

Re: Try syntax is no longer required when pushing to try

On Fri, Mar 4, 2016 at 1:25 AM, Andrew Halberstadt wrote: > With treeherder's "Add New Jobs" [1] UI, using try syntax is no longer > the only way to schedule stuff on try. As of now, it's possible to push > to try without any try syntax. If you do this, no jobs will be scheduled > on your push an

Re: Are we in favour of implementing the client hints header?

On Tue, Mar 8, 2016 at 7:40 PM, Gervase Markham wrote: > On 08/03/16 06:22, Andrew Overholt wrote: > > Implement Client-Hints HTTP header > > https://bugzilla.mozilla.org/show_bug.cgi?id=935216 > > Well, we are in favour of adaptive content, progressive enhancement, > responsive images in HTML,

Re: The convention to pass a parameter when ownership transfer is optional

On Fri, Mar 18, 2016 at 11:07 AM, wrote: > > https://hg.mozilla.org/mozilla-central/file/3e04659fdf6aef792f7cf9840189c6c38d08d1e8/mfbt/UniquePtr.h#l182 > > "To unconditionally transfer ownership of a UniquePtr into a method, use a > |UniquePtr| argument. To conditionally transfer ownership of a

Intent to implement and ship: text-combine-upright: all

Summary: According to some people from Japanese ebook companies, text-combine-upright (a.k.a horizontal-in-vertical, or tate-chu-yoko) is a must for Japanese vertical layout. Without the proper support of this feature, a book may not be considered complete, and thus cannot be sold online. This is a

Re: Intent to switch to Visual Studio 2015

On Fri, Mar 25, 2016 at 12:44 AM, Gregory Szorc wrote: > On Wed, Mar 23, 2016 at 7:03 PM, Gregory Szorc wrote: > > > On Wed, Mar 16, 2016 at 11:49 PM, Gregory Szorc wrote: > > > >> > >> On Thu, Mar 10, 2016 at 8:14 AM, Gregory Szorc wrote: > >> > >>> Visual Studio 2015 has been out for a while

Re: Announcing MozillaBuild 2.2.0 Release

On Wed, Mar 30, 2016 at 12:30 PM, Ryan VanderMeulen < rvandermeu...@mozilla.com> wrote: > I am pleased to announce the final release of MozillaBuild 2.2.0. > > http://ftp.mozilla.org/pub/mozilla.org/mozilla/libraries/win32/MozillaBuildSetup-Latest.exe I'd suggest you use https instead, it seems

Re: Why is Mozreview hassling me about squashed commits?

On Mon, Apr 4, 2016 at 11:09 AM, L. David Baron wrote: > On Saturday 2016-04-02 18:51 -0300, Eric Rescorla wrote: > > 1. I write a bunch of code, committing along the way, so I have a lot of > > commits named "Checkpoint" and "Fix bug" and the like. > > 2. When it works, I push the code up to the

Re: CSS Triggers

On Wed, Feb 24, 2016 at 8:53 AM, Boris Zbarsky wrote: > On 2/23/16 4:18 PM, Jordan Santell wrote: > >> are there any other suggestions on how we >> can observe this data and minimize incorrect results? >> > > In an automated way, or manually? > > Because you can look at nsStyleStruct.cpp to figur

Re: Coding style for C++ enums

On Mon, Apr 11, 2016 at 5:17 PM, Chris Peterson wrote: > On 4/8/16 8:10 AM, Kartikaya Gupta wrote: > >> Is there a recommendation for what enum values in C++ code should be >> styled as? The coding style doesn't say and we use a variety of things >> in existing code, so I was wondering if we shou

Re: Intent to Ship: HTML5 and tags

On Thu, Apr 14, 2016 at 6:51 PM, Ting-Yu Lin wrote: > On Firefox: > summary::-moz-list-bullet { list-style-type: none; } OR summary { > display: block; } Shouldn't "summary { list-style-type: none; }" be enough? - Xidorn ___ dev-platform mailing li

Re: Intent to ship: Treat cookies set over non-secure HTTP as session cookies

On Thu, Apr 14, 2016 at 6:54 PM, Chris Peterson wrote: > > Do other browser engines implement this? No > I have no particular thought about the idea itself, but it seems to me this is a breaking change to the web. As it's a major breaking change, I don't think we should do this without support

Re: Intent to Implement/Ship: -webkit-text-stroke

On Thu, Apr 14, 2016 at 7:40 PM, Ms2ger wrote: > On 14/04/16 09:26, Jeremy Chen wrote: > > *Summary*: We don't currently support -webkit-text-stroke; however, it > has > > been available for years in webkit based browsers and has seen widespread > > usage on the web. This css property is current

Re: PSA: Cancel your old Try pushes

On Sat, Apr 16, 2016 at 1:47 AM, Ryan VanderMeulen < rvandermeu...@mozilla.com> wrote: > I'm sure most of you have experienced the pain of long backlogs on Try > (Windows in particular). While we'd all love to have larger pools of test > machines (and our Ops people are actively working on improvi

Re: PSA: Cancel your old Try pushes

On Sat, Apr 16, 2016 at 10:24 AM, Steve Fink wrote: > On 04/15/2016 05:11 PM, Xidorn Quan wrote: > >> On Sat, Apr 16, 2016 at 1:47 AM, Ryan VanderMeulen < >> rvandermeu...@mozilla.com> wrote: >> >> I'm sure most of you have experienced the pain of long b

  1   2   3   >