Intent to ship: unprefixed appearance property

I intend to land bug 1620467 tomorrow, which implements the unprefixed appearance property and removes many non-standard values of -moz-appearance. Intent to Prototype mail: https://groups.google.com/g/mozilla.dev.platform/c/nlun5QV63Bo/m/xUXCmySGAgAJ The only things that have changed since

Intent to prototype: unprefixed appearance property

Summary: The appearance property allows authors to specify that a widget element (such as a form control element) is to be rendered as a regular element without its usual themed appearance. For example, `appearance: none` on a prevents the element from being rendered with its usual

Re: Intent to ship: a change to the initial value of image-orientation

On Mon, Feb 17, 2020, at 8:19 AM, Cameron McCormack wrote: > This doesn't really fit the format of an Intent email, but just as a > heads up, I am landing a change to the initial value of the > image-orientation property, from "none" to "from-image". The effect o

Re: Intent to unship: FTP protocol implementation

If you plan to time the unshipping of our FTP support to be after Chrome 81, then please be aware that Chrome releases are currently paused on Chrome 80. https://chromereleases.googleblog.com/2020/03/upcoming-chrome-and-chrome-os-releases.html On Thu, Mar 19, 2020, at 8:56 PM, Michal Novotny

Re: Land your tests for now-public security bugs

On Tue, Mar 10, 2020, at 10:33 AM, Daniel Veditz wrote: > We need to do better at the remembering-to-land part. If you've fixed a > security > bug in the past please check if you have any hanging *in-testsuite?* bugs > for bugs that are now public. Thank you for the reminder. (I've got tests

Re: Intent to ship: a change to the initial value of image-orientation

On Mon, Feb 17, 2020, at 9:12 PM, Anne van Kesteren wrote: > Where is this standardized? https://drafts.csswg.org/css-images-3/#the-image-orientation > See https://github.com/whatwg/html/issues/4495 for some tricky questions > that come up that haven't been conclusively answered yet, as far as I

Intent to ship: a change to the initial value of image-orientation

This doesn't really fit the format of an Intent email, but just as a heads up, I am landing a change to the initial value of the image-orientation property, from "none" to "from-image". The effect of this change is that EXIF orientation data in JPEG images used in HTML elements and in the CSS

Re: Intent to ship: CSS subgrid

On Fri, Oct 18, 2019, at 9:31 AM, ikilpatr...@chromium.org wrote: > I'd argue that the color example is a "trivial" feature, unlike > subgrid. But the original framer of the policy would have a better > understanding of what that meant. > > FWIW most new CSS features are placed behind

Re: Intent to unship SVGZoomAndPan interface

On Sun, Sep 29, 2019, at 1:22 PM, Boris Zbarsky wrote: > Sure, we could pass that by making it a mixin, not an interface, but > that says nothing about the `zoomAndPan` attribute on SVGSVGElement and > SVGViewElement. What does the compat situation look like for those? Both Chrome and Safari

Re: What to do about scroll anchoring?

How useful is scroll anchoring outside of the two cases mentioned in https://drafts.csswg.org/css-scroll-anchoring/#intro i.e. images loading and ad iframes being inserted? Would it be feasible to make scroll anchoring a much less general mechanism, and to scope it down to handling these

Re: Intent to unship SVGZoomAndPan interface

On Sat, Sep 28, 2019, at 11:41 PM, longs...@gmail.com wrote: > In [1] I intend to unship the SVGZoomAndPan interface. The SVG WG > decided to remove this interface in [2] as it's either not implemented > at all or does nothing in current implementations. Our implementation > is currently the

Re: Intend to deprecate: XLink attributes on MathML elements

On Sat, Aug 24, 2019, at 8:31 PM, Frédéric Wang wrote: > In bug 1548524, I intend to deprecate XLink attributes (“href”, “type”, > “show” and “actuate”) on MathML elements. This has never been supported > by other browsers and AFAIK there is not any plan to do so. Gecko > actually only has partial

Re: NS_NewURI is now thread-safe

This is going to let us simplify a whole lot of URL handling code in the style system, where we otherwise have to store strings and lazily creating nsIURIs when we're back on the main thread. Thanks so much! On Mon, Jun 10, 2019, at 1:08 PM, Valentin Gosu wrote: > Hello everyone, > > nsIURI

Re: Intent to unship: hasFeature() method on some SVG elements

