writing modes and widgets' operabilities & native appearances
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 4.9k
- Forks
- 816
- PR merge metrics
- PR metrics pending
Description
I think writing modes need to be taken into account for the appearance property and widget operabilities.
Question 1:
Should we make it clear that, when the native UI controls do not support vertical writing mode, UAs must implement the according operability themselves(For example, if the operating system doesn't support vertical textfield, UAs should implement <input type="text"> in vertical writing mode themselves)?
Question 2:
What if the native UI controls of the host operating system do not support vertical writing mode when appearance is auto?
Must UAs adjust UI controls to fit the writing mode while simulating native appearances as far as possible?
Or must UAs adjust UI controls as if appearance is none.
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 two questions about writing modes, native widget operability, and the appearance property. Determine the required behavior when native controls lack vertical writing-mode support, then document a resolved specification direction for both appearance: auto and simulated or non-native controls.
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
- 25/100