12846 2011-06-01 15:47:24 +0000 The beforeprint and afterprint shouldn't fire if the user at any time cancels the print request. These events would imply that the user actually printed. Perhaps there should be an onprint event that fired when it is actually sent to the "printer". 2011-08-12 20:23:53 +0000 1 1 1 Unclassified HTML WG LC1 HTML5 spec unspecified Other other RESOLVED NEEDSINFO http://www.whatwg.org/specs/web-apps/current-work/#head P3 normal --- 1 contributor ian ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 49017 0 contributor 2011-06-01 15:47:24 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/timers.html Section: http://www.whatwg.org/specs/web-apps/current-work/#head Comment: The beforeprint and afterprint shouldn't fire if the user at any time cancels the print request. These events would imply that the user actually printed. Perhaps there should be an onprint event that fired when it is actually sent to the "printer". Posted from: 173.161.150.137 User agent: Mozilla/5.0 (Windows NT 5.1; rv:2.0.1) Gecko/20100101 Firefox/4.0.1 53001 1 mike 2011-08-04 05:05:54 +0000 mass-moved component to LC1 54794 2 ian 2011-08-12 20:23:53 +0000 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: Do you have a test case showing what browsers actually do?