On Fri, May 3, 2019, at 8:31 PM, Christopher Mills wrote: > On Fri, May 3, 2019 at 3:38 AM Cameron McCormack wrote: >> The hasFeature() method on some SVG elements comes from SVG 1.0 and was >> intended to be used as part of SVG's extension mechanisms. This function >> ne

Intent to unship: hasFeature() method on some SVG elements

The hasFeature() method on some SVG elements comes from SVG 1.0 and was intended to be used as part of SVG's extension mechanisms. This function never returned anything other than false in browser implementations, and was removed in SVG 2. Chrome no longer supports this, although WebKit still

Re: nsIPresShell has gone

On Fri, May 3, 2019, at 11:44 AM, Masayuki Nakano wrote: > Finally, I completely got rid of nsIPresShell from our tree. > https://bugzilla.mozilla.org/show_bug.cgi?id=253889 Thank you for doing this, Masayuki! ___ dev-platform mailing list

Re: Lack of browser mochitests in non-e10s configuration and support for turning off e10s on desktop going forward

On Thu, Apr 25, 2019, at 7:55 PM, Gijs Kruitbosch wrote: > Ideally, I think the debugging usecase would be better served by a more > barebones "here's a docshell that will load arbitrary content off our > trusted localhost server in 1 process" type app than by making desktop > firefox run these

Re: Proposal to remove unnecessary [type] attributes on script tags in mozilla-central

On Tue, Apr 9, 2019, at 1:56 PM, Cameron McCormack wrote: > You should exclude layout/reftests/w3c-received/ too. layout/reftests/w3c-css/received/ ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/

Re: Proposal to remove unnecessary [type] attributes on script tags in mozilla-central

On Tue, Apr 9, 2019, at 1:39 PM, Brian Grinstead wrote: > I'd like to rewrite markup in the tree to avoid using the [type] > attribute on

Re: SVG text coordinate systems

Hi Alex, On Tue, Apr 2, 2019, at 1:47 AM, Alex Henrie wrote: > Hi, I am trying to fix Bug 1529182,[1] but debugging the SVG > code is particularly difficult for me because it uses at least six > coordinate spaces, and I can't figure out how they relate to each > other: > > - Run space > - Run

MOZ_DBG

Lately I've been finding Rust's dbg!() macro[1] useful for quick debugging. Its main usefulness is in avoiding the need to extract out an expression into a separate variable just so that you can print out its value and then use the value in its original context. I wanted something similar for

Re: Where to put timeout test?

On Wed, Mar 6, 2019, at 5:05 PM, violet.bugrep...@gmail.com wrote: > However, both the reviewer and me don't know how to put a timeout test. > It won't crash in any case, so it's not a crash test. But the mochitest > can only be used to check JavaScript assertion, if I use mochitest, the > test

Intent to implement: -webkit-line-clamp

Summary: -webkit-line-clamp is a feature implemented in WebKit, Blink, and Edge that allows authors to control the height of a block so that it contains at most the specified number of lines, and if there are excess lines, an ellipsis is inserted in the last non-excess line.

Re: Intent to unship: -moz-binding CSS property from content.

On Thu, Jan 31, 2019, at 8:03 AM, Emilio Cobos Álvarez wrote: > In bug 1523712 I intend to unship the `-moz-binding` CSS property from > content pages. Sounds good to me, thanks! ___ dev-platform mailing list dev-platform@lists.mozilla.org

Re: Proposed W3C Charter: SVG Working Group

On Thu, Jan 10, 2019, at 12:38 AM, Henri Sivonen wrote: > A (non-changed) part of the charter says under SVG2: "This > specification updates SVG 1.1 to include HTML5-compatible parsing". Is > that in reference to > https://svgwg.org/svg2-draft/single-page.html#embedded-HTMLElements or > something

Re: Proposed W3C Charter: SVG Working Group

On Mon, Dec 24, 2018, at 4:59 AM, L. David Baron wrote: > Please reply to this thread if you think there's something we should > say as part of this charter review, or if you think we should > support or oppose it. Given our past involvement, we should > probably have some comment, even if it's

Re: nasm will soon become a build dependency

On Fri, Dec 21, 2018, at 3:17 PM, Martin Thomson wrote: > The OP said >= 2.10. But you appear to have that. Oh, missed that. I just tried building some other versions of nasm from source (since 2.11 is the latest packaged in my distribution) and 2.13 was the earliest that I could build with.

Re: nasm will soon become a build dependency

