Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Intent to ship: Support for color-adjust CSS property

80 views
Skip to first unread message

Tobias Schneider

unread,
Mar 4, 2016, 10:11:52 AM3/4/16
to dev-pl...@lists.mozilla.org
As of Firefox 47 I intend to ship support for color-adjust on all
platforms. Chrome is already shipping this as -webkit-print-color-adjust.

The color-adjust CSS property allow pages to opt in to printing background
colors and images. Chrome is already shipping this and Google Docs is using
it in production (e.g. they highlight text using backgrounds). This is one
of the missing features that prevents Google Docs from printing natively in
Firefox.

Open question:

Should this be implemented behind a preference first or can we ship this
directly? Given the fact that this feature is already used in Google Docs,
we might rather ship this without a prefer off phase.

Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1209273
Link to standard: https://drafts.csswg.org/css-color-4/#color-adjust.

Lawrence Mandel

unread,
Mar 4, 2016, 10:15:37 AM3/4/16
to Tobias Schneider, dev-platform
Whether or not we ship with the feature enabled, the ability to disable a
feature with a pref gives us an easy out if a critical issue is discovered.
(For ex, a code path that results in a top crash.) I suggest that we create
the pref in either case and plan to remove it after a couple of releases if
no critical bugs have come in.

Lawrence

On Thu, Mar 3, 2016 at 11:39 PM, Tobias Schneider <tschn...@mozilla.com>
wrote:
> _______________________________________________
> dev-platform mailing list
> dev-pl...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-platform
>

Eric Shepherd

unread,
Apr 11, 2016, 11:06:45 AM4/11/16
to Lawrence Mandel, Tobias Schneider, dev-platform
A note from the developer docs team: when you do this, please be sure
that you both share the information about the existence of the
preference to the bug about adding the feature -- and be sure to add
dev-doc-needed to the bug for removing the preference. If there's not a
bug for some reason, please file a bug against the developer
documentation telling us the preference and the feature it controls, so
we can properly document its removal for developers.

The best way to do this is to include in the Bugzilla comment when you
add dev-doc-needed a note about the name of the preference and that it's
been added or removed. But anywhere that it stands out to the writers
when we look at the bug is helpful.

Thanks in advance for your help!

(This is of course great general advice whenever a feature is introduced
behind a pref, btw).

------------------------------------------------------------------------
*From:* Lawrence Mandel
*Sent:* Friday, Mar 4, 2016 10:15:12 AM EST
*To:* Tobias Schneider
*Cc:* dev-platform
*Subject:* Intent to ship: Support for color-adjust CSS property

> Whether or not we ship with the feature enabled, the ability to disable a
> feature with a pref gives us an easy out if a critical issue is discovered.
> (For ex, a code path that results in a top crash.) I suggest that we create
> the pref in either case and plan to remove it after a couple of releases if
> no critical bugs have come in.

--

Eric Shepherd
Senior Technical Writer
Mozilla Developer Network <https://developer.mozilla.org/>
Blog: https://www.bitstampede.com/
Twitter: http://twitter.com/sheppy
Doodle: http://doodle.com/the.sheppy

0 new messages