As I'm not sure if we should implement the spec as is. The last time I checked, no other UA implemented command API, and I don't necessarily agree with all the design decisions they've made.
For example, I'm not sure if command's state should be directly tied with the element that defines a command. Also it seems odd that an element that defines commands can be a part of UI. In particular, I would not want to see us implementing http://dev.w3.org/html5/spec/Overview.html#building-menus-and-toolbars. I think we should start from listing use cases first. - Ryosuke On Tue, Nov 22, 2011 at 11:09 PM, Rakesh Chaitanya <[email protected]>wrote: > Hi WebKit, > > I am planning to implement the command API in WebKit. The specificationfor > the same is > here <http://dev.w3.org/html5/spec/Overview.html#commands>. > > Command API defines DOM apis for the elements which are commands. Any > element with a 'accesskey' attribute defines a command except few(like 'a', > 'button') where the condition to define a command is different. A command > is one of the component in > menu<http://dev.w3.org/html5/spec/Overview.html#building-menus-and-toolbars> > . > > Please let me know your suggestions and inputs on the same. > > The WebKit bug for this is https://bugs.webkit.org/show_bug.cgi?id=72955, > I have put up a basic implementation here. > > -- > Regards, > Rakesh > > > _______________________________________________ > webkit-dev mailing list > [email protected] > http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev > >
_______________________________________________ webkit-dev mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
