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 18274 - looking for illustration
Summary: looking for illustration
Status: RESOLVED NEEDSINFO
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-18 17:55 UTC by contributor
Modified: 2012-08-20 19:38 UTC (History)
4 users (show)

See Also:


Attachments

Description contributor 2012-07-18 17:55:23 UTC
This was was cloned from bug 17662 as part of operation convergence.
Originally filed: 2012-06-30 16:35:00 +0000

================================================================================
 #0   contributor@whatwg.org                          2012-06-30 16:35:22 +0000 
--------------------------------------------------------------------------------
Specification: http://www.whatwg.org/specs/web-apps/current-work/
Multipage: http://www.whatwg.org/C#entity-Agrave
Complete: http://www.whatwg.org/c#entity-Agrave

Comment:
looking for illustration

Posted from: 69.119.1.17
User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:14.0) Gecko/20100101 Firefox/14.0
================================================================================
Comment 1 Erika Doyle Navara 2012-08-20 19:38:39 UTC
Please add more information to identify a problem or potential action.

A bug report is most useful if it includes the following components:

•A clear statement of a problem with the spec—bug reports are more useful if they identify concrete problems.
•Only one specific problem—please use separate bugs for separate problems with the spec.
•An indication of what section or sections of the spec are affected.
•At least one suggested way to solve the problem. Optionally, this can include sample spec text. Listing multiple alternatives is ok, and even a vague suggestion is fine at this stage.