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 22853 - Little confused by example "4.8.1.1.16"
Summary: Little confused by example "4.8.1.1.16"
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 editorial
Target Milestone: ---
Assignee: steve faulkner
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-01 16:37 UTC by dmacdona
Modified: 2016-04-22 17:22 UTC (History)
7 users (show)

See Also:


Attachments

Description dmacdona 2013-08-01 16:37:40 UTC
There are two separate code examples back to back with nothing in between.

==================

In this example, we have a link pointing to a site's home page, the link contains a house icon image and the text "home". The image has an empty alt text. Where images are used in this way, it would also appropriate to add the image using CSS 

  <a href="home.html"><img src="home.gif" width="15" height="15" alt="">Home</a>
  #home:before
  { 
  content: url(home.png);
  }=
  <a href="home.html" id="home">Home</a>
  
==============
Perhaps rearrange like this:

In this example, we have a link pointing to a site's home page, the link contains a house icon image and the text "home". The image has an empty alt text. 

  <a href="home.html"><img src="home.gif" width="15" height="15" alt="">Home</a>
 
Where images are used in this way, it would also appropriate to add the image using CSS.

 #home:before
  { 
  content: url(home.png);
  }=
  <a href="home.html" id="home">Home</a>

=======================

*Also note that period is missing from end of sentence:
...it would also appropriate to add the image using CSS
Comment 1 Arron Eicholz 2016-04-22 17:22:11 UTC
HTML5.1 Bugzilla Bug Triage: Fixed, see the change

https://github.com/w3c/html/pull/238

If this resolution is not satisfactory, please copy the relevant bug details/proposal into a new issue at the W3C HTML5 Issue tracker: https://github.com/w3c/html/issues/new where it will be re-triaged. Thanks!