W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2009

[A&E] Last Call comments (1)

From: Marcin Hanclik <Marcin.Hanclik@access-company.com>
Date: Tue, 15 Sep 2009 23:29:31 +0200
To: "public-webapps@w3.org" <public-webapps@w3.org>
Message-ID: <FAA1D89C5BAF1142A74AF116630A9F2C2890C6626A@OBEEX01.obe.access-company.com>
The below comments refer to:
Widgets 1.0: The widget Interface
Editor's Draft 14 September 2009

General:
Replace "can" with "may" in the whole document.

2.
Feature
Why to repeat the definition from P&C?

Getting / Setting
Refer to HTML5 for those definitions?

Viewport
[1] says that scrollbars are part of the rendering area
(I do not claim that it is fully correct, I assume scrollbars are a discussion point, specifically in the context of DHTML where they could appear and vanish depending on the dynamic content).
My proposal is to make this definition non-final.

All definitions:
Could we have a document with the definitions for all specifications from the family?

3.
achived -> achieved

4.
Again about the definitions:
Could we have a common definition of the user agent, decoupled from the specs?
(e.g. UA in P&C is an implementation, here it is a software implementation)

4.2
a read-only item is an item in a storage area cannot be ...
should be
a read-only item is an item in a storage area that cannot be ...

5.
Why aren't the following attributes available on the widget interface?
@viewmodes from <widget>,
@short from <name>,
@href from <license> and license,
icons

5.
It preferences(via the preferences attribute).
Unclear.

5.
A user agent should to impose ...
Should be
A user agent should impose ...

5.
... global object context of the widget's start file.
What about:
... global object context of the document loaded from widget's start file.
???

5.
In
... global object context of the widget's start file.
And
A user agent whose start file implements HTML5's Window interface ...
The "start file"s refer to 2 different locations.

5.4
How to handle multiple instances of the same widget?
As far as I remember it was to be moved to WURIv2, but it seems important in the context of preferences.

5.4
Storage interface:
The A&E specification should not add interpretation to the WebStorage with regard to the exceptions thrown. It would be better to improve the WebStorage specification.
Specifically the NO_MODIFICATION_ALLOWER_ERR shall be presented in WebIDL on Storage interface based on "raises" keyword of WebIDL.

5.4.1
onClick -> onclick

5.4.2#3
... make the preferences attribute a pointer that storage area.
Should be
... make the preferences attribute a pointer to that storage area.

5.4.2#2.4.1
... apply the  rule for dealing with an invalid Zip archive ...
And
"In the event that an implementation encounters an invalid Zip archive ...
In the case the UA is a CC, it must inform the author that the Zip archive is an invalid Zip archive." From P&C.

Do not play well together.
The problem is with the WUA and not with the widget, so the correct information should be provided to the user.

The problem
5.5
... should open the provided iri ...
What does opening of the IRI mean?
Maybe this would work (IRI handler could be defined anyway) :

... should handle the provided iri ...

5.5
... it is otherwise rejected by the user agent (e.g., because of security policy or user prompting), or iri is not a valid IRI, then the user agent must act as if the method had not been invoked.

The user agent should inform the end-user when a request to handle the IRI via the openURL() method has failed.

The above requirements seem contradicting and not prepared for handling the security policy.
a) acting as if the method had not been invoked (a MUST) and informing the end user (a SHOULD) may not work well together.
b) it should be possible for the UA to reject the call to openURL, and then the exception or error shall be thrown, so that the script could catch it and inform the user.
I suggest leaving the WebIDL for openURL to DAP.

5.5
Last sentence seems to be lost in action.

[1] http://dev.w3.org/2006/waf/widgets-vm/vm-mediafeature.src.html

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

www.access-company.com

CONFIDENTIALITY NOTICE
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 Tuesday, 15 September 2009 21:30:27 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:33 GMT