- From: <bugzilla@jessica.w3.org>
- Date: Tue, 07 Jun 2011 23:14:49 +0000
- To: public-script-coord@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12845 --- Comment #12 from Cameron McCormack <cam@mcc.id.au> 2011-06-07 23:14:47 UTC --- (In reply to comment #11) > That seems like the sort of footgun issue we're talking about here. Why > shouldn't the command API be usable for <track>? If there's a good reason, why > does it not apply to random other HTML elements? At a guess, I would say that the command API properties on HTMLElement exist to reflect the command-ness of elements that intrinsically define commands, such as <button>, <a href>, etc. <command> lets authors define a custom command that doesn't correspond to a visible element. The properties are defined to return ""/false on elements that don't define a command, including <track>. So I guess the properties were put on HTMLElement because that's the common ancestor of the different elements that define commands. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
Received on Tuesday, 7 June 2011 23:14:51 UTC