On Fri, Dec 21, 2018, at 11:05 AM, Thomas Daede wrote: > nasm is now required for building on Linux. Is there a minimum version required? I am getting errors like this building: /z/moz/g/third_party/dav1d/src/x86/ipred_ssse3.asm:42: error: operand 1: expression is not simple or relocatable $

Re: Bypassing about:home/privacy page loads on new test profile builds via mach

On Tue, Oct 23, 2018, at 9:53 AM, Kyle Machulis wrote: > Adding the following prefs turns off all new profile about:home loads > and just starts the browser with about:blank: > > [runprefs] > browser.startup.blankWindow=true > browser.newtabpage.enabled=false >

Re: Enabling (many) assertions in opt builds locally and eventually Nightly

On Thu, Sep 20, 2018, at 1:52 AM, Ehsan Akhgari wrote: > While it may be the case that we may need to be more stable for > MOZ_RELEASE_ASSERTs, I very much doubt that every single MOZ_ASSERT in our > codebase is actually a guaranteed to never fail, so promoting them all to > be enabled in

Re: CSS Scroll Snap Level 1

On Wed, Sep 5, 2018, at 7:30 PM, Chris Mills wrote: > https://drafts.csswg.org/css-scroll-snap-1/ > > > Have we got any current or future plans for implementing this in Gecko? Yes, we have an implementation of an earlier draft for this feature,

Layout Bugzilla components

[bcc: firefox-dev, firefox-triage-leads] Hi, The Layout team has done some Bugzilla component reorganization to distribute features and areas of code a bit better. There are a number of new components split out from existing ones: * Previously covered by CSS Parsing and Computation: ** CSS

PSA: static atom definitions have moved to xpcom/ds/StaticAtoms.py

Hi everyone, Just a heads up on some changes to static atoms that I landed a couple of days. Static atom definitions now live in xpcom/ds/StaticAtoms.py. This script generates nsGkAtomList.h at build time. nsGkAtomList.h is still used by nsGkAtoms.{h,cpp} to actually define the C++ atoms and

Re: Intent to implement: Visual Viewport API

On Tue, Jul 24, 2018, at 12:22 PM, Boris Zbarsky wrote: > On 7/23/18 7:36 PM, Tanushree Podder wrote: > > Secure contexts: Yes > > I'm not sure what this line means here. I updated the intent to implement template at https://wiki.mozilla.org/ExposureGuidelines#Intent_to_implement to make it

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

On Fri, Jul 13, 2018, at 6:51 AM, Kris Maglione wrote: > I actually have a patch sitting around with helpers to make it super easy to > use smart pointers as tagged pointers :) I never wound up putting it up for > review, since my original use case went away, but it you can think of any >

Intent to unship: explicit values in image-orientation

https://drafts.csswg.org/css-images-3/#the-image-orientation The CSS image-orientation property allows an author to control whether an image (in an or generated content) is automatically rotated and flipped according to the EXIF data in the image. Originally, the specification only allowed

Re: Intent to Unship: -moz-is-resource-document media feature from content pages.

On Fri, Jun 15, 2018, at 8:02 AM, Emilio Cobos Álvarez wrote: > I expect no compat fallout whatsoever since it can only match, well, in > SVG resource documents, and it was meant to be an internal media feature > in the first place. This is fine. I expect approximately zero content relies on

Re: Is super-review still a thing?

On Thu, Apr 26, 2018, at 12:41 AM, Mark Côté wrote: > How we might use blocking reviewers in our workflow is still open, but > it could be used for training up reviewers, in which case the trainee > would be a regular reviewer and the module peer/owner would be a > blocking reviewer. It's not

Re: Using WebIDL objects in XPIDL

On Thu, Apr 19, 2018, at 1:19 PM, Nika Layzell wrote: > This allows us to avoid using nsISupports to pass WebIDL objects which > don't have corresponding XPIDL interfaces through XPIDL defined methods. Thanks Nika, this is great! Avoiding nsIDOMBlah interfaces in C++ was one of the reasons that

Intent to unship: SVGSVGElement.{pixel, screenPixel}UnitToMillimeter{X, Y}

In https://bugzilla.mozilla.org/show_bug.cgi?id=1133172 I plan to remove our implementations of these four IDL attributes on SVGSVGElement: pixelUnitToMillimeterX pixelUnitToMillimeterY screenPixelUnitToMillimeterX screenPixelUnitToMillimeterY These were originally in SVG 1, but they never had

