Talk:Requests for comment/Clickable section anchors

Implementation
$('#mw-content-text').find('.mw-headline').after(function {	return $('')		.text('[#]')		.css({'color': '#aaa', 'font-size': '12px', 'margin-left': '1em'})		.attr('href', '#' + $(this).attr('id')) })

Code from Matma Rex. --MZMcBride (talk) 18:17, 16 July 2013 (UTC)

Implementation (2)
See MediaWiki:Gadget-vector-headanchor.js and MediaWiki:Gadget-vector-headanchor.css. Krinkle (talk) 18:22, 16 July 2013 (UTC)


 * Option 2, left margin looks great to me on desktop. What would be the implementation on mobile, though?  Also, have you had a chance to run this by someone in UX? -- RobLa-WMF (talk) 17:35, 2 January 2014 (UTC)

What does it copy, a wikilink, ID, or href?
The proposal reads to provide a copyable  or possible

But the talk about the link icon makes it sound as if it's to provide a full hyperlink URL,. Well, which? Sometimes you want one, sometimes you want the other.

The Flow discussion and collaboration extension uses a permalink icon in the right margin that is an hyperlink so that right-click > Copy Link Location provides a full href URL. We may move it into an action menu.

-- S Page (WMF) (talk) 00:02, 7 January 2014 (UTC)

Clear User Need?
First of, who is in need of this feature? Who are the users?

Only when this feature is a clear improvement for the majority of our users – without bringing confusion or slowing them down in their tasks (like impairing reading fluency, at skimming a page or finding the edit link) – it is useful to implement. Is it probably just a power user feature, that doesn't need to be in core or doesn't need to be activated by default (optional user setting)? , All the examples given in this task discussion so far has been technical documentation  and in one case legal text. Is this, because the usage of section links is much more needed or because it address a special engineering/judicial thinking? Do we have implementations in text heavy sites apart from those, NY Times seem to have abandoned their try again ?


 * “I can understand that the most people do not need this feature, so the best way is it to implement it as option or gadget. I personally use it longtime as gadget from @Schnark […]”
 * I have the gadget enabled on mediawiki, and I miss it on other wikis (where I have to use the workaround of: scrolling up to the top of the page and clicking in the ToC). I use it to obtain links (from the browser address bar) for sharing (email/IRC/phabricator/twitter/etc), and sometimes to obtain links for onwiki content creation or discussions (if the former then I have to remove the underscores manually and fix any percent-encoding; if the latter I usually do the same, but not always due to laziness). I use the functionality (or try to at other wikis) about 3 times a week, and have done so consistently for many years. Quiddity (WMF) (talk) 00:50, 7 April 2016 (UTC)

What to share/copy?

 * wikilink,
 * ID or
 * href (full URL)
 * Pro: To accomplish possibly broadest usage (think social media sharing) a full URL seems advantageous --VEckl (WMF) (talk) 08:23, 24 March 2016 (UTC)
 * We do not want to override the OS clipboard (we don't want editors to accidentally overwrite multiple paragraphs they were storing there, due to an accidental click). We just want to update the browser's address bar (as the MediaWiki gadget does), or provide a copyable string (as the Frwiki gadget does). Quiddity (WMF) (talk) 00:57, 7 April 2016 (UTC)

Visibility, also which trigger event?
Findability versus distraction - On focus (Patch) - If visible, how strong? Intended patch, which targeted to decrease contrast. Take in account color contrast requirements! --VEckl (WMF) (talk) 08:23, 24 March 2016 (UTC)

Iconography? (Option 2)
Discussions on which icon:
 * Is there an icon that works globally as clear identifier for this proposed action applied to it?
 * If not, can we choose a global default, but enable an easy per-wiki override? (Probably, per T18691.)
 * Section sign: §
 * Uses: Implementation example at W3C on right side Implementation example at W3C before the heading on the left
 * Pro: "I propose to keep using the "§" symbol: it's not what I originally proposed, but we already tried it and we saw it's mostly well-received. It's correct and used in any text which needs to refer to sections, not only laws (also in German; [example for non-legal usage has been received as not appropriate in current times further down])." Enwiki's w:en:template:See also automatically converts  into.
 * Con: In some languages mainly just used in legal context (German, Norway, Polish)  & . I fully agree with that, in German language, it's nowadays used exclusively in judicial context --VEckl (WMF) (talk) 08:23, 24 March 2016 (UTC)
 * Link chain icon: 🔗 or Link_icon.svg
 * Uses:
 * Pro:    &
 * Con: The link icon is already widely used to set a link in VE, in old wikitext editor surface. Getting a section link is a different action. --VEckl (WMF) (talk) 08:23, 24 March 2016 (UTC)
 * Bookmark icon: 🔖 or Bookmark_icon.svg
 * Uses:
 * Pro:
 * Con: Link chain icon more intuitive
 * Anchor icon: ⚓
 * Uses:
 * Pro:
 * Con: ; Technology-driven metaphor, doubting that most people who haven't been working with HTML directly, are aware of “anchor” metaphor. --VEckl (WMF) (talk) 08:23, 24 March 2016 (UTC)
 * Number sign: #
 * Uses:
 * Pro: Clicking the link will add "#foo" to the URL, so this option is somewhat logical.
 * Con: Used in wiki markup as number list item. Widely used in connection with hashtags.
 * Paragraph sign/pilcrow: ¶
 * Uses:
 * Pro:
 * Con: We're Not actually linking to individual paragraphs.
 * The section's numbers themselves: 1.2.3
 * Uses:
 * Pro: We already have "Auto-number headings" in Special:Preferences (default-off), and we could just make those numbers into links (and perhaps reduce their size, and color them grey, to distinguish them from content), if we decided to not make this a default-on feature.
 * Con: Would probably have to be default-off, and thus vastly less discoverable, due to ambiguity and size. Would probably have to remain permanently-visible (not use a hover state) due to expectations from current users.

Option 3
Having an  seems not to affect VoiceOver. It reads it as normal heading. See http://s.codepen.io/Volker_E/debug/KzmQQL --VEckl (WMF) (talk) 08:23, 24 March 2016 (UTC)