Hi All,
I've gone through the API and Events spec and done a general clean up
to ready the doc for publication. Changes:
* Added TOC, changed from definition list structure to headings for
easier access/overview of content
* Fixed a bunch of typos and copy/paste errors
* Added references
* Made t
Phillips, Addison wrote:
Assuming for a moment that CSS3 does not resolve the problem with
Unicode normalization in selectors, users of selectors-api will be
potentially surprised by the results in certain circumstances
involving denormalized selectors.
I have discussed this with my co-edito
Hi Art,
On Sat, Jan 31, 2009 at 2:18 PM, Arthur Barstow wrote:
> Does the P&C spec include any normative assertions that create a dependency
> on the API & Events spec? I just made a quick scan of the P&C's latest ED
> and I did not find any any such statements.
>
> If there are no such dependenc
Marcos,
On Jan 31, 2009, at 8:31 AM, ext Marcos Caceres wrote:
Ok, fair enough. However, I think the words "such as" does not make
the assertion sound particularly definitive. I think it MUST that
widget engines support the APIs and a SHOULD that they support updates
and sigs.
New text:
"A wi
Hi Art,
On Sat, Jan 31, 2009 at 12:48 PM, Arthur Barstow wrote:
>
> I propose the following changes to the 22 December 2008 P&C LCWD [1]:
>
> 1. As currently written, the spec implies a Widget User Agent must support
> [Widgets-DigSig]. I think that requirement is too strong and must be
> relaxed
I propose the following changes to the 22 December 2008 P&C LCWD [1]:
1. As currently written, the spec implies a Widget User Agent must
support [Widgets-DigSig]. I think that requirement is too strong and
must be relaxed. To address this, change the first paragraph in
Section 3.0 to:
[[
