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 14911 - provide a way to make UAs' ":visited" pseudo-state's behavior more consistent
Summary: provide a way to make UAs' ":visited" pseudo-state's behavior more consistent
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: All All
: P2 enhancement
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-23 16:12 UTC by Giorgio
Modified: 2011-12-09 00:20 UTC (History)
4 users (show)

See Also:


Attachments

Description Giorgio 2011-11-23 16:12:05 UTC
hello

today pages are frequently updated: for example a discussion list (a forum) contains links to pages that are updated at every user's post

the behavior of :visited is not consistent in this case, because UAs shows as ":visited" pages that are now updated

so an attribute to the anchor tag <a href="..." updatetime="datetime">...</a> can prevent UAs from activating the :visited state, that is what site designers probably want for their users.

an alternative can be to introduce an :updated pseudo state:

a{color:blue;}
a:visited{color:purple;}
a:updated{color:blue;} /* overrides :visited */

but in any case a new attribute should be introduced

hope this helps.

bye
Comment 1 Ian 'Hixie' Hickson 2011-12-07 22:58:58 UTC
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Rejected
Change Description: no spec change
Rationale: You can do this today just by putting the last update date in the URL, as in:

   <a href="forum.cgi?page=124&lastUpdated=2011-12-03">page 2</a>

...or whatnot.
Comment 2 Giorgio 2011-12-08 06:40:09 UTC
no, this will create two different pages at search engine's eyes
Comment 3 Ian 'Hixie' Hickson 2011-12-09 00:20:33 UTC
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Rejected
Change Description: no spec change
Rationale: For search engine purposes, you can use rel=canonical.