This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
General comment: numerous elements and algorithms in HTML5 describe state and state transitions. It would be helpful to produce state transition diagrams for each of these. Additionally such diagrams will likely reveal potential problems (state unreachability, transition ambiguity, etc.) in the corresponding prose descriptions.
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: Did Not Understand Request Change Description: no spec change Rationale: I agree in principle, but could you elaborate on which algorithms you think would benefit from such diagrams? If you could illustrate what such a diagram would look like that would be very helpful also. If possible, I'd like to do this in such a way that the diagrams are written in textual form in the spec and the postprocessor generates the diagrams from them, so that they are trivial to keep up to date there's no way I'm editing PNGs every time I need to fix a bug in an algorithm. If anyone can help suggest how to do that, please let me know.