You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
do space replacement on hyphens as well as underscores. Convert any hostnames with underscores into hyphenated ones when sharing to social media. Disadvantage: people can no longer use hyphenated words in subdomains
do space replacement in subdomain via a double hyphen -- as well as underscores. Convert any hostnames with underscores into double hyphentated when sharing to social media.
travel back in time and make the hostname spec the same as the domain name spec Judged non-viable
Option 2 is probably the least bad.
The text was updated successfully, but these errors were encountered:
Not closing this yet because it should be refactored (one of the reasons this was tricky to debug was subdomain is a bad variable name for what it's currently used for - the subdomain with its underscore / double hyphens converted into spaces)
This issue resulted in having to remove the social media link implementation until we can figure out a way around it. FB's sharer URL validator seems to be strict and follow the distinction made in this Stack Overflow post between domain name and hostname.
Twitter's share URL is OK with them, and pasting a link to a hostname with underscores directly into FB works.
Replication:
Possible workarounds:
--
as well as underscores. Convert any hostnames with underscores into double hyphentated when sharing to social media.Option 2 is probably the least bad.
The text was updated successfully, but these errors were encountered: