-
Notifications
You must be signed in to change notification settings - Fork 2k
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.
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
Separating Grid and Flex support for align-items #2156
Conversation
css/properties/align-items.json
Outdated
}, | ||
"first_last_baseline": { | ||
"flex_context": { | ||
"description": "Supported in Flex Layout", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be a sub-item of __compat
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure I understand this comment - I was going on a suggestion by @wbamberg which had this outside __compat, so perhaps he could comment to clarify.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's my mistake: yes, description
should be inside __compat
:).
css/properties/align-items.json
Outdated
"chrome": [ | ||
{ | ||
"version_added": "57" | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Arrays are only permitted in support blocks when they have more than 1 entry.
css/properties/align-items.json
Outdated
"chrome_android": [ | ||
{ | ||
"version_added": "52" | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
css/properties/align-items.json
Outdated
"edge": [ | ||
{ | ||
"version_added": "16" | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
css/properties/align-items.json
Outdated
"edge_mobile": [ | ||
{ | ||
"version_added": true | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
css/properties/align-items.json
Outdated
"firefox": [ | ||
{ | ||
"version_added": "52" | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
css/properties/align-items.json
Outdated
"firefox_android": [ | ||
{ | ||
"version_added": "52" | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
css/properties/align-items.json
Outdated
"version_added": null | ||
}, | ||
"version_added": "52" | ||
}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wrong indentation
Thanks for this, @rachelandrew . It helps a lot to have something concrete to look at. With this data I think it would be best to include 2 tables in the page, with calls like:
That would give us a table looking like this: I think this looks pretty clear. Note that this means the If we tried to include both in the same table I think it would get confusing when sub-sub-features like " I can't think of any compelling reason not to use this as a model for the Grid/Flex/Multicol properties. I'm not sure if it will work very well when and if we want to support "aggregate" tables, like a table of all the Grid properties. But I don't think that should stop us moving forward with this. I'd like to hear if @Elchi3 also thinks this is a good approach though, as it is a bit unusual. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like npm-debug.log was included in this PR by accident.
Other than this I think this approach looks great. I'd also like to hear Florian's take though.
"description": "<code>first baseline</code> and <code>last baseline</code>", | ||
"support": { | ||
"webview_android": { | ||
"version_added": null |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would be really nice to change some of these null
values to Yes/No even if the version number is not known.
I like the idea to have the separate tables. That looks nice and clear. |
@rachelandrew @wbamberg We should probably also do the same table separation for |
@ExE-Boss yes that's the intention (I'm currently working on restructuring the Box Alignment documentation). |
I also like the idea of separate tables. Great idea, @wbamberg 👍
Not sure about this yet either, but "aggregate" tables are a whole separate thing we'll have to look at on a future day. I agree to not worry about it for now. |
So, this PR looks good to me, but unsure about whether there is more to come per the first comment
If not, I'm happy to merge this and get it in today's release. |
This one stands alone, so lets publish this one and I'll work on the others doing an individual PR for each property if that makes sense? It will end up being a lot of files in one PR otherwise. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That makes sense to me and is easier to review :) Thanks a lot @rachelandrew 👍
I'm merging this now and it will get published later this evening to MDN prod.
* Separating Grid and Flex support for align-items * fixes to align-items as requested * moving description as requested * fixing indentation * removing debug log
Further to emails with @chrisdavidmills and @wbamberg an attempt at adding a separate section for grid and flex layout support info.
I am sure this will need all kinds of changes but if we can get this one figured out then I can go through all the rest.