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 20121 - See Also context hints
Summary: See Also context hints
Status: NEW
Alias: None
Product: webplatform.org
Classification: Unclassified
Component: skin (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Doug Schepers
QA Contact: public-webplatform-bugs list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-28 16:00 UTC by Mike Sierra
Modified: 2012-11-28 16:06 UTC (History)
0 users

See Also:


Attachments

Description Mike Sierra 2012-11-28 16:00:08 UTC
See apis/css-regions for example. Undifferentiated links give little idea of context. Ideally prefix w/icons giving feedback about what sort of info is at the destination:

a[href=~"/dom"]::before { content: url(icon_dom.png) }
a[href=~"/apis"]::before { content: url(icon_api.png) }
a[href=~"/css/properties"]::before { content: url(icon_cssprop.png) }
a[href=~"/css/cssom"]::before { content: url(icon_cssom.png) }

Perhaps a deeper template rather than skin issue, but see-alsos for API member pages might also benefit by being prefixed with the interface name. In this case, instead of "name", "NamedFlow.name" gives more context.
Comment 1 Mike Sierra 2012-11-28 16:06:20 UTC
See-also links displaying "NamedFlow.name property" or "NamedFlow.getContent method" would provide yet more context.