Should coordinates for actions should support floats and not integer?
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 718
- Forks
- 228
- PR merge metrics
- No merged PRs in 30d
Description
Right now coordinates for eg. pointer actions require integer values:
Let x be the result of getting the property x from action item.
If x is not an Integer, return error with error code invalid argument.
The question is if we still need this restriction or if it is unnecessary / unhelpful these days. Most users have a high DPI display where we can have multiple physical pixels per CSS pixel. In such a case we should probably really allow floats?
CC'ing @jgraham given his feedback from https://bugzilla.mozilla.org/show_bug.cgi?id=1793835#c2.
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 the WebDriver specification text for action-item coordinates, including the linked definitions of getting properties, Integer, and invalid argument. Review the related Mozilla Bugzilla discussion for the existing feedback. Done means reaching and documenting a decision on whether the coordinate restriction should change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100