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 11345 - "Errors that result in disproportionally poor performance" has a bad example. It doesn't result in disproportionally poor performance (the conforming alternative also has to examine all open elements, one at a time for each close tag). A better example is
Summary: "Errors that result in disproportionally poor performance" has a bad example....
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-19 07:16 UTC by contributor
Modified: 2011-08-04 05:04 UTC (History)
4 users (show)

See Also:

Attachments

Description contributor 2010-11-19 07:16:54 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/complete/introduction.html
Section: http://www.whatwg.org/specs/web-apps/current-work/#syntax-errors

Comment:
"Errors that result in disproportionally poor performance" has a bad example.
It doesn't result in disproportionally poor performance (the conforming
alternative also has to examine all open elements, one at a time for each
close tag). A better example is
<p><a><b><code><i><em></p><p>x</p><p>x</p><p>x</p>

Posted from: 85.227.152.46
Comment 1 Ian 'Hixie' Hickson 2010-12-31 07:07:52 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: Partially Accepted
Change Description: see diff given below
Rationale: I tried to come up with an even better example.
Comment 2 contributor 2010-12-31 07:08:09 UTC 
Checked in as WHATWG revision r5731.
Check-in comment: better example
http://html5.org/tools/web-apps-tracker?from=5730&to=5731
Comment 3 Michael[tm] Smith 2011-08-04 05:04:57 UTC 
mass-moved component to LC1