Closed Bug 1350383 Opened 7 years ago Closed 5 years ago

Update `justify-all` on "text-align" page

Categories

(Developer Documentation Graveyard :: CSS, enhancement)

All
Other
enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: chrisharvey2pi+mozilla, Assigned: me)

Details

(Whiteboard: [specification][type:bug])

What did you do?
================
1. Visit https://developer.mozilla.org/en-US/docs/Web/CSS/text-align

What happened?
==============
There is no indication of the `justify-all` value in the Formal Syntax, in any examples, on the Specifications table, or on the Browser Compatibility table.

The link to the Working Draft in the Specifications table incorrectly points to the Editor’s Draft.

What should have happened?
==========================
`justify-all` is introduced in the CSS Text Module Level 3 Editor’s Draft, but not in the Working Draft. Both of these should be indicated on the Specifications table. The link to the Working Draft should be corrected, and the Editor’s Draft should have its own row in the Specifications table, noting the addition of the `justify-all` keyword.

`justify-all` should also have its own row in the Browser Compatibility table, showing which browsers support the new value.



Is there anything else we should know?
======================================
CSS Text Module Level 3 Editor’s Draft - https://drafts.csswg.org/css-text-3/#text-align-property

CSS Text Module Level 3 Working Draft - https://www.w3.org/TR/css-text-3/#text-align
The format syntax, examples, and browser compatibility can be fixed by creating an MDN account and updating the page.  Updating the Specifications requires a PR updating the SpecName and Spec2 macros:

https://github.com/mozilla/kumascript/blob/master/macros/SpecName.ejs#L258
https://github.com/mozilla/kumascript/blob/master/macros/spec2.ejs#L74
Component: Wiki pages → CSS
Product: Mozilla Developer Network → Developer Documentation
Assignee: nobody → me
I believe all of these have now been added in the two years since this was reported (I just checked this page) so I think we can close this issue.
Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.