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 18024 - Apply 'tag' (link type) to its nearest article or body element ancestor
Summary: Apply 'tag' (link type) to its nearest article or body element ancestor
Status: RESOLVED WONTFIX
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-18 15:45 UTC by contributor
Modified: 2012-08-25 16:48 UTC (History)
4 users (show)

See Also:


Attachments

Description contributor 2012-07-18 15:45:50 UTC
This was was cloned from bug 17579 as part of operation convergence.
Originally filed: 2012-06-23 00:10:00 +0000
Original reporter: res-html@untief.org

================================================================================
 #0   res-html@untief.org                             2012-06-23 00:10:21 +0000 
--------------------------------------------------------------------------------
(if it's undesirable for a link type definition to differ from 'a'/'area' to 'link', dump this issue)

The spec about the 'rel' keyword 'tag' states:
"The tag keyword indicates that the tag that the referenced document represents applies to the current document."

I think it would be useful if the tag (when linked with the 'a'/'area' element) applies to its nearest article or body element ancestor, instead (which is the case for the 'address' element, too).

Thereby a page listing several articles could make use of the 'tag' keyword:

<section>
  <h1>Recent articles</h1>

  <article>
    <h1>My first cooking lesson</h1>
    <p>… — <a href="/blog/cooking-lesson">Read more</a></p>
    <footer>Tagged with <a href="/tags/cooking" rel="tag">Cooking</a></footer>
  <article>

  <article>
    <h1>I scored two goals</h1>
    <p>… — <a href="/blog/two-goals">Read more</a></p>
    <footer>Tagged with <a href="/tags/football" rel="tag">Football</a></footer>
  <article>

</section>

With the current definition, the tags "Cooking" and "Football" apply to the whole page. 
With my proposed addition, the tag "Cooking" applies only to the first article snippet, the tag "Football" only to the second.
================================================================================
 #1   res-html@untief.org                             2012-06-23 00:14:12 +0000 
--------------------------------------------------------------------------------
(sorry, I messed up the example; another try)

<section>
  <h1>Recent articles</h1>

  <article>
    <h1>My first cooking lesson</h1>
    <p>… — <a href="/blog/cooking-lesson">Read more</a></p>
    <footer>Tagged with <a href="/tags/cooking" rel="tag">Cooking</a></footer>
  <article>

  <article>
    <h1>I scored two goals</h1>
    <p>… — <a href="/blog/two-goals">Read more</a></p>
    <footer>Tagged with <a href="/tags/football" rel="tag">Football</a></footer>
  <article>

</section>
================================================================================
Comment 1 Ian 'Hixie' Hickson 2012-08-25 16:48:22 UTC
If I recall correctly, the specced behaviour matches deployed implementations, so can't really be changed.