leyrer on Nostr: So Google went to a "must use JavaScript" UI for it's search. Which currently results ...
So Google went to a "must use JavaScript" UI for it's search.
Which currently results in searches containing a "&" being cut off at that character.
Apparently Percent-Encoding <https://datatracker.ietf.org/doc/html/rfc3986#section-2.1>; is hard and an unsolved problem for those young JavaScript developers at Google.
If someone at Google could turn the front end team to the documentation their Maps team has provided: https://developers.google.com/maps/url-encoding ???
Which currently results in searches containing a "&" being cut off at that character.
Apparently Percent-Encoding <https://datatracker.ietf.org/doc/html/rfc3986#section-2.1>; is hard and an unsolved problem for those young JavaScript developers at Google.
If someone at Google could turn the front end team to the documentation their Maps team has provided: https://developers.google.com/maps/url-encoding ???