Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Does not recognize uncommon top level domain (TLD) #57

Open
Graybound opened this issue Jun 17, 2023 · 1 comment
Open

Does not recognize uncommon top level domain (TLD) #57

Graybound opened this issue Jun 17, 2023 · 1 comment

Comments

@Graybound
Copy link

It seems that if ".com", ".org", ".net" etc. is not in the url the plugin will not recognize it as a url.

It did not recognize there was a url selected when I tried to add a note about configuring the 1.1.1.1 DNS and add a iframe link to https://1.1.1.1/dns/. I noticed that if I put .com in the url like: https://1.1.1.1 .com /dns/ it would recognize there was a url. Unfortunately that is not a valid domain. A workaround I am doing is to put the ".com" make the iFrame and then changing it to the correct url after inserting the iframe.

Is it possible to set the recognition to validate based if the selected text contains "http" which would cover 99% of URLs?

For details I am experiencing this on:
2020 M1 MacBook Air running MacOS Ventura 13.4 (22F66)
Convert URL to iframe v0.5.0
Obsidian v1.3.5

@dcolli23
Copy link

This would be wonderful. I embed local HTML files (that I produced, so I know they're safe) in my journal and being able to recognize http:, file:, or app: prefixes would make this plugin a dream.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants