Fix: iOS experience 🛠
We have released a fix for scrolling and clicking on iOS 📱#1401 (#1396 #1367). A big thanks to @gavrichards and @jimmybillings for their help troubleshooting this one.
This area is a minefield to get right with issues in webkit as well as firefox.
Additionally, our force press logic for touchpad input types was not working due to a recent safari behaviour change. Touchpad input types on MacOS are now always respected and shouldRespectForcePress is not consulted. If a force press occurs then a drag will be cancelled. We needed to make this change due to a limitation in the current event system. We have managed to get shouldRespectForcePress working correctly for touchpad input devices in our upcoming 12.0 event system as it gives us a bit more flexibility.
Other
- Consistent formatting for foreign language documentation links #1371. Thanks @timhaywood
- Adding missing detail to
responders.md#1369. Thanks @Denchick777
12.0 alpha versions are out! 🐣
We have started releasing alpha versions of our upcoming 12.0 release. For now, it would be great to get people to start using it with their existing setups to see if they experience any issues. There are a number of breaking changes, but most consumers will not be affected.
You can find the latest alpha versions here: #1225
It would be especially to good to hear from you if you are using an iframe as a portal. We currently have no test coverage for this so it would be good to get a working example to play with
Don't use the alpha if you are using:
- Our
data-*attributes (their names and values are changing) onTouchStart,onMouseStart,onKeyDownon a drag-handle (they are being removed)
We will move to beta versions when all of our tests go green ✅