[css-flex] Add APIs for discovering flex information not exposed by properties
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 4.9k
- Forks
- 816
- PR merge metrics
- PR metrics pending
Description
This is the same issue than #4511 but for flexbox instead of grid layout.
Despite flexbox is simpler than grid, it might be needed some internal information to be able to develop some stuff like dev tools, or a flex highlighter in an editor, or things like that. Those tools could probably back compute that information, but that's information already known by the engine so maybe it could be a good idea to expose it.
I guess @captainbrosset can provide examples of the kind of things that would be needed here, as he's working on flexbox tooling for Chromium DevTools.
JFYI, in this case Firefox doesn't have an internal API, like for grid.
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 by reading issue #4511 and compare its grid-layout discussion with the flexbox tooling needs described here. Seek concrete examples from Chromium DevTools work, then define which flex information should be exposed and how the CSS Working Group should specify it; the issue is complete when those requirements are agreed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100