issue:
  - shown:
      - true
      - true
      - true
    id: '1'
    summary: Mixed content warning for HTTP w3c_home image
    openness: closed
    status: accepted
    from: SimonSapin
    comment:
      - 'https://github.com/w3c/csswg-drafts/issues/90'
    response: []
    resolved: editorial
    tag: []
    notes: Caused by bug in old CSS preprocessor
    authorResponse: 'https://github.com/w3c/csswg-drafts/issues/90#issuecomment-172771890'
  - shown:
      - true
      - true
      - true
    id: '2'
    summary: Link syntaxes with CSS Values
    openness: closed
    status: invalid
    from: ' SebastianZ '
    comment:
      - 'https://github.com/w3c/csswg-drafts/issues/143'
    response:
      - >-
        Auto linking between CSS specs is a Bikeshed feature; CSS Fonts 3 is an
        old spec and doesn't use Bikeshed.
    resolved: editorial
    notes: Caused by bug in old CSS preprocessor
    tag: []
  - shown:
      - true
      - true
      - true
    id: '3'
    summary: Finish up Bikeshed source
    openness: closed
    status: deferred
    from: SebastianZ
    comment:
      - 'https://github.com/w3c/csswg-drafts/issues/234'
    response:
      - CSS Fonts 4 uses Bikeshed
    resolved: editorial
    tag: []
  - shown:
      - true
      - true
      - true
    id: '4'
    summary: Feature resolution and caps synthesis conflicting
    openness: closed
    status: accepted
    from: tabatkins
    comment:
      - 'https://github.com/w3c/csswg-drafts/issues/259'
    response: []
    resolved: bugfix
    tag: []
  - shown:
      - true
      - true
      - true
    id: '5'
    summary: Consider marking @font-feature-values at risk
    openness: closed
    status: accepted
    from: litherum
    comment:
      - 'https://github.com/w3c/csswg-drafts/issues/577'
    response: []
    resolved: resolution
    notes: Marked at-risk
    tag: []
  - shown:
      - true
      - true
      - true
    id: '6'
    summary: >-
      Change @font-face and @font-feature-values syntax definitions to use CSS
      syntax and link to those definitions
    openness: closed
    status: deferred
    from: SebastianZ
    comment:
      - 'https://github.com/w3c/csswg-drafts/issues/624'
    response: []
    resolved: editorial
    notes: Fixed by CSS Fonts 4 using Bikeshed
    tag: []
  - shown:
      - true
      - true
      - true
    id: '7'
    summary: '[css-fonts] hasn’t been updated in a long time'
    openness: closed
    status: accepted
    from: simevidas
    comment:
      - 'https://github.com/w3c/csswg-drafts/issues/788'
    response: []
    resolved: editorial
    notes: Bug in old CSS preprocessor. Updated CR in Feb 2018
    tag: []
  - shown:
      - true
      - true
      - true
    id: '8'
    summary: >-
      explicitly specify that font-size-adjust should be either none or a
      non-negative number
    openness: closed
    status: invalid
    from: chenpighead
    comment:
      - 'https://github.com/w3c/csswg-drafts/issues/702'
    response: []
    authorResponse: 'https://github.com/w3c/csswg-drafts/issues/702'
    resolved: editorial
    notes: Spec already says negative values are invalid.
    tag: []
  - shown:
      - true
      - true
      - true
    id: '9'
    summary: '@font-face doesn''t accept individual font-variant-* descriptors'
    openness: closed
    status: deferred
    from: litherum
    comment:
      - 'https://github.com/w3c/csswg-drafts/issues/790'
    response:
      - '(no discussion, no response)'
    tag: []
    authorResponse: 'https://github.com/w3c/csswg-drafts/issues/790#issuecomment-349521070'
    resolved: nochange
    notes: Deferred to Fonts 4
  - shown:
      - true
      - true
      - true
    id: '10'
    summary: CSSFontFaceRule does not seem Web compatible
    openness: closed
    status: accepted
    from: svgeesus
    comment:
      - 'https://github.com/w3c/csswg-drafts/issues/825'
    response:
      - 'https://github.com/w3c/csswg-drafts/issues/825#issuecomment-295143110'
    authorResponse: 'https://github.com/w3c/csswg-drafts/issues/825#issuecomment-317616156'
    resolved: resolution
    resolution: >-
      RESOLVED: rollback to previous state with CSSStyleDeclaration and umerged
      interfaces
    tag: []
  - shown:
      - true
      - true
      - true
    id: '11'
    summary: All CSS-wide keywords should be excluded from <family-name> type
    openness: closed
    status: accepted
    from: upsuper
    comment:
      - 'https://github.com/w3c/csswg-drafts/issues/946'
    response: []
    resolved: bugfix
    tag: []
  - shown:
      - true
      - true
      - true
    id: '12'
    summary: Grammar of <feature-value-name>
    openness: closed
    status: accepted
    from: SimonSapin
    comment:
      - 'https://github.com/w3c/csswg-drafts/issues/1000'
    response:
      - 'https://github.com/w3c/csswg-drafts/issues/1000#issuecomment-356680248'
    tag: []
    authorResponse: 'https://github.com/w3c/csswg-drafts/issues/1000#issuecomment-356685004'
    resolved: editorial
    notes: Grammar now links to the correct definitions
  - shown:
      - true
      - true
      - true
    id: '13'
    summary: Should font-synthesis be reset by font shorthand?
    openness: closed
    status: accepted
    from: upsuper
    comment:
      - 'https://github.com/w3c/csswg-drafts/issues/1032'
    response: []
    tag: []
    authorResponse: 'https://github.com/w3c/csswg-drafts/issues/1032#issuecomment-360682467'
    resolved: bugfix
    notes: >-
      Note added to clarify that font-synthesis is not reset by the font
      shorthand.
  - shown:
      - true
      - true
      - true
    id: '14'
    summary: should there be more options to font-synthesis?
    openness: closed
    status: deferred
    from: frivoal
    comment:
      - 'https://github.com/w3c/csswg-drafts/issues/1034'
    response: []
    notes: Small caps synthesis is already added in css fonts 4.
    tag: []
  - shown:
      - true
      - true
      - true
    id: '15'
    summary: Spec uses phrase "system fonts" when it means "installed fonts"
    openness: closed
    status: accepted
    from: litherum
    comment:
      - 'https://github.com/w3c/csswg-drafts/issues/1052'
    response: []
    resolved: editorial
    tag: []
  - shown:
      - true
      - true
      - true
    id: '16'
    summary: >-
      Clarify what value is invalid for font-language-override and why it
      shouldn't generate parse error
    openness: closed
    status: deferred
    from: upsuper
    comment:
      - 'https://github.com/w3c/csswg-drafts/issues/1104'
    response:
      - 'https://github.com/w3c/csswg-drafts/issues/1104#issuecomment-356679391'
    notes: Deferred to css fonts 4.
    tag: []
    resolved: nochange
  - shown:
      - true
      - true
      - true
    id: '17'
    summary: Is the exclusion of calc() from @font-feature-values intentional?
    openness: closed
    status: accepted
    from: MatsPalmgren
    comment:
      - 'https://github.com/w3c/csswg-drafts/issues/1127'
    response: []
    resolved: editorial
    tag: []
  - shown:
      - true
      - true
      - true
    id: '18'
    summary: Handling of @font-face rule which lacks font-family or src descriptor
    openness: closed
    status: accepted
    from: upsuper
    comment:
      - 'https://github.com/w3c/csswg-drafts/issues/1133'
    response: []
    resolved: resolution
    resolution: >-
      RESOLVED: font face rules should be in the om, but should not be used for
      font matching 
    tag: []
  - shown:
      - true
      - true
      - true
    id: '19'
    summary: Add font-language-override descriptor
    openness: closed
    status: invalid
    from: dbaron
    comment: []
    response: []
    notes: 'Duplicate of [#1392](https://github.com/w3c/csswg-drafts/issues/1392)'
    tag: []
  - shown:
      - true
      - true
      - true
    id: '20'
    summary: Default feature list should not require a list of features to turn on
    openness: closed
    status: retracted
    from: litherum
    comment:
      - 'https://github.com/w3c/csswg-drafts/issues/1267'
    response:
      - 'https://github.com/w3c/csswg-drafts/issues/1267#issuecomment-356678934'
      - 'https://github.com/w3c/csswg-drafts/issues/1267#issuecomment-358384846'
      - 'https://github.com/w3c/csswg-drafts/issues/1267#issuecomment-360208046'
    tag: []
    authorResponse: retracted
    resolved: nochange
    notes: >-
      We have interop with Gecko and Chrome on the default values; Safari is
      nearly conforming except for two bugs. No spec change.
  - shown:
      - true
      - true
      - true
    id: '21'
    summary: font-feature-settings property should be reset by font shorthand
    openness: closed
    status: deferred
    from: upsuper
    comment:
      - 'https://github.com/w3c/csswg-drafts/issues/1349'
    response: []
    notes: >-
      Duplicate of [#1636](https://github.com/w3c/csswg-drafts/issues/1636) on
      css-fonts-4
    tag: []
  - shown:
      - true
      - true
      - true
    id: '22'
    summary: >-
      Should the OpenType spec dictate the acceptable values for variable font
      CSS properties?
    openness: closed
    status: rejected
    from: drott
    comment:
      - 'https://github.com/w3c/csswg-drafts/issues/1531'
    response:
      - 'https://github.com/w3c/csswg-drafts/issues/1531#issuecomment-358384560'
    tag: []
    resolved: nochange
    authorResponse: 'https://github.com/w3c/csswg-drafts/issues/1531#issuecomment-362272221'
  - shown:
      - true
      - true
      - true
    id: '23'
    summary: Serialization of font properties when system font is specified
    openness: closed
    status: deferred
    from: upsuper
    comment:
      - 'https://github.com/w3c/csswg-drafts/issues/1586'
    response:
      - 'https://github.com/w3c/csswg-drafts/issues/1586#issuecomment-356678007'
    tag: []
    resolved: resolution
    resolution: serialization when system fonts are used to font properties to L4 of Fonts
    authorResponse: 'https://github.com/w3c/csswg-drafts/issues/1586#issuecomment-360682547'
  - shown:
      - true
      - true
      - true
    id: '24'
    summary: Font matching algorithm; issue with weight selection
    openness: closed
    status: rejected
    from: neilj
    comment:
      - 'https://github.com/w3c/csswg-drafts/issues/1701'
    response:
      - >-
        we'd love to improve this but we feel constrained about compatibility.
        Please reopen this if you can find a way around the compatibility issue
    tag: []
    resolved: nochange
  - shown:
      - true
      - true
      - true
    id: '25'
    summary: Make larger/smaller simple ratios
    openness: closed
    status: accepted
    from: ' Manishearth '
    comment:
      - 'https://github.com/w3c/csswg-drafts/issues/1711'
    response:
      - 'https://github.com/w3c/csswg-drafts/issues/1711#issuecomment-356676602'
    tag: []
    resolved: resolution
    resolution: >-
      add 1.2-1.5 as the conventional ratio range for the relative sizes when
      they're not modifying an absolute keyword size
  - shown:
      - true
      - true
      - true
    id: '26'
    summary: The CSSFontFeatureValuesRule interface has only one implementation
    openness: closed
    status: deferred
    from: svgeesus
    comment:
      - 'https://github.com/w3c/csswg-drafts/issues/1713'
    response:
      - 'https://github.com/w3c/csswg-drafts/issues/1713#issuecomment-322826118'
    authorResponse: 'https://github.com/w3c/csswg-drafts/issues/1713#issuecomment-349510893'
    resolved: resolution
    resolution: 'RESOLVED: Move CSSFontFeatureValuesRule to L4 Fonts'
    tag: []
  - shown:
      - true
      - true
      - true
    id: '27'
    summary: the font-language-override property has only one implementation
    openness: closed
    status: deferred
    from: svgeesus
    comment:
      - 'https://github.com/w3c/csswg-drafts/issues/1714'
    response: []
    authorResponse: 'https://github.com/w3c/csswg-drafts/issues/1714#issuecomment-349511623'
    resolved: resolution
    resolution: 'RESOLVED: Move the font-language-override property to fonts L4'
    tag: []
  - shown:
      - true
      - true
      - true
    id: '28'
    summary: 6.1. Glyph selection and positioning should be marked as informative
    openness: closed
    status: accepted
    from: svgeesus
    comment:
      - 'https://github.com/w3c/csswg-drafts/issues/1728'
    response: []
    authorResponse: 'https://github.com/w3c/csswg-drafts/issues/1728#issuecomment-349512065'
    resolved: bugfix
    tag: []
  - shown:
      - true
      - true
      - true
    id: '29'
    summary: Do generic fonts resolve to a single font face value?
    openness: closed
    status: accepted
    from: gsnedders
    comment:
      - 'https://github.com/w3c/csswg-drafts/issues/1736'
    response:
      - 'https://github.com/w3c/csswg-drafts/issues/1736#issuecomment-356672760'
    tag: []
    resolved: resolution
    resolution: >-
      Take Chris's language in https://github.com/w3c/csswg-drafts/issues/1736
      into the spec as an example
  - shown:
      - true
      - true
      - true
    id: '30'
    summary: '@font-face unicode-range and first available font'
    openness: closed
    status: accepted
    from: 'SergeyMalkin '
    comment:
      - 'https://github.com/w3c/csswg-drafts/issues/1765'
    response: []
    resolved: resolution
    resolution: >-
      RESOLVED: Change spec text to read first available font that would match
      the U+0020 (space) character
    tag: []
  - shown:
      - true
      - true
      - true
    id: '31'
    summary: 'Animation on the condensed-expanded axis '
    openness: closed
    status: rejected
    from: svgeesus
    comment:
      - 'https://github.com/w3c/csswg-drafts/issues/1811'
    response: []
    authorResponse: 'https://github.com/w3c/csswg-drafts/issues/1811#issuecomment-329190345'
    resolved: resolution
    resolution: 'Already resolved in fonts 4, won''t fix in fonts 3'
    tag: []
  - shown:
      - true
      - true
      - true
    id: '32'
    summary: Handle language/family dependent cascading of keyword font-size values
    openness: closed
    status: deferred
    from: 'Manishearth '
    comment:
      - 'https://github.com/w3c/csswg-drafts/issues/1835'
    response: []
    tag: []
  - shown:
      - true
      - true
      - true
    id: '33'
    summary: Change default <sup> and <sub> styling?
    openness: closed
    status: rejected
    from: domenic
    comment:
      - 'https://github.com/w3c/csswg-drafts/issues/1888'
    response:
      - 'https://github.com/w3c/csswg-drafts/issues/1888#issuecomment-339391611'
      - 'https://github.com/w3c/csswg-drafts/issues/1888#issuecomment-337711657'
    tag: []
    resolved: nochange
    notes: >-
      Requested change not possible due to web compatibility with nested sup and
      sub
  - shown:
      - true
      - true
      - true
    id: '34'
    summary: >-
      font-variation-settings and font-feature-settings what should be returned
      for getComputedValue
    openness: closed
    status: accepted
    from: 'gregwhitworth '
    comment: []
    response: []
    authorResponse: 'https://github.com/w3c/csswg-drafts/issues/1959#issuecomment-342685617'
    resolved: resolution
    resolution: >-
      RESOLVED: For both font-variation-settings and font-feature-settings, the
      computed value is a map (and thus specified dupes are removed)
    tag: []
  - shown:
      - true
      - true
      - true
    id: '35'
    summary: '[css-fonts-3] use class=advisement for font-feature-settings'
    openness: closed
    status: accepted
    from: fantasai
    comment:
      - 'https://github.com/w3c/csswg-drafts/issues/2235'
    response: []
    resolved: editorial
    tag: []
  - shown:
      - true
      - true
      - true
    id: '36'
    summary: '[css-fonts-3] @font-face font-variant cannot easily be reverted to default'
    openness: closed
    status: deferred
    from: faceless2
    comment:
      - 'https://github.com/w3c/csswg-drafts/issues/2265'
    response: []
    tag: []
    authorResponse: 'https://github.com/w3c/csswg-drafts/issues/2265#issuecomment-372403769'
    notes: Deferred to level 4
  - shown:
      - true
      - true
      - true
    id: '37'
    summary: Cross-link to CSS Text order of operations
    openness: closed
    status: accepted
    from: fantasai
    comment:
      - 'https://github.com/w3c/csswg-drafts/issues/2393'
    response: []
    resolved: editorial
    tag: []
title: CSS Fonts 3