In bug 1308636 [1], I plan to unship all -moz-prefixed multi-column
properties defined in CSS Multi-column spec [2] and -moz-column-gap [3].
We've shipped column-span in Firefox 71 [4] and completed the support of
all the properties in the multi-column spec. Other standard properties have
been
I'm not aware of any cross-implementation testsuite, but I agree it would
be valuable. I suppose that would fall under the responsibility of the
specification, so I could file an issue in the AVIF spec repo (
https://github.com/AOMediaCodec/av1-avif/issues/), unless anyone has other
suggestions.
We get notified accounts getting blocked in Bugzilla fairly often and the
two biggest causes are systems deciding bugmail is spam, and delivery
problems.
For the first, if you can configure a 'confirmed senders' list for your
email host/service, add "bugzilla-dae...@mozilla.org" to it. That's the
The W3C is proposing a revised charter for:
WebAssembly Working Group
https://www.w3.org/2020/01/wasm-wg-charter-2020-proposed.html
https://lists.w3.org/Archives/Public/public-new-work/2020Jan/0003.html
The differences from the previous charter are:
Hello!
We here in Data Stewardship have been receiving inquiries about how the
Data Collection Review process[0] works now that more products are being
built out of reusable components. What follows is a memo about how to
approach Data Review when you're adding a data collection to a reusable
On Thu, 16 Jan 2020 at 21:59, Sean Voisen wrote:
> On Thu, Jan 16, 2020 at 7:50 AM Sebastian Zartner <
> sebastianzart...@gmail.com> wrote:
>
>> Hi everybody,
>>
>> 2020 is already about two weeks old now and I stumbled over the list of
>> planned CSS features again at
The TextMetrics interface represents the dimensions of a piece of text
in the canvas, as created by the CanvasRenderingContext2D.measureText()
method.
Currently, Gecko only supports the .width attribute, but authors would
also like to determine the actual dimensions that the rendered text
On 1/16/20 11:21 PM, Karl Tomlinson wrote:
Would it be appropriate to state that we don't intend to implement
the Audio Device Client API in Gecko because we don't see a need
for this additional/parallel audio API?
Does anyone other than Google want the Audio Device Client API?
* Something
Just a reminder that the deadline for submitting Fx74 PI requests as well
as feature technical documentation is *today*. Please file your PI requests
and share documentation as soon as possible.
Thanks,
Tania
On Wed, Jan 8, 2020 at 5:55 PM Tom Grabowski wrote:
>
> Similar to what QA did for
Hello,
Here's the list of new issues found and filed by the Desktop Release QA
team in the last 7 days.
Additional details on the team's priorities last week, as well as the
plans for the current week are available at: https://tinyurl.com/yfwt3p5x.
Bugs logged by Desktop Release QA in the
On Monday, January 6, 2020 at 12:51:56 PM UTC+11, Emilio Cobos Álvarez wrote:
> If you need UTF-8 inputs from WebIDL (for example if you are passing the
> input to Rust), chances are you're doing an extra copy from JS.
>
> In bug 1449861 I've added an UTF8String so that you can convert a
>
On 1/20/20 8:44 PM, Marcos Caceres wrote:
Is there a proposal to add this to the WebIDL spec
In the IDL spec, the USVString type is representation-agnostic: it's
Unicode on the IDL side, and doesn't say whether you represent Unicode
as UTF-16, UTF-8, UTF-7, UCS-32, or whatever. So it
On Thu, Jan 16, 2020 at 7:50 AM Sebastian Zartner <
sebastianzart...@gmail.com> wrote:
> Hi everybody,
>
> 2020 is already about two weeks old now and I stumbled over the list of
> planned CSS features again at https://wiki.mozilla.org/CSS.
>
> As the list is totally outdated, I was wondering
Hi,
In Firefox 74, we'll ship the optional chaining operator.
*Bug: *https://bugzilla.mozilla.org/show_bug.cgi?id=1566143
*Standard: *https://tc39.es/proposal-optional-chaining/
*Platform coverage: *All, no pref
*DevTools bug: *N/A.
*Other browsers:* Shipping in Chrome, Shipping in Safari
14 matches
Mail list logo
