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 _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
