Intent to Prototype: Aliasing -webkit-font-feature-settings to font-feature-settings for webcompat

2020-09-11 Thread Jens Hausdorf

Hi everyone!

Summary: Aliasing the proprietary css property 
-webkit-font-feature-settings to font-feature-settings so Gecko picks up 
more CSS stylesheets, eventually producing the same behavior as with 
Webkit for website that don't update their css to include the 
standardized version of font-feature-settings.


Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1595620

Standard: n/a, font-feature-settings was standardized in 
https://drafts.csswg.org/css-fonts-3/#propdef-font-feature-settings


Platform coverage: All

Preference: layout.css.prefixes.font-features

DevTools bug: n/a

Other browsers: n/a

web-platform-tests: don't seem necessary in this case as 
-webkit-font-feature-settings should not be used anymore as the spec is 
finalized.


Cheers,
Jens
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Re: Intent to Prototype: Aliasing -webkit-font-feature-settings to font-feature-settings for webcompat

2020-09-04 Thread Mike Taylor

Hi Jens,

On 8/31/20 10:02 AM, Jens Hausdorf wrote:

Hi everyone!

Summary: Aliasing the proprietary css property 
-webkit-font-feature-settings to font-feature-settings so Gecko picks up 
more CSS stylesheets, eventually producing the same behavior as with 
Webkit for website that don't update their css to include the 
standardized version of font-feature-settings.


Thank you for working on this!

--
Mike Taylor
Web Compat, Mozilla
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform