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 18253 - typo "or explicit ignored"; should be "or explicitly ignored"
Summary: typo "or explicit ignored"; should be "or explicitly ignored"
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: Other other
: P4 normal
Target Milestone: ---
Assignee: Silvia Pfeiffer
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords: CR, editorial
Depends on:
Blocks:
 
Reported: 2012-07-18 17:50 UTC by contributor
Modified: 2013-06-06 07:51 UTC (History)
5 users (show)

See Also:


Attachments

Description contributor 2012-07-18 17:50:51 UTC
This was was cloned from bug 17605 as part of operation convergence.
Originally filed: 2012-06-26 14:02:00 +0000

================================================================================
 #0   contributor@whatwg.org                          2012-06-26 14:02:47 +0000 
--------------------------------------------------------------------------------
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/parsing.html
Multipage: http://www.whatwg.org/C#preprocessing-the-input-stream
Complete: http://www.whatwg.org/c#preprocessing-the-input-stream

Comment:
typo "or explicit ignored"; should be "or explicitly ignored"

Posted from: 85.240.245.121
User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_4) AppleWebKit/536.5 (KHTML, like Gecko) Chrome/19.0.1084.56 Safari/536.5
================================================================================
Comment 1 Silvia Pfeiffer 2013-06-06 07:51:01 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: Accepted

Rationale: fixed