Skip to content

Drop new notices on partial and behavioral guidelines #29703

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.

Sign up for GitHub

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

Merged
caugner merged 1 commit into from
May 22, 2026
Merged

Drop new notices on partial and behavioral guidelines #29703

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 2 additions & 11 deletions docs/data-guidelines/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -58,10 +58,6 @@ This guideline was adopted to protect the quality of stable data in the face of

## `"partial_implementation"` general usage guidelines

> [!NOTE]
> This guideline was added in August 2025 and feedback is welcome.
> If you have questions or concerns about how to apply it, [file an issue](https://github.com/mdn/browser-compat-data/issues/new/choose).

The partial implementation flag often requires a judgment call.
If you're not completely certain, ask for a second opinion.

Expand Down Expand Up @@ -95,8 +91,7 @@ Here are some example situations where this guideline may or may not apply:

- `"partial_implementation": false`: All implementing browsers provide a form control user interface, but the specification gives the implementer discretion over its look and feel.
A developer complains that one browser's user interface lacks some desired quality that other browsers implement; they want it to be marked as partially implemented.
Use a note or non-standard behavioral subfeature instead.
<!-- TODO: link to behavioral subfeature guidelines, when available -->
Use a note or non-standard [behavioral subfeature](#behavioral-subfeatures) instead.

- `"partial_implementation": false`: An implementing browser fails a web platform test against a corner case.
No web developers have reported the bug and it's unlikely that there are real-world applications that would attempt to use the corner case.
Expand Down Expand Up @@ -220,10 +215,6 @@ This guideline was proposed in [#15703](https://github.com/mdn/browser-compat-da

## Behavioral subfeatures

> [!NOTE]
> This guideline was added in August 2025 and feedback is welcome.
> If you have questions or concerns about how to apply it, [file an issue](https://github.com/mdn/browser-compat-data/issues/new/choose).

A behavioral subfeature records support for some facet, nuance, or evolution of a parent feature, where the behavior doesn't have a natural identifier (like CSS properties, API methods, or HTTP headers do).
Due to the lack of a natural identifier, a behavioral subfeature must have a `description`.

Expand All @@ -235,7 +226,7 @@ If a more specific guideline applies, follow that guideline instead of this one.

Behavioral subfeatures are rare.
Do not create a subfeature when the behavioral subfeature's `support` data would be the same, across all browsers, as the parent feature.
For serious bugs affecting a single engine, consider using `partial_implementation` instead. <!-- TODO: link to partial_implementation guidelines, when available -->
For serious bugs affecting a single engine, consider [using `partial_implementation`](#partial_implementation-general-usage-guidelines) instead.

You may create a behavioral subfeature for the following types of browser behaviors:

Expand Down