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
When at the /post URL, iOS cannot select the full private URL provided in the text box, if the URI contains underscores. Currently, this can only be replicated in Chome for iOS, so it may also be a Chrome bug.
As such, should the base64 characters change in the URL that prevents iOS from doing word separation on underscores?
The text was updated successfully, but these errors were encountered:
I should be able to fix this. Provided that the nonce can be both base64-encoded and base64-decoded, any set of characters that are URL safe should be valid. However, this will invalidate any links sent via email/SMS/etc. that have not yet been opened.
It may be more worthwhile to report a bug upstream to either iOS or Chrome.
When at the /post URL, iOS cannot select the full private URL provided in the text box, if the URI contains underscores. Currently, this can only be replicated in Chome for iOS, so it may also be a Chrome bug.
As such, should the base64 characters change in the URL that prevents iOS from doing word separation on underscores?
The text was updated successfully, but these errors were encountered: