[Suggestion] Consider using more strict parsing for auto URL highlighting
Thank you for the suggestion. I'm afraid it would require more sophisticated scripts, and it might not be worth the trouble since you can already use
inline codeto work around this, like that:
This forum uses Markdown. You can learn more about it here. Hope this helps.
Thanks for the reply. It should only require less sophisticated scripts.
The trouble... if you wouldn't mind leaking some of the implementation details, I might help with the implementation.
I know about Markdown. I also know about Markdown's ineffectiveness.
What if we do not wish the component be marked as code?
@masterquestionable I'm not the one who's making these changes - just expressed some of my concerns, as I think it might not be worthwhile. Nevertheless, I haven't moved your request anywhere, which means, that we might still look into this, if the community shows interest in this issue.
I noted a more severe problem: the highlighting scheme is even meddling with the parsed URL's visual representation. (as displayed in [ https://forum.vivaldi.net/post/598856 ]; and may be tested trivially)
The semantic difference is distinct and that must not be ignored. (URI encoded components vs. literal)
@masterquestionable What is the issue with the post you mentioned? The link works properly.
As for other aspects of your formatting, why not use the markdown options available on this forum?
So instead of this:
You could do this:
After text with a link here https://forum.vivaldi.net/post/598856 and some more text.
With this markdown:
Example list: - `one.so` - `other.com` After text with a link here https://forum.vivaldi.net/post/598856 and some more text.
Or this if you want different text to show up for the link:
After text with a link [here](https://forum.vivaldi.net/post/598856) and some more text.
for this result:
After text with a link here and some more text.
It currently looks as if you are trying to force some other formatting from another system.
The semantic difference between '''URI encoded components''' and the '''literal representation''' is distinct and that must not be ignored. 
Taken the example from the link: the "%5B" was meddled to "[" (and the "%5D" to "]").
 And the "%22" here to `"`.
While the link indeed works in many cases, not having certain characters escaped might cause interoperability issues under certain circumstances.
See [ https://pastebin.com/raw/YTi5UzLq ] for some background. ]
Thank you for your effort, but you do not really have to teach me Markdown.
In short: for general interoperability.
<.> Further reading:
|*| https://en.wikipedia.org/wiki/Template_talk:Portal?oldid=1104009396#Use_of_"Johnny-automatic-scales-of-justice.svg" 
<.> Also, Markdown has difficulties representing complex structures.
=== Off-Topic ===
If you have the time and interest, please help checking the status of my previous reports: there are recent updates of Vivaldi that may have things changed.