- From: Mark Callow <callow_mark@hicorp.co.jp>
- Date: Thu, 19 Jul 2012 13:14:26 +0900
- To: "whatwg@lists.whatwg.org" <whatwg@lists.whatwg.org>
On 18/07/2012 13:57, Charles Pritchard wrote: > We don't have events based on poster, so we don't know whether or not it's been loaded. On 19/07/2012 09:46, Charles Pritchard wrote: > I'm not opposed to the idea, but I'm failing to see the benefit. > Still, if there's going to be one, we're going to need an > onposterloaded event. I don't understand these concerns. Step 4 of the algorithm to be run when the video element is created or the @poster attribute is set, changed or removed says: Fetch <http://www.whatwg.org/specs/web-apps/current-work/multipage/fetching-resources.html#fetch> the resulting absolute URL <http://www.whatwg.org/specs/web-apps/current-work/multipage/urls.html#absolute-url>, from the element's |Document <http://www.whatwg.org/specs/web-apps/current-work/multipage/dom.html#document>|'s origin <http://www.whatwg.org/specs/web-apps/current-work/multipage/origin-0.html#origin>. This must delay the load event <http://www.whatwg.org/specs/web-apps/current-work/multipage/the-end.html#delay-the-load-event> of the element's document. So once the documented is loaded, the poster, if there is one, will be available. Regards -Mark -- 注意:この電子メールには、株式会社エイチアイの機密情報が含まれている場合 が有ります。正式なメール受信者では無い場合はメール複製、 再配信または情 報の使用を固く禁じております。エラー、手違いでこのメールを受け取られまし たら削除を行い配信者にご連絡をお願いいたし ます。 NOTE: This electronic mail message may contain confidential and privileged information from HI Corporation. If you are not the intended recipient, any disclosure, photocopying, distribution or use of the contents of the received information is prohibited. If you have received this e-mail in error, please notify the sender immediately and permanently delete this message and all related copies.
Received on Thursday, 19 July 2012 04:14:57 UTC