New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

font-variant-numeric #2116

Open
ierhyna opened this Issue Nov 28, 2015 · 10 comments

Comments

Projects
None yet
9 participants
@ierhyna

ierhyna commented Nov 28, 2015

There is no information about font-variant-numeric feature support.
(MDN: https://developer.mozilla.org/en/docs/Web/CSS/font-variant-numeric)
Thanks!

@Ugoku

This comment has been minimized.

Show comment
Hide comment
@Ugoku

Ugoku Dec 1, 2015

Contributor

+1

Contributor

Ugoku commented Dec 1, 2015

+1

@kiding

This comment has been minimized.

Show comment
Hide comment
@kiding

kiding Mar 31, 2016

Contributor

Not only font-variant-numeric, but also many properties defined by CSS Fonts Module Level 3 are missing, which include;

  • font-variant-ligatures
  • font-variant-position*****
  • font-variant-caps
  • font-variant-numeric
  • font-variant-east-asian
  • font-variant (shorthand)
  • font-language-override*****

***** Features at risk, may be removed in the future.

Some are only supported by Firefox, and Safari started to support them recently. I'd like to suggest we change the issue to conform with all the CSS Fonts properties.

Contributor

kiding commented Mar 31, 2016

Not only font-variant-numeric, but also many properties defined by CSS Fonts Module Level 3 are missing, which include;

  • font-variant-ligatures
  • font-variant-position*****
  • font-variant-caps
  • font-variant-numeric
  • font-variant-east-asian
  • font-variant (shorthand)
  • font-language-override*****

***** Features at risk, may be removed in the future.

Some are only supported by Firefox, and Safari started to support them recently. I'd like to suggest we change the issue to conform with all the CSS Fonts properties.

@drott

This comment has been minimized.

Show comment
Hide comment
@drott

drott May 23, 2016

Contributor

+1

Contributor

drott commented May 23, 2016

+1

@drott

This comment has been minimized.

Show comment
Hide comment
@drott

drott May 23, 2016

Contributor

I implemented font-variant-numeric and font-variant-caps in Chrome 52, compare https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/p9k6H2tUADk

Contributor

drott commented May 23, 2016

I implemented font-variant-numeric and font-variant-caps in Chrome 52, compare https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/p9k6H2tUADk

@kiding

This comment has been minimized.

Show comment
Hide comment
@kiding

kiding May 23, 2016

Contributor

@drott Very cool!

Contributor

kiding commented May 23, 2016

@drott Very cool!

@maddesigns

This comment has been minimized.

Show comment
Hide comment

+1

@Megabyte-16

This comment has been minimized.

Show comment
Hide comment

+1

@garrik

This comment has been minimized.

Show comment
Hide comment

garrik commented Nov 1, 2017

+1

@chharvey

This comment has been minimized.

Show comment
Hide comment
@chharvey

chharvey Nov 2, 2017

#1550 seems to have already proposed this, but I like that @kiding has enumerated out the sub-properties for all to see. @kiding, can you cite any sources on the "features at risk," i.e., where are you getting that information?

chharvey commented Nov 2, 2017

#1550 seems to have already proposed this, but I like that @kiding has enumerated out the sub-properties for all to see. @kiding, can you cite any sources on the "features at risk," i.e., where are you getting that information?

@kiding

This comment has been minimized.

Show comment
Hide comment
@kiding

kiding Nov 2, 2017

Contributor

@chharvey The W3C CSS standard has "Features at risk" section near the top of the document, right below the status section.

Contributor

kiding commented Nov 2, 2017

@chharvey The W3C CSS standard has "Features at risk" section near the top of the document, right below the status section.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment