[Bug 17092] New: "Queue a task to set the current document readiness to "complete"[...]" - this sentence is hard to understand. It is difficult to determine that the load event should be fired as part of the task that has set the current document readiness. I suggest maki

https://www.w3.org/Bugs/Public/show_bug.cgi?id=17092

           Summary: "Queue a task to set the current document readiness to
                    "complete"[...]" - this sentence is hard to
                    understand. It is difficult to determine that the load
                    event should be fired as part of the task that has set
                    the current document readiness. I suggest maki
           Product: HTML WG
           Version: unspecified
          Platform: Other
               URL: http://www.whatwg.org/specs/web-apps/current-work/#the
                    -end
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P3
         Component: other Hixie drafts (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: contributor@whatwg.org
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org


Specification: http://www.whatwg.org/specs/web-apps/current-work/
Multipage: http://www.whatwg.org/C#the-end
Complete: http://www.whatwg.org/c#the-end

Comment:
"Queue a task to set the current document readiness to "complete"[...]" - this
sentence is hard to understand. It is difficult to determine that the load
event should be fired as part of the task that has set the current document
readiness. I suggest making the task two subteps or something i.e. "queue a
task to perform the following substeps: 1) set the current document readiness
to complete 2) if the document is in a browsign context [...]"

Posted from: 2001:4c28:a030:30:219:99ff:fe0e:5501
User agent: Opera/9.80 (X11; Linux x86_64; U; Edition Next; en) Presto/2.10.289
Version/12.00

-- 
Configure bugmail: https://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 Friday, 18 May 2012 09:34:39 UTC