Closed Bug 1428255 Opened 7 years ago Closed 7 years ago

Small issue on MDN Web docs "Backgrounds" page - syntax differs from W3C

Categories

(Developer Documentation Graveyard :: CSS, defect, P1)

All
Other
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: russ, Unassigned)

References

()

Details

:: Developer Documentation Request Request Type: Correction Gecko Version: Trunk Technical Contact: :: Details The background page has syntax that differs slightly from the relevant W3C page. While the differences are minor, they could be confusing for some. -------------- MDN <bg-layer> syntax: -------------- <bg-layer> = <bg-image> || <position> [ / <bg-size> ]? || <repeat-style> || <attachment> || <box>{1,2} -------------- W3C <bg-layer> syntax: -------------- <bg-layer> = <bg-image> || <bg-position> [ / <bg-size> ]? || <repeat-style> || <attachment> || <box> || <box> Note that MDN uses "<box>{1,2}". While this suggests the same thing as the W3C, it does differ. -------------- MDN <final-layer> syntax: -------------- <final-bg-layer> = <bg-image> || <position> [ / <bg-size> ]? || <repeat-style> || <attachment> || <box> || <box> || <'background-color'> -------------- W3C <final-layer> syntax: -------------- <final-bg-layer> = <‘background-color’> || <bg-image> || <bg-position> [ / <bg-size> ]? || <repeat-style> || <attachment> || <box> || <box> Note that MDN places the <‘background-color’> value last, the W3C places it first. As above, this makes no difference to the outcome, as they can be written in any order, but could be confusing for new-comers.
Priority: P5 → P1
Thanks for filing! This content is actually pulled from https://github.com/mdn/data, so I filed an issue for this over there: https://github.com/mdn/data/issues/159.
Should be fixed now, thanks to @lahmatiy: please confirm and I will close this. https://developer.mozilla.org/en-US/docs/Web/CSS/background#Syntax
Flags: needinfo?(russ)
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Flags: needinfo?(russ)
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.