Skip to content

Require notes for partial_implementation #4162

@ddbeck

Description

@ddbeck

The partial_implementation data alone isn't very useful. We should consider requiring the notes property for any support statement that has partial_implementation: true. I started doing the schema work to do this, but it turned out there are more such cases than I would've guessed. At the moment, such support statements appear in the following features:

  • api.CSS.supports
  • api.Crypto.subtle
  • api.GeometryUtils
  • api.SubtleCrypto
  • api.VisualViewport.onresize
  • api.VisualViewport.onscroll
  • api.VisualViewport.resize_event
  • api.VisualViewport.scroll_event
  • api.WindowOrWorkerGlobalScope.indexedDB
  • css.properties.appearance
  • css.properties.appearance.compat
  • css.properties.filter
  • css.properties.font-feature-settings
  • css.properties.font-size.rem_values
  • css.properties.text-decoration.shorthand
  • html.elements.input.input-range
  • html.elements.script.integrity
  • html.elements.source.sizes
  • html.elements.source.srcset
  • webextensions.api.events.Event

Note: many of these features have more than support statement with a partial_implementation and no note.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNice to have features.schemaIsses or pull requests regarding the JSON schema files used in this project.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions