Removal/Archiving of some box-X CSS properties?

[Julien Sphinx]

Hello all,

While going across the CSS Reference, I met the following properties:
- box-align
- box-direction
- box-flex-group
- box-lines
- box-ordinal-group
- box-orient

It seems to me that all those properties:
- exist in moz-prefixed version for use in XUL/internals
- have been migrated to Flexbox equivalents since

So I'm wondering what is the best solution here:
- move pages to "moz-box-..." pages
- archive them
- delete them
?

Thanks for your answers,
Respectfully,
Julien

[Sebastian Zartner]

Note that the browser compatibility is wrong for them. Chrome still
supports a -webkit-prefixed version of them.
Furthermore, while they may initially be designed for XUL content only in
Gecko, they also work in web content.

I've copied the example of the 'box-align' property to a JSFiddle:
https://jsfiddle.net/rdf2fas9/

So, I believe the best is to keep them as they are. The other possibility
would be to split them into pages with -webkit- and -moz- prefixes, but
because they basically work the same with both prefixes, it may not be
worth the effort.

Sebastian

> _______________________________________________
> dev-mdc mailing list
> dev...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-mdc
> MDN contributor guide: http://bit.ly/ContributorGuide
> Doc project Trello board: https://trello.com/b/HAhl54zz/status
>

[Eric Shepherd]

I think they should stay as they are -- except that the browser
compatibility sections should be updated to include not just
compatibility, but prefix information and details on differences in
implementations if needed.

------------------------------------------------------------------------
*From:* Sebastian Zartner
*Sent:* Monday, Apr 11, 2016 6:23:37 AM EDT
*To:* Julien Sphinx
*Cc:* dev...@lists.mozilla.org
*Subject:* [dev-mdc] Removal/Archiving of some box-X CSS properties?

> So, I believe the best is to keep them as they are. The other possibility
> would be to split them into pages with -webkit- and -moz- prefixes, but
> because they basically work the same with both prefixes, it may not be
> worth the effort.

--

Eric Shepherd
Senior Technical Writer
Mozilla Developer Network <https://developer.mozilla.org/>
Blog: https://www.bitstampede.com/
Twitter: http://twitter.com/sheppy
Doodle: http://doodle.com/the.sheppy

[Sebastian Zartner]

I've updated/added the browser compatibility sections including their
prefixes, renamed some related pages, added proper formal syntaxes, syntax
examples, info boxes and tags. From testing I didn't see much differences
in implementations.
Some compatibility data is still missing and half of the pages still need
examples. Feel free to add those.

Sebastian

On 11 April 2016 at 16:49, Eric Shepherd <eshe...@mozilla.com> wrote:

> I think they should stay as they are -- except that the browser
> compatibility sections should be updated to include not just compatibility,
> but prefix information and details on differences in implementations if
> needed.
>
> ------------------------------

[Sphinx]

Thanks for the feedback and most importantly, thanks for the action
Sebastian :)
I consider the thread closed for now!

Respectfully,
Julien