[css-device-adapt] Clarify setting "user-scalable=no" clamps min/max values
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 4.9k
- Forks
- 816
- PR merge metrics
- PR metrics pending
Description
We have a bug report that the site in question is rendered properly on Chrome but not on Firefox.
I noticed the difference between Chrome and Firefox is that Chrome clamps min/max scale values to the auto calculate initial scale value if "user-scalable=no" is specified. That makes sense to me. So we are going to change our behavior to match Chrome's behavior. The spec should mention it clearly somewhere.
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 linked Bugzilla report and locate the current specification text for the user-scalable setting and min/max scale values. Clarify whether user-scalable=no clamps those values to the automatically calculated initial scale, and consider the work done when the specification states the intended behavior unambiguously.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css
- Domain
- documentation, web-dev
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100