Re: Intent to implement and ship: ping, rel, referrerPolicy, relList, hreflang, type and text properties on SVG elements

On Tue, Apr 10, 2018, at 11:58 AM, Jeff Gilbert wrote: > Do we have a heuristic for when to /not/ include something from HTML in SVG? If it doesn't make two features which already exist in both HTML and SVG more consistent, then I wouldn't include it. > More or less, these additions to SVG just

Re: Intent to implement and ship: ping, rel, referrerPolicy, relList, hreflang, type and text properties on SVG elements

On Tue, Apr 10, 2018, at 7:56 AM, Jeff Gilbert wrote: > Can we not put more things into SVG? Making SVG more complicated seems > like it should be an anti-goal for the web platform. I think we should align the features and behavior of HTML and SVG . something I don't see why the

Re: PSA: Chrome-only WebIDL interfaces no longer require DOM peer review

On Fri, Mar 9, 2018, at 9:41 AM, Robert O'Callahan wrote: > It might be worth measuring how that translates to installer code. One > might hope that all that repetitive boilerplate code compresses well > (or can be made to). Testing my local bug 1341546 patches, I get a 59 KiB increase in .tar.bz2

Re: PSA: Chrome-only WebIDL interfaces no longer require DOM peer review

On Fri, Mar 9, 2018, at 8:41 AM, Bobby Holley wrote: > The problem is precisely that it's gradual - a few kilobytes at a > time, certainly nothing to trigger our alerts. Waiting for it all to > pile up and then launching a herculean effort to move things _back_ to > XPIDL would be a huge waste of

performing cross-context instanceof checks

Hi, For a long time Firefox's behaviour for instanceof checks on DOM objects, when the right-hand side interface object comes from a different window from the object on the left, has differed from other browsers. For example, otherWindow.document instanceof Node evaluates to true in

Re: De-XBL Plans

On Sat, Oct 21, 2017, at 01:47 AM, Dave Townsend wrote: > Are there any other concerns that we're missing? One thing I'm wondering about is memory usage of the Web Components implementations of these components compared to the XBL ones. Specifically for style, XBL has the ability to list the

Re: Debugging Firefox e10s with rr?

On Tue, Aug 29, 2017, at 08:58 PM, Emilio Cobos Álvarez wrote: > I didn't find any obvious docs in either the rr wiki[1] or MDN, so I > thought I'd ask before I actually need it. > > What is the best/easiest way to debug Firefox multi-process using rr? > > Right now I just disable e10s, but

Re: [PATCH] gfx: thebes: decouple GfxSurfaceType from cairo_surface_type_t

Hi Enrico, Firefox patches should be submitted via Bugzilla, rather than by email to dev-platform. Please see: https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Introduction#Step_4_-_Get_your_code_reviewed Thanks, Cameron On Mon, Jul 31, 2017, at 03:14 PM, Enrico Weigelt, metux

