public-webapi@w3.org from February 2006 by subject

<?access-control?> allows privelege escalation attacks with many embedding mechanisms

[DOM3 Events]: boolean readonly attributes as methods

[DOM3 Events]: Current UA extensions to the Event interface

[DOM3 Events]: Use cases for new features?

[REX] Inserting comments?

[REX] no move operation ?

[REX] Non conformant example

[REX] Repeated IDs in a REX message

[REX]: Name "Remote Events for XML" is misleading

[REX]: REX Requirements does not seem like a requirements document

ACTION-87: Selectors API

Asymptotic computational complexity bounds for DOM methods

Back Button

Comments on "Authorizing Read Access to XML Content Using the <?access-control?> Processing Instruction 1.0"

ISSUE-27: Where can you use null

ISSUE-28: Can we make focus/blur more generic

ISSUE-29: how is uri parameter of the open() method resolved

ISSUE-30: mousewheel event

ISSUE-31: invalid bytes and default character encoding

ISSUE-32: Accessibility and UI events - how to improve the interaction

ISSUE-33: Multiple devices generating events

ISSUE-34: XHR: Should synchronous loading call onstatechange

Namespaces in Xpath expressions

Public access to WebAPI documents and issues

Question about charter (was Re: Window object)

Question from Web APIs WG on connecting multiple devices and multipoints touchscreen devices

REX and XUP

REX typo 1.1.2

Safe copy and paste with scripts

Sandboxed consideration ?

stopImmediatePropagation() use case

Super rough draft of Window spec

Targeted Cross-Document Scripting

typo in REX requirements?

Window object, very rough cut of proposed content for first version of spec

Working Group members

XMPP API

Last message date: Tuesday, 28 February 2006 23:56:23 UTC