[widgets][vmmf] clarifications

Hi All,

I have modified the VMMF draft at http://dev.w3.org/2006/waf/widgets-vmmf/ and merged the comments from Vodafone after reviewing them.
I have the following questions that I would like to agree on (the VMMF text highlights the corresponding content):

1. Does the "interactivity" affect the value of "disabled" attribute of the instances of the HTMLInputElement in the document? (I assume yes)

2. Does the "interactivity" affect the ":enabled" and ":disabled" pseudo-classes? (I assume yes)

3. Since "opacity" property in CSS affects the rendered elements' tree, it seems we cannot use "opacity" on <body> element to make it transparent. What about defining new property (e.g. "transparent: on | off") that would be applicable on <body> element only? Then the transparency would depend on the content and not on the view-mode, thus it would limit the necessity for additional values. For example, I would like to have the widget behave like fullscreen or mini, but the transparency could depend on the content.

4. Should we use the DOM0 objects in the spec? It seems to be clearer to the readers, but the objects / methods / attributes are not normatively documented.


Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452  |  Fax: +49-208-8290-6465
Mobile: +49-163-8290-646
E-Mail: marcin.hanclik@access-company.com


Access Systems Germany GmbH
Essener Strasse 5  |  D-46047 Oberhausen
HRB 13548 Amtsgericht Duisburg
Geschaeftsfuehrer: Michel Piquemal, Tomonori Watanabe, Yusuke Kanda


This e-mail and any attachments hereto may contain information that is privileged or confidential, and is intended for use only by the
individual or entity to which it is addressed. Any disclosure, copying or distribution of the information by anyone else is strictly prohibited.
If you have received this document in error, please notify us promptly by responding to this e-mail. Thank you.

Received on Thursday, 14 January 2010 14:53:08 UTC