Re: Intent to unship: HTML scoped style sheets (

On Wed, Jun 21, 2017, at 10:56 PM, Ehsan Akhgari wrote: > Why only in the medium term? Restyling is very costly for browser.xul > right now, and it would be very nice if we can use Stylo to gain some > advantages there, especially since costly restyles in the parent process > do mean UI jank

Re: Intent to unship: HTML scoped style sheets (

On Wed, Jun 21, 2017, at 02:05 AM, Bobby Holley wrote: > Yeah - stylo for the frontend would be nice, but it's not part of > our MVP. Thanks for confirming what I thought was the case. :-) On Tue, Jun 20, 2017, at 03:26 PM, Patrick Brosset wrote: > Cameron, what bug should this one block (iiuc

Re: Intent to unship: HTML scoped style sheets (

On Tue, Jun 20, 2017, at 01:08 PM, Jared Wein wrote: > We use a scoped stylesheet for styling the popup for [1]. We > chose this route to limit performance impact as well as limit our > temporary stylesheet from affecting other parts of the browser UI. > Will your removal also remove support in

Intent to unship: HTML scoped style sheets (

HTML scoped style sheets is a feature that allows the effects of style sheets to be scoped to a subtree of a document. Support for this feature was introduced first in Chrome 19 behind a flag (in mid-2012) and in Firefox 21 without a pref (in mid-2013). Since then, Chrome removed their

Re: Introducing mozilla::Result for better error handling

On Tue, Dec 20, 2016, at 09:46 PM, Jan de Mooij wrote: > A few weeks ago we added mozilla::Result to MFBT [0][1]. I was > asked > to inform dev-platform about this, so here's a quick overview. > mozilla::Result is based on Rust's Result type [2]. It contains > either a success value of

Ensuring new CSS features are supported in Quantum CSS

Hi, For the Quantum CSS project, we are aiming not to regress support for CSS features when the Servo-backed style system is turned on. This means that if you are implementing a new CSS feature that will land (behind a pref or not) before Quantum CSS is ready to ship, we'll need to do some work

Re: Intent to Use Counter: Everything

dy expanded shorthands out to their component longhands: https://dxr.mozilla.org/mozilla-central/source/layout/style/nsCSSDataBlock.cpp#712 We could handle shorthands by recording them earlier, up in nsCSSParser somewhere. -- Cameron McCormack ≝ http://mcc.id.au/

Re: Intent to ship: unprefix :dir pseudo-class

ich involves looking at localedir="" on the root element or a pref.) -- Cameron McCormack ≝ http://mcc.id.au/ ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform

Re: #include sorting: case-sensitive or -insensitive?

nclude "bbb/ccc/ddd.h" #include "bbb/eee/fff.h" #include "bbb/ggg.h" #include "ccc.h" or #include "bbb/ccc/ddd.h" #include "bbb/eee/fff.h" #include "bbb/bbb.h" #include "bbb/ggg.h" #include "aaa.h" #include &quo

Re: Returning dictionaries in WebIDL

he object, then you have to use “object” as the type and invoke the type conversions or do the JS property getting in the spec yourself. -- Cameron McCormack ≝ http://mcc.id.au/ ___ dev-platform mailing list dev-platform@lists.mozilla.

Re: Intent to Implement: HTML and tags

to the details. > > An example: Open the example in Chrome or Safari. http://simpl.info/details/ > > Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=591737 Great work Ting-Yu, and thanks very much for picking this up! -- Cameron McCormack ≝ http://mcc.id.au/

Re: API request: MutationObserver with querySelector

ffectively 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 the rule cascade so that we can quickly decide whether a given element needs to have rule matching run again could be re-used. -- Cameron McCo

Re: Operating CSS font parsing and associated font objects all usable from worker threads.

d from other threads, although it might not be too much work to make it threadsafe for the things that 2D canvas contexts need it for. In fact that might be less work than duplicating and <‘font’> parsing. -- Cameron McCormack ≝ http://mcc.id.au/ _

Re: Help needed: define Bugzilla components in moz.build files

in components like Core :: XPCOM. -- Cameron McCormack ≝ http://mcc.id.au/ ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform

Re: Reversely iterating nsTArray

. -- Cameron McCormack ≝ http://mcc.id.au/ ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform

Re: Proposal: Standardize initializer list formatting in our coding style guide

Nicholas Nethercote wrote: This is already present in the example at https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Coding_Style#Classes: class MyClass : public X // when deriving from more than one class, put each on its own line , public Y I have encountered far more

Re: Proposal: Standardize initializer list formatting in our coding style guide

[Sorry, white space got eaten up in the previous mail...] Nicholas Nethercote wrote: This is already present in the example at https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Coding_Style#Classes: class MyClass : public X // when deriving from more than one class, put each

Re: Using c++11 right angle bracket in template code?

On 01/10/14 17:57, Kan-Ru Chen (陳侃如) wrote: It seems all the compilers we use support the c++11 in template, could we start using it in new code? Yes we have some uses of that already. It's also mentioned in https://developer.mozilla.org/en-US/docs/Using_CXX_in_Mozilla_code.

Re: Using c++11 right angle bracket in template code?

On 01/10/14 19:23, Nicholas Nethercote wrote: Note the large, red warning at the top of that page This page is a draft for expository and exploratory purposes. Do not trust the information listed here. I don't know why that page exists with such an authoritative-looking URL. We should make

Re: Using c++11 right angle bracket in template code?

On 02/10/14 09:24, Eric Rescorla wrote: Obviously, if you have some argument that auto is bad programming practice or a hazard and should thus be forbidden, that's something you could make and see if people generally agree... The style guide is probably a better place to describe where we want

Re: Intent to implement: image-rendering: pixelated CSS property-value

On 24/09/14 09:24, Jonas Sicking wrote: Would it make sense to have separate properties for scale up and scale down? With image-rendering being a shorthand for setting both? Separately, isn't image-rendering a bit too generic of a name for setting scaling strategy? I guess it was chosen

Re: Intent to ship: CSS mask-type property

and Blink for more than a year. -- Cameron McCormack ≝ http://mcc.id.au/ ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform

Re: Upcoming changes to Mac package layout, signing

Ben Hearsum wrote: Apple recently announced changes to how OS X applications must be packaged and signed Does this also apply if you run .app/Contents/MacOS/firefox binary manually rather than opening the .app? If developers do update their OS to 10.9.5 when it's released, is there a way

Re: Intent to implement and ship: Improved ruby parsing in HTML with new tag omission rules

On 02/07/14 17:05, Henri Sivonen wrote: On Tue, Jul 1, 2014 at 10:58 PM, Koji Ishii kojii...@gluesoft.co.jp wrote: Platform coverage: all platforms (parsing only, layout will be in separate intents) The parsing change is the easy part. Is there a plan to get the layout part implemented? My

Re: Intent to implement: CSS Font Loading API

On 24/06/14 16:35, Anne van Kesteren wrote: No, no more indexed getters. You should know! Yes hence the something similar. :-) Was just easiest for working with while implementing. Making the object iterable seems like the right thing to do, but our bindings generation scripts don't handle

Re: Intent to implement: CSS Font Loading API

On 24/06/14 16:30, Jonas Sicking wrote: I don't understand why anyone would want to key gets and sets using FontFace instances. I.e. why would you want to ever call fontFaceSet.has(myFontFace). That returning false doesn't really tell you anything about what fonts are or are not loaded. It

Re: Intent to implement: CSS Font Loading API

On 24/06/14 17:21, Anne van Kesteren wrote: That part of IDL is wrong. That needs to be fixed to use Symbol.iterator. Yep, aware of that. And ideally an easier way to define an iterator than having to define the entire thing. E.g. for something like FormData all you need is iterating over

Re: Intent to implement: CSS Font Loading API

On 24/06/14 06:30, Jonas Sicking wrote: Has the [MapClass] issue been resolved yet? No. There's a note in the spec that says [SetClass] will be removed in favour of members on the interface that feel like a Set, but there's nothing concrete in there yet. I'm proceeding with something

Intent to implement: CSS Font Loading API

Summary: The CSS Font Loading API provides a mechanism for authors to load a font from the network that can then be used from the font-family property. This allows control over when the font load happens -- something that fonts referenced by @font-face rules currently occurs only when a glyph

Re: Intent to implement: DOMMatrix

On 05/06/14 07:20, Milan Sreckovic wrote: In general, is “this is how it worked with SVGMatrix” one of the design principles? I was hoping this would be the time matrix rotate() method goes to radians, like the canvas rotate, and unlike SVGMatrix version that takes degrees... By the way, in

Re: Intent to ship: :scope support in querySelector(All)

this on? Anyone actively in agreement? Sounds good to me. -- Cameron McCormack ≝ http://mcc.id.au/ ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform

Re: Graceful Platform Degradation

Jet Villegas: I've asked Cameron McCormack to look into how Firefox and other browsers should behave when under mild to severe stress. As all browser engines have to manage how to run under low memory, feeble network, pegged CPU, weak GPU, low battery, small/slow screens, etc., I think web

Re: Intent to ship: CSS Variables

smaug wrote: Curious, how much have we tested the performance of our implementation and are there some known perf issues? I have not tested. The only extra work we should be doing at the moment when variables aren't used in the style sheet is nsRuleNode::ResolveVariableReferences. That

Intent to ship: CSS Variables

CSS Variables is a feature that allows authors to define custom properties that cascade and inherit in the same way that regular properties do, and to reference the values of these custom properties in the values of regular properties (and other custom properties too).

Intent to ship: paint-order property

The paint-order property is a new property defined in SVG 2 that controls the order that the { fill, stroke, markers } of an element are painted in. I blogged about the feature when it was implemented here: http://mcc.id.au/blog/2013/01/paint-order It lives behind the

Re: Column numbers appended to URLs recently

Jan Honza Odvarko wrote: Next example: http://example.com:80 Now it isn't clear whether it's a port number or a line number. Could we somehow fix this? http://example.com/; is equivalent to http://example.com; so you could just ensure that you output a / when the path is empty.

Re: support for Visual Studio 2010

Ted Mielczarek wrote: Historically we haven't updated toolchains without a pressing reason, since there's a lot of hassle involved. Is there a specific reason you're asking? The two recent things I have had to work around in VS2010 were bugs in handling sized enums 32 bits (enum Blah :

support for Visual Studio 2010

When do we plan to drop support for Visual Studio 2010? I remember at one point that it was not possible to generate builds that ran on Windows XP with VS2010, but Update 1 (released in November) added support for that. ___ dev-platform mailing list

Re: support for Visual Studio 2010

Cameron McCormack wrote: When do we plan to drop support for Visual Studio 2010? I remember at one point that it was not possible to generate builds that ran on Windows XP with VS2010, but Update 1 (released in November) added support for that. Not possible to generate builds that ran

Re: Mozilla Location Services - Heads up

Doug Turner wrote: In the mean time, if you want to help, download the Stumbler application for Android and start helping the world by mapping your area: https://github.com/mozilla/MozStumbler/releases I have the Mozilla location services box ticked in my Firefox for Android. Will that do

using LLDB to debug Gecko

Hi, For those of you who are using LLDB -- either by choice, or against your will after upgrading to OS X 10.9 -- I've added some Gecko-specific LLDB functionality to an .lldbinit file in the tree. I've mainly started with porting across the commands from the in-tree .gdbinit that were

Re: Style guide clarity on C++-isms

Benjamin Smedberg wrote: 1) Bracing of method bodies in a C++ class declaration Currently, C++ method bodies inline within a class declaration are documented to start on the next line, e.g. class B { public: void Method() { // Inline body brace is on the next line, column 2 } }; Mozilla code

Re: Mozilla style guide issues, from a JS point of view

Patrick McManus wrote: Typically I have to choose between 1] 80 columns 2] descriptive and non-abbreviated naming 3] displaying a logic block without scrolling to me, #1 is the least valuable. Thoroughly agree. ___ dev-platform mailing list

