[Rating] Precision doesn't work on android chrome
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 99.1k
- Forks
- 32.5k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 106
Description
Duplicates
- I have searched the existing issues
Latest version
- I have tested the latest version
Steps to reproduce 🕹
Link to live example: https://mui.com/material-ui/react-rating/
Steps:
- Open example at android cellphone using chrome or if you are using PC, open chrome and change device mode using dev tool.
- Try to select 0.5, 1.5, 2.5 and so on at Rating precision section.
Current behavior 😯
I set precision 0.5 at Rating component and expected to select 0.5, 1.5, 2.5 and so on, but when I touch, 1 selected instead of 0.5, 2 instead of 1.5, 3 instead of 2.5 and so on only in android chrome. It works well on iphone chrome and safari.
Expected behavior 🤔
If I set precision 0.5 at Rating component, 0.5, 1.5, 2.5 and so on should be selected on android chrome as well.
Context 🔦
I made rating component for user review using custom icon with precision 0.5, but it doesn't work on only android chrome. I tried issue #32557 solution which change pointer-events as auto on MuiSvgIcon-root, but it still doesn't work on only android chrome.
Your environment 🌎
npx @mui/envinfo
Don't forget to mention which browser you used.
Output from `npx @mui/envinfo` goes here.
Google Chrome: 110.0.5481.177(Official Build) (x86_64)
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 live Rating example at https://mui.com/material-ui/react-rating/ and reproduce half-step selection on Android Chrome using precision 0.5. Compare the behavior with the linked issue #32557 solution and verify that 0.5, 1.5, and 2.5 can be selected on Android Chrome without breaking the reported working browsers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100