osm

    • May 15, 2024
    • Joined May 14, 2024
    • 1 discussion
    • 1 post
    • 0 best answers
    • 2 points
    • I think what's going on is that under the hood Orion handles the properly encoded url (with + as %2B for example) but presents the "decoded" url to the user.
      But the decoded url is the one that the user gets in their clipboard and is also the one that gets used when hitting enter in the address bar which breaks some websites in some situations.

      1. Go here: https://www.google.com/search?q=%2B
      2. Copy the URL and re-paste back into the searchbar (or just select the URL and press enter)
        • Notice the google search box is empty and the results are stuff like wikipedia etc

      Some other urls that behave differently with the same steps to reproduce:

      • Search on google for C# (as noted in #6347)
        • Originally shows results for C#
        • With the copy bug the results are about C instead
      • A link to my own project
        • Originally shows the state of the app
        • With the copy bug the app breaks (this is due to some json parsing issue around the + symbol)

      Tested in Chrome, Safari & Firefox and none had the same behaviour as above.

      (Possibly) related issues: #6347 #5046


      When copying the url I expect to get the url encoded version in my clipboard.
      This means links shared with others won't be broken (which is how I discovered the bug).

      When editing the url I expect Orion to either always show the encoded url or always encode the result of whatever the user types.

      Version 0.99.127.3-beta (WebKit 619.1.1)

      Sonoma (14)