Hey, guys. I would like to bring here a discussion I had with @brunobasto.
The fallback used in Metal URI doesn't behave as expected. Differently of the main implementation, the fallback doesn't throw errors.
One example of this is when the url port exceeds the maximum allowed 65535:
For the given url http://localhost:99999 the following happens:
The main implementation throws Failed to construct 'URL': Invalid URL.
The fallback doesn't throw errors and we don't have a consistency behaviour in how browsers interpret this. Safari 5 for example replaces the given port 99999 by the maximum number allowed 65535, others replace by 0.
There is a pull request for SennaJS to prevent crashes because of errors from Metal URI, but the test fails in browsers that use the fallback.
Hey, guys. I would like to bring here a discussion I had with @brunobasto.
The fallback used in Metal URI doesn't behave as expected. Differently of the main implementation, the fallback doesn't throw errors.
One example of this is when the
url portexceeds the maximum allowed65535:For the given url
http://localhost:99999the following happens:Failed to construct 'URL': Invalid URL.Safari 5for example replaces the given port99999by the maximum number allowed65535, others replace by0.There is a pull request for SennaJS to prevent crashes because of errors from Metal URI, but the test fails in browsers that use the fallback.