Closed Bug 1180573 Opened 8 years ago Closed 6 years ago

Standardized flag is wrong

Categories

(developer.mozilla.org Graveyard :: BrowserCompat, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: fs, Unassigned)

References

Details

(Whiteboard: [bc:infra][bc:milestone=scooter])

What did you do?
================
1. Fix parsing issues on https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Functions/arguments/caller
2. Provided {{WhyNoSpecStart}}, to fix parsing and to indicate no spec (=non-standard feature)

What happened?
==============
https://browsercompat.herokuapp.com/importer/4728

Correctly parsed with no errors.
Correctly displays no specification entries.
Wrongly sets "standardized": true in "Raw Data"

What should have happened?
==========================
"standardized" should be "false", as no spec is present and WhyNoSpec is provided, too.

Is there anything else we should know?
======================================
Blocks: 1132269
I've asked :sheppy on bug 1170206 if he agrees that's how {{WhyNoSpecStart}} should act.  For now, it just signals that the parser shouldn't report an issue about the extra text in the spec section.

The current way to clear the standardized flag is to add one of these in the feature name cell:

{{non-standard_inline}} - https://developer.mozilla.org/en-US/docs/Web/API/AnimationEvent
{{not_standard_inline}} - https://developer.mozilla.org/en-US/docs/Web/CSS/text-align

Those pages are where I first found that KumaScript - it may have changed since then.
{{WhyNoSpecStart}} is a no-op. It (as does {{WhyNoSpecEnd}}) does absolutely nothing. It's there only to allow the parser to detect this scenario, where there's material other than a specification table in that position.
I don't think {{non-standard-inline}} in a cell is enough to clear the standardized flag.

This page is typical for a non-standard JS feature:
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/toSource

1) {{WhyNoSpec}} is present
2) {{non-standard_header}} is present
3) "Non-standard" tag is present

Either of these should clear the flag, imo.
Blocks: 1181140
No longer blocks: 1132269
Summary: [CompatData][Importer] Standardized flag is wrong → [Compat Data][Importer] Standardized flag is wrong
While {{WhyNoSpec}} for recognition of non-standard features may not be adequate, {{non-standard_header}} should be enough, though, to set 'standardized' for the whole feature to 'false'.

Sebastian
Component: General → BrowserCompat
Keywords: in-triage
OS: Other → All
Summary: [Compat Data][Importer] Standardized flag is wrong → Standardized flag is wrong
Whiteboard: [specification][type:bug] → [bc:infra]
Mentor: jwhitlock
Whiteboard: [bc:infra] → [bc:infra][bc:milestone=scooter]
Mentor: jwhitlock
The BrowserCompat project is canceled.  See https://github.com/mdn/browsercompat for current effort. Bulk status change includes the random word TEMPOTHRONE.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.