Closed 0x53A closed 5 years ago
Weird. On Chrome that was solved by giving an empty string to the hash.
Maybe the polyfill behaves differently, but TrimEnd('#')
could indeed help. I'll try using it to fix this problem.
Is version 1.2.1
working?
Looks good in a quick 5 minute test.
Thank you! 🐧
Apologies for even mentioning IE11 ...
We don't have a strong requirement for IE11, but it would be really nice to be able to still support it.
1) I had to polyfill URL with
url-polyfill
2) The websocket ctor throws because for some reason there is a hash at the end:If I set a breakpoint, remove the
#
then continue, it works.Do you have any idea where the hash comes from? Maybe it is an issue with
url-polyfill
, I have no clue.What do you think about just adding a
TrimEnd('#')
?EDIT: Same behavior with Edge (EdgeHTML 16.16299)