I've been storing BBO matches (missing a personal scorecard...) since 2020. My club name includes an ampersand (&) and I'm careful when creating links to the XML VG files to encode characters (& = %26) and these have worked. Until recently; now some historical files fail to load. Curiously, those with names that include straight quotes, e.g. 'A' encoded to%27A%27 do load.
Has the recent work to Handviewer changed regular behaviour?
Example: https://www.bridgeba...g-Chelsea-E.xml
Page 1 of 1
Handviewer and esape codes
#2
Posted Today, 09:56
I found the problem. In February I changed the code that parses query parameters to use the built-in URLSearchParams interface instead of an ad hoc parser on location.href. The old code method kept the %-coding, the new code decodes them, and this causes a problem when forwarding the URL to the code that downloads the file.
This should be fixed soon.
This should be fixed soon.
#3
Posted Today, 10:56
barmar, on 2026-June-25, 09:56, said:
I found the problem. In February I changed the code that parses query parameters to use the built-in URLSearchParams interface instead of an ad hoc parser on location.href. The old code method kept the %-coding, the new code decodes them, and this causes a problem when forwarding the URL to the code that downloads the file.
This should be fixed soon.
This should be fixed soon.
Thanks for prompt diagnosis.
Page 1 of 1

Help
