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

Link input without URI scheme should be completed with HTTPS by default #46244

Open
porg opened this issue Dec 1, 2022 · 4 comments
Open

Link input without URI scheme should be completed with HTTPS by default #46244

porg opened this issue Dec 1, 2022 · 4 comments
Labels
[Feature] Link Editing Link components (LinkControl, URLInput) and integrations (RichText link formatting) Needs Decision Needs a decision to be actionable or relevant [Type] Enhancement A suggestion for improvement.

Comments

@porg
Copy link

porg commented Dec 1, 2022

Reproduction

  1. Select an element which supports a hyperlink, e.g. text in a paragraph.
  2. Press the link button or shortcut (⌘ K)
  3. Into the text field "Search or type url" type or paste an URL without the URI scheme at the beginning, e.g. "example.com/page"
  4. Press ENTER to confirm and close the dialog.

Actual

  • Upon inspection you see that the link was created with http:// prepended.

Expected

  • In this day and age the auto completion should default to https://

HTTPS as the default scheme? Arguments pro (✅) or against (❌) or uncertain (ℹ️)

  • ✅ The majority of websites moved to HTTPS.
  • ❌ Most HTTPS websites have set up HTTP to HTTPS redirections, so most users will get to their destinations anyways.
  • ✅ But that redirection means longer wait times to reach the destination, instead of a correct HTTPS on first try.
  • ❌❌ Falsely using HTTPS for a page that is HTTP only fails totally.
    • The user has to realize this and manually correct in the address bar. Some users will fail here.
  • ℹ️ I do not know if it has negative/punishing SEO implications on your website if your outgoing links use predominantly HTTP (for destinations which actually are available as HTTPS).

My preliminary conclusion (no CMS or SEO or W3C expert at all)

  • Overally it seems that defaulting to HTTP is safer, but nevertheless it kinda feels wrong in this day and age.
  • You experts decide. It's just something that came to my attention.
@skorasaurus skorasaurus added [Feature] Link Editing Link components (LinkControl, URLInput) and integrations (RichText link formatting) Needs Decision Needs a decision to be actionable or relevant labels Dec 1, 2022
@jordesign jordesign added the [Type] Enhancement A suggestion for improvement. label Jul 28, 2023
@jordesign
Copy link
Contributor

I see this has been resolved for adding links to the buttons block specifically (in #46385).

@eoinsav @getdave is there any way the work from that could be brought in to impact here more broadly?

@getdave
Copy link
Contributor

getdave commented Jul 28, 2023

Yes it could be done.

@porg
Copy link
Author

porg commented Jul 28, 2023

@WDWNT-Frank
Copy link

Just wondering but is anything being done on this? It's still n issue and not resolved in any way.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Feature] Link Editing Link components (LinkControl, URLInput) and integrations (RichText link formatting) Needs Decision Needs a decision to be actionable or relevant [Type] Enhancement A suggestion for improvement.
Projects
None yet
Development

No branches or pull requests

5 participants