On Wed, Mar 20, 2019 at 8:45 AM Hiroyuki Ikezoe wrote:
> The Android backend for prefers-color-scheme didn't get on Firefox 67,
> it's just landed on mozilla-central, will be shipped in Firefox 68.
>
The backend was uplifted into Firefox 67 beta yesterday. So
prefers-c
sumably that’s noted appropriately in some manner in Bugzilla?
>
> On March 19, 2019 at 7:45:53 PM, Hiroyuki Ikezoe (hike...@mozilla.com)
> wrote:
>
> The Android backend for prefers-color-scheme didn't get on Firefox 67, it's
>
> just landed on mozilla-central, will
The Android backend for prefers-color-scheme didn't get on Firefox 67, it's
just landed on mozilla-central, will be shipped in Firefox 68.
Thanks,
hiro
On Sat, Feb 16, 2019 at 5:38 AM Mats Palmgren wrote:
> Summary:
> The 'prefers-color-scheme' media feature is way for pages to detect
> if the
Hello, fantasai!
On Sun, Mar 10, 2019 at 6:14 AM fantasai
wrote:
> 1. Handling overlarge snap areas per
> https://www.w3.org/TR/css-scroll-snap-1/#snap-overflow
> This is important to make content accessible on smaller-than-expected
> screens.
>
I think I've finished this properly, but..
2
Summary:
The scroll snap specification has been significantly changed since we
implemented. scroll-snap-coordinate, scroll-snap-destination and
scroll-snap-points-{x,y} were dropped, instead, scroll-snap-align,
scroll-snap-margin and scroll-snap-padding were added in the spec. Also,
scroll-
I just realized that I did send below message only to Tom. :)
-- Forwarded message --
From: Hiroyuki Ikezoe
Date: Wed, Jul 25, 2018 at 6:59 AM
Subject: Re: Intent to implement and ship: CSS prefers-reduced-motion media
feature for Windows and MacOSX
To: Tom Ritter
Thank you
Summary: By using CSS prefers-reduced-motion media feature, web developers
can provide contents depending on a system setting that users want
*motion-less* content. A WebKit blog post [1] might be useful to know
this feature in more detail.
Bugs: https://bugzilla.mozilla.org/show_bug.cgi?id=1365
Summary: We are about to land bug 1193394 which will change microtask
behavior that our microtask behavior complied with the HTML spec.
We had fixed all test failures but still it's possible that new failures
will
appear before the change gets merged into mozilla-central. If we found any
faile
As of Firefox 57 I intend to turn PerformanceObserver on by default.
It's been enabled on nightly by default for 16 months. Chrome has
already shipped it since 52, WebKit has implemented it since January
2017, but not shipped yet. Edge has not implemented it yet, but as far
as I know they have
In Firefox 51 I indent to turn PerformanceObserver on by default. It has
been developed behind the dom.enable_performance_observer preference.
Chrome has been shipping it[1]. Their 'intent to ship' is [2].
Bug to turn on by default:
https://bugzilla.mozilla.org/show_bug.cgi?id=1271487
Link to
is has caused.
[1] https://treeherder.mozilla.org/logviewer.html#?job_id=8927888&repo=try
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
--
Hiroyuki Ikezoe
_
Summary: Provides an interface for receiving frame performance timing
including composites happening on a separate thread/process. This can
be used to calculate measures of smoothness that incorporate the
effect of async pan and zoom and off-main thread animation.
Bug: https://bugzilla.mozilla.org
On 2012年08月23日 18:11, Justin Lebar wrote:
I encourage you to consider using [infallible] in new code for
attributes whose getters never fail. Not only is it cleaner to call
such methods, but using [infallible] also draws attention to those
attributes which /may/ fail.
Before each time using [
13 matches
Mail list logo
