- From: <bugzilla@jessica.w3.org>
- Date: Wed, 13 Oct 2010 18:34:15 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10801 Ian 'Hixie' Hickson <ian@hixie.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |ASSIGNED --- Comment #5 from Ian 'Hixie' Hickson <ian@hixie.ch> 2010-10-13 18:34:14 UTC --- In practice, the limits have in fact been increasing over time (once or twice a decade currently). However, we could always put the limit in the spec and increase it there, I guess. Could you elaborate on what limit you would like to see specified? What should happen when the loop count has been exceeded? In particular, I'm interested in what you think should happen if the loop is aborted after some changes have been made but not all the changes that would be made if it was run to completion. Is the goal to simply stop creating elements? How would this handle a page like the ASCII art colour Tux constructed with nothing but one opening <font> per character, or pages that use nested <em>s for "semantic" tag clouds? -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Wednesday, 13 October 2010 18:34:16 UTC