[Webkit-unassigned] [Bug 219577] New: Safari implicitly converts character in XHR request

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=219577

            Bug ID: 219577
           Summary: Safari implicitly converts character in XHR request
           Product: WebKit
           Version: Safari 14
          Hardware: All
                OS: All
            Status: NEW
          Severity: Blocker
          Priority: P2
         Component: Text
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: birowsky at gmail.com
                CC: mmaxfield at apple.com

I picked this character "〉" as a separator for my combo-key-field for my DynamoDb database.

That character surfaces in the browser as part of a next-page-query token. (in an endless scroll list view)

Chrome properly sends that character to the backend (as part of the next-page-query token).

However, Safari, sends that character as this character: "〉", which is different, and as a result, my backend is unable to recognise it.

Why is the browser changing the character? Is this behaviour expected? Did I miss declaring a char-set somewhere?

Probably an important finding is that running '〉' === '〉' returns true in Safari.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20201206/49a24c05/attachment.htm>