Summary: implement and ship value "break-spaces" of "white-space" CSS property
Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1351432
Link to standard:
https://drafts.csswg.org/css-text-3/#valdef-white-space-break-spaces
Platform coverage: all.
Estimated or target release: 69
Preference
On 6/11/19 7:49 AM, Kartikaya Gupta wrote:
IIRC another difference between prefs in all.js and gfxPrefs was that if a
pref was not listed in all.js, you couldn't use it in the
{test-,ref-,}pref(...) annotations in reftest.list files.
That restriction is due to the code at
Hi.
Thanks for the kind words.
> On 11 Jun 2019, at 9:49 pm, Kartikaya Gupta wrote:
>
> IIRC another difference between prefs in all.js and gfxPrefs was that if a
> pref was not listed in all.js, you couldn't use it in the
> {test-,ref-,}pref(...) annotations in reftest.list files. Can you
On Tue., Jun. 11, 2019, 04:01 Jean-Yves Avenard,
wrote:
>
> 1- If you define a StaticPref in StaticPrefList.h there is absolutely
> no-need to also defines the value in all.js. In fact this is strongly
> discouraged and there should almost never be a need for it. There will
> be no end-user
Hi there.
So the changes have been lived for a couple of weeks now and some issues
were raised or encountered since. So I would like to clarify some of those.
1- If you define a StaticPref in StaticPrefList.h there is absolutely
no-need to also defines the value in all.js. In fact this is
5 matches
Mail list logo
