You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Safari in iOS, it's difficult to delete text in the Try Purescript! code window. Backspace seems to be the only option. I gather that this is due to some interaction between the Ace editor and iOS or Safari. (This makes issue #309 more important in this context.)
It would be nice to be able to try out Purescript on an iPad. On a real computer, you always have the option of installing Purescript, so in some ways it's more important to be able to use Try Purescript! on a tablet.
Obviously, it's unlikely that one would do real work in Try Purescript! on a tablet, but it would be nice to able to play around with the language. At present, you have to be pretty desperate to do that in iOS Safari.
Maybe I'm missing way of interacting with the editor, but I tried the usual tricks, I think. (Maybe other browsers for iOS are better, but Safari is the default, obviously.)
The text was updated successfully, but these errors were encountered:
In Safari in iOS, it's difficult to delete text in the Try Purescript! code window. Backspace seems to be the only option. I gather that this is due to some interaction between the Ace editor and iOS or Safari. (This makes issue #309 more important in this context.)
It would be nice to be able to try out Purescript on an iPad. On a real computer, you always have the option of installing Purescript, so in some ways it's more important to be able to use Try Purescript! on a tablet.
Obviously, it's unlikely that one would do real work in Try Purescript! on a tablet, but it would be nice to able to play around with the language. At present, you have to be pretty desperate to do that in iOS Safari.
Maybe I'm missing way of interacting with the editor, but I tried the usual tricks, I think. (Maybe other browsers for iOS are better, but Safari is the default, obviously.)
The text was updated successfully, but these errors were encountered: