Closed vbence86 closed 7 years ago
Hey @brunobasto, @Robert-Frampton, @eduardolundgren could you guys take a look at this? We're adding a stronger support for our fallback so it behaves similarly to modern browsers.
Do you think it is worth adding this complexity or should we simply drop support or assume a slightly flunky behaviour on browsers not supporting URL
?
Hey @vbence86, I just realized we have https://github.com/metal/metal-useragent, maybe we can use that instead of a custom uaHelper
here?
Though metal-useragent
indeed exposes a function to check whether the browser is Safari, the implementation still requires a functionality to check the version. Do you want me to delegate it to metal-useragent
and rid the code of the uaHelper
fully?
or
Keep using the uaHelper with empoying the isSafari
function from metal-useragent
.
I've updated the function in order to exclude auth sections as potential port numbers.
Thanks for working on those improvements @vbence86.
@jbalsas @brunobasto I won't be able to analyze it deeply this week, you guys can take the decision. Keep in mind that this module is used everywhere by our other dependencies, can't break :)
All tests and more are passing, so that should be a good indicator... in any case, we can still run the tests on a local link for:
@vbence86, could you take care of that?
No problem, will report the results in due course.
All tests against the pointed projects have been successfully executed locally using metal-uri:travis
branch. As a reminder, please note that my local testing environment only employs Chrome.
Awesome @vbence86!!
@Robert-Frampton, can you take a look at this one and merge or ask for additional changes?
Hey guys,
LGTM. I think in regards to leveraging metal-useragent
, we should add some more functionality for checking browser versions. Once that's in place we can remove the uaHelper
from this repo.
Intent
To provide more flexible parsing functionality that works with major built-in
<a>
URI validations.