[css-grid-3] Does reversing reverse placement only or also line/track ordering?
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 4.9k
- Forks
- 816
- PR merge metrics
- PR metrics pending
Description
From @celestepan's https://github.com/w3c/csswg-drafts/issues/12803#issuecomment-3387605000
In masonry, if we go with option 2, the behavior is exactly analogous:
row-reverseplaces items right-to-left instead of left-to-right across the columns, andwrap-reversestacks them up instead of down.Regardless of the naming, for implementations where we change the direction in which we're placing items across tracks (in columns, if we place items right-to-left, in rows, if we place items bottom-up), would we want to reverse the line names / line indices as well?
If we have 4 lines, would line 1 still be the left-most line, or would the right-most line become line 1?
When we talked about reversing originally, I don't think we explicitly considered this aspect of it when adding these values in #3622. What should happen? Do we have use cases to help us determine that?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the referenced comment in issue #12803 and the earlier discussion in #3622. Compare the proposed reversing behavior for placement with its effect on line names and indices, and look for use cases that resolve the question. Done means the CSS Grid 3 behavior is decided and clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css
- Domain
- web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100