A bug has been reported where text selection and quoting don’t work after using the composer on iOS 12 devices ljpp. The issue can be reproduced by editing a post, saving, and then trying to quote text with a long press.
@pmusaraj was able to reproduce the issue and investigated further, but was unable to find a solution. It appears to be a general iOS 12 bug, not specific to Discourse, as the same issue can be reproduced on other websites pmusaraj.
@joffreyjaffeux noted that iOS 12 has improvements on text selection, which could be contributing to the bug. The issue was not reproducible on iOS 11 pmusaraj.
@ChrisBeach also experienced the issue and suggested finding a workaround. However, @merefield reported that the issue is fixed in iOS 12.1 Beta 2 build, and @pmusaraj confirmed the fix. Unfortunately, the fix is not included in the publicly released 12.0.1, and users will have to wait for the 12.1 public release ChrisBeach.
I spent a few hours looking into this issue, and I couldn’t figured out how to solve it.
But I did notice though that this can happen on any website, focusing on an input and then focusing out of it causes the text on the page to become unselectable. This points to a general iOS 12 bug, not a Discourse-specific bug.
Here is a quick video done with the Simulator to demonstrate the issue on google.com for example:
Looks like this isn’t our bug @ljpp . Did you want to write Apple and tell them how they should restructure their development process to make it better in your professional opinion?
I wonder if we could find some kind of workaround - or at least figure out what it is about the action of bringing up the composer window which triggers the bug.
I’m on Beta 2 of iOS 12.1 build on my iPhone and cannot repro this issue, quoting is fine. So please check this build (16B5068i) and it may be Apple has fixed it? I certainly saw a lot of broken things wrt Discourse on Safari 12 during the PB.