URL parser thinks `>` is a valid URL character
See original GitHub issueFirst off, thanks for this awesome irc client! ❤️
Ran into an issue with the following message:
Can I Use Node.innerText? [IE 6+ | FF 45+ | Chrome 4+ | Opera 9.5-9.6+ | Safari 3.2+ | iOS 4.0-4.1+ | Android 2.3+] Overall: 97.6% <http://caniuse.com/innertext>;
The expected URL is http://caniuse.com/innertext
but lounge is grabbing http://caniuse.com/innertext>
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Which characters make a URL invalid? - Stack Overflow
When validating, you should always "think positive": ask for "what is valid", everything else is invalid. Testing against the (few) valid characters is...
Read more >Uri.parse fails to parse a valid Url · Issue #34451 · dart-lang/sdk
It is indeed not a valid URL as defined by RFC 3986. The [ and ] characters are general delimiters, and are not...
Read more >URL Encoding | Google Maps Platform
When building a valid URL, you must ensure that it contains only those characters shown in the Summary of Valid URL Characters table....
Read more >(Please) Stop Using Unsafe Characters in URLs
The characters < and > are unsafe because they are used as the delimiters around URLs in free text; the quote mark (...
Read more >Markdown parser does not recognize all valid URL paths
Markdown parser does not recognize all valid URL paths ... New! Save questions or answers and organize your favorite content. Learn more.
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
We indeed have a test for it in #972 called
should balance brackets
Hey @Niggler, #972 should have fixed that. Mind testing your examples on
master
?