...
65. Gadget Spec: Action Contributions... in runAction, there is the statement, "The gadget should call this method whenever an action is triggered by the user." ... I assume this is meant to say "The container should..." as it is the container that actually invokes the callback function.
66. Gadget Spec: Action Contributions... when using gadgets.actions.registerShowActionsListener, will the container invoke the callback immediately after registration to let the gadget know about any actions contributed BEFORE the listener was registered or will the gadget only be notified of actions registered AFTER the listener is registered? Same question with regards to registerHideActionsListener. Is registerHideActionsListener called when the gadget is closed or uninstalled? It's not clear. The spec simply says when the container unloads the gadget. What does unload mean as far as lifecycle events are concerned?
67. Gadget spec: PubSub-2... Use of variable substitution in Topic element names really doesn't seem to make a lot of sense as defined currently. The text says that it's use to supposed to make interop easier but it actually doesn't appear to do that at all since gadgets would be leaving it entirely up to the container to figure out what the topic names are... the gadget would never really be able to know what it should expect to get.
...
83. Gadget Spec: The gadgets.views.View.getUrlTemplate and bind methods are defined without any real explanation about why they exist or how they relate to the current view.
84. Gadget Spec: When calling gadget.views.openEmbeddedExperience and passing in both an EE dataModel AND opt_params... and both specify view and viewTarget parameters, which take precedence?
85. Gadget Spec: For ModulePrefs/@screenshot... why do we need to specify a specific size or format for the image? Why not simply let the container figure this out?
...