polyfill inconsistent with chrome by how it handle search
See original GitHub issuethis example works in chrome & Deno
new URLPattern({ search: "a=:a" }).exec('http://localhost?a=x/y')
but that does not work with the polyfill
the problem seem to be in where the search param value includes a /
replace x/y
with just xy
and it works
Issue Analytics
- State:
- Created a year ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Handling common JavaScript problems - MDN Web Docs
Polyfills use JavaScript or other technologies entirely to build in support for a feature that a browser doesn't support natively. For example, ...
Read more >How to add a polyfill to support finally() in Edge?
I'm using axios library and using then(), catch() and finally(). Works perfectly in Chrome.
Read more >Set Chrome policies for users or browsers - Google Support
For administrators who manage Chrome policies from the Google Admin console. ... Tip: Quickly find a setting by entering text in the search...
Read more >Inside the container query polyfill - Chrome Developers
However, the polyfill does this at runtime instead, for two reasons: you and your visitors. With support for container queries already in ...
Read more >How to resolve JavaScript Cross Browser Compatibility Issues
Learn to find Javascript cross browser compatibility issues and how ... But because the code doesn't include Chrome 87, the feature won't be ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@wanderview, I added a test for this to the suite and updated the code to use
??
instead of||
in the relevant parts. (see #95 for details)@jimmywarting Can you give version 5.0.1 a try and see if it works for you too?
I will close this issue now, as it should be fixed. Depending on feedback, we might need to reopen.
We could fix that in our local copy. I think that would be fine