[WARP] Last Call comments (1)

Hi All, Here are a couple of the Last Call comments to WARP LCWD [1]. They were already partially presented in my emails [2] and [3]. The comments below are more of architectural nature than just editorial fixes. That is why the arguments together with the derived understanding are followed by t

PFWG comments on Widgets 1.0: Packaging and Configuration Last Call (late, very late)

This is a review of Widgets 1.0: Packaging and Configuration , the Last Call Working Draft. These comments are submitted on behalf of the Protocols and Formats Working Group and are focused on accessibility to people with disabilities. We apologize f

[widgets] P&C UA does not deal with SVG icons

I also don't believe that the following text belongs in the P&C spec (though it certainly needs to go somewhere): [[ A user agent that supports [SVG] as an icon format may display declarative animation. However, for security reasons, a user agent must not execute scripts or interactivity defin

[widgets] P&C the following should be a note

For the purpose of testing, the following assertion should be a note: [[ A user agent that supports the [Widgets-APIs] specification must expose any declared preference to the author at runtime via scripting in the manner described in the [Widgets-APIs] specification. ]] I propose changing it

[widgets] More misplaced assertions

I don't think the following two assertions are worth testing (and should not apply to the P&C UA). [[ A user agent should expose custom icons in a way that it is visible to the end user. ]] And... [[ When the license element's href attribute is used, the user agent should provide end users

[widgets] Draft Minutes for 27 August 2009 Voice Conference

The draft minutes from the August 27 Widgets voice conference are available at the following and copied below: http://www.w3.org/2009/08/27-wam-minutes.html WG Members - if you have any comments, corrections, etc., please send them to the public-webapps mail list before 3 September 2009 (th

[widgets] P&C, assertion in wrong spec

For the purpose of testing, I think the following assertion is in the wrong spec (P&C): [[ A user agent must prevent a browsing context of a widget from accessing (e.g., via scripts, CSS, HTML, etc.) the contents of a digital signature document unless an access control mechanism explicitly ena

[WebIDL] "proper UTF-16 string"

In section 3.7.12 DOMString, Web IDL speaks of a "proper UTF-16 string". However, it is not defined what a "proper UTF-16 string" is. I presume it means a valid UTF-16 string (per D30e of Unicode 4.0 and D89 of Unicode 5.1). The simplest solution would be to change "proper UTF-16 string" to "va

Re: ISSUE-99 (listen): Add shorter method names for addEventListener, et al? [DOM3 Events]

I agree, also it is trivial for a developer or library to provide aliases to provide the shortened form (including supporting listenOnce) -- additionally "unlisten" is incredibly awkward sounding :D --Oliver On Aug 27, 2009, at 2:46 AM, Sergey Ilinsky wrote: Starting shortening member names

Re: ISSUE-99 (listen): Add shorter method names for addEventListener, et al? [DOM3 Events]

Starting shortening member names can open the Pandora box. What about getElementsByTagName, querySelector etc.? I think at this point of time it is better to avoid such an initiative. Sergey/ --- On Thu, 27/8/09, Web Applications Working Group Issue Tracker wrote: > From: Web Applications

RE: DOM3EV: [ViewModes] typeArg on initXXXEvent

Hi Doug, Thanks for the information! I agree with the lowercase convention, but tried to be consistent with DOM3Events. I will update the ViewModes pre-FPWD with lowercase accordingly. Thanks, Marcin Marcin Hanclik ACCESS Systems Germany GmbH Tel: +49-208-8290-6452 | Fax: +49-208-8290-6465 Mo