[resize-observer] Shouldn't ResizeObserverEntry contain writing-mode values?
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 4.9k
- Forks
- 816
- PR merge metrics
- PR metrics pending
Description
Otherwise we must call getComputedStyle on the observed element to get the value. There's otherwise no way to get the writing-mode as far as I know.
The callback's handling code may needs to know whether to use inlineSize as width or as height (and similar with blockSize).
This issue could be avoided if there were verticalSize and horizontalSize values instead of inlineSize and blockSize, so that the vertical and horizontal sizing could be reliable without needing to look for the writing-mode value.
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 reviewing the ResizeObserverEntry and writing-mode concepts described in the issue. Determine whether exposing writing-mode values or changing the size properties is the appropriate specification change, then document the agreed behavior in the relevant CSSWG draft definitions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100