Hey @eduardolundgren, @brunobasto, @fernandosouza, this is a tentative fix for #11.
For the fallback, I've added the check used by the DOM-URL polyfill
The native implementation in Safari is non-standard, and doesn't throw for overflowing ports, so I've added a simple check against the stored href to verify it is the same, although it might fail if the overflowing port contains the max port number... we can improve it a bit more if necessary
Hey @eduardolundgren, @brunobasto, @fernandosouza, this is a tentative fix for #11.
DOM-URL
polyfillhref
to verify it is the same, although it might fail if the overflowing port contains the max port number... we can improve it a bit more if necessary