Re: Mozilla style guide issues, from a JS point of view

Speaking of the troubles with 80 character line lengths, I find I often need to write variable and function declaration/calls like this: https://hg.mozilla.org/mozilla-central/file/8f1c9cdedba5/layout/style/nsCSSParser.cpp#l429

Re: Style guide clarity on C++-isms

Ehsan Akhgari wrote: Exactly. If we require braces on their own lines for function bodies everywhere, we wouldn't need to solve this! Are you sure? :) There are a bunch of instances of class A { A(int aMember) : mMember(aMamber) {} }; through the tree. Depends how the

Re: nsGUIEvent.h related stuff has been sorted out

builds, and to assert its value inside the As*Event() functions? -- Cameron McCormack ≝ http://mcc.id.au/ ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform

Re: Feature tracking via bug keyword

Lukas Blakk wrote: This wiki page: https://wiki.mozilla.org/Features/Release_Tracking now picks up on the keyword 'feature' in your meta/tracking bugs. Please add this to your feature work to make sure it gets early QA, Stability, PR, User Advocacy, and Release Management awareness in

Re: Poll: What do you need in MXR/DXR?

Brian Smith wrote: * When in blame mode, the revision number of the most change to the line is shown. I would like a link next to every line's revision number that links to the *previous* revision where the line changed. That way, I can navigate the change history much easier. Yes, I think

Re: C++ style question: virtual annotations on methods

Bobby Holley wrote: +1. EIBTI. I agree, though MOZ_OVERRIDE does imply that the function is virtual already, so it may not be so necessary there. There are many cases of member function declarations like: /* virtual */ void theFunction(); I'm assuming this is done because of some

Re: Exposing the CSS/SVG Filters as Canvas API's

Robert O'Callahan wrote: On Fri, Aug 9, 2013 at 9:29 AM, K. Gaddk...@luminance.org wrote: Consider this my +1 in favor of a dedicated .colorMatrix attribute, Good, then I'll expect you to back me up in WHATWG with usecases :-). Why should color matrix become a property if other filters

Re: running tests in HiDPI mode on the build machines

Asa Dotzler wrote: Testing the only Firefox platform that isn't on the above list? Wouldn't it be smarter to test on Windows 7 or some combination of Windows machines where almost all of our users are? If we've got the resources for it, sure. ___

Re: running tests in HiDPI mode on the build machines

jmaher wrote: Can you explain what would need to be done for Android to get into this mode? It might be difficult to make this work with our current solution for automated tests. This proposal is just to affect how content is rendered, by setting that pref. If it's a XUL UI it should render

  1   2   >