This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 26108 - hrefless anchors -- bring up information on anchor content
Summary: hrefless anchors -- bring up information on anchor content
Status: RESOLVED WONTFIX
Alias: None
Product: HTML.next
Classification: Unclassified
Component: default (show other bugs)
Version: unspecified
Hardware: All All
: P2 enhancement
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-06-16 19:28 UTC by Josh Brown
Modified: 2016-05-05 15:04 UTC (History)
3 users (show)

See Also:


Attachments

Description Josh Brown 2014-06-16 19:28:26 UTC
The anchor tag allows us to link to a destination (with a URL) or a thing (with a URN). However, very commonly on the web today, people incorrectly use URLs as a way to direct people to more information on a thing. This happens because there is currently no good alternative available.

e.g.:
    "We suggest you change your password due to the recent <a href="http://en.wikipedia.org/wiki/Heartbleed">Heartbleed bug</a> discovered in OpenSSL."

The above is typical of many links found on the internet, and highlights 3 main problems:

  1.  The semantic issue that there is currently no way to express what you really want here. Instead of "show information about the Heartbleed bug", you can only say "show this Wikipedia article about the Heartbleed bug". Wikipedia often being chosen somewhat arbitrarily.

  2.  The person creating the link will often choose their favourite online encyclopedia at the time of authoring, whereas it would be better to use the user's favourite encyclopedia at the time they follow the URL. The advantage being that the user is in control, and can use an encyclopedia that is on their own computer, or was created after the document was authored.

  3.  People often don't bother to link things that users may want to read more about because of the time it takes to get the URL to the Wikipedia article. If an href wasn't required, I probably would have linked <a>OpenSSL</a> as well, so that users who are interested could easily read about that as well.


So my proposal is that if there is an <a> tag without `href` or `name` attributes specified, browsers should take users to information about the text inside. This may involve performing a search for the text on some search engine, or going to the article on Wikipedia, but users should be able to configure this behavior.

I think this would have a positive effect on the web; like on Wikipedia, it would be easy to conveniently link things that users may want to read more about, saving users time and allowing them to get to the information they want with a single click.

The only downsides I can see is that this would reduce page ranking for sites that are currently linked to for general-purpose information, e.g. Wikipedia and Google, and that it could cause issues in some cases if you're already using anchors without `href` for some reason - http://stackoverflow.com/questions/3186767/using-anchor-without-href-just-to-get-that-hover-effect

A new tag could be created to avoid the latter, but I feel that using the existing <a> tag would be better, as it seems very logical and, in many cases, would avoid systems requiring update to support the new tag.

This is my first contribution to W3, so I'm sorry if I've done something wrong or wasted anyone's time. I hope this suggestion is useful.
Comment 1 Charles McCathieNevile 2016-05-05 15:04:36 UTC
Hi,

thanks for the contribution, and sorry it took so long to reply. While you haven't wasted people's time or done anything wrong, we are rejecting the proposal as it stands, because it requests a new feature that is a significant variation from what the Web does.

As per the current guidelines for issues [1], rather than track such requests as bugs or issues, please create a proposal outlining the desired behavior, or at least a sketch of what is wanted (much of which is probably contained in this bug), and start the discussion/proposal in the WICG [2]. As your idea gains interest and momentum, it may be brought back into HTML through the Intent to Migrate process [3].

[1] https://github.com/w3c/html#contributing-to-this-repository
[2] https://www.w3.org/community/wicg/
[3] https://wicg.github.io/admin/intent-to-migrate.html