[cors] Comments on 17 March 2009
Re: http://dev.w3.org/2006/waf/widgets/#reserved-file-and-folder-names
[WebIDL] grammar in ABNF
[webstorage] deleting a database
Widgets PAG seeks feedback on Widget Updates spec
[WebStorage] Property enumeration and checking presence
A+E todo
RE: [widgets] P&C LC#2 comment regarding icons
[widgets] P&C comments, 8
An import statement for Web IDL
- Re: An import statement for Web IDL
- Fw: An import statement for Web IDL
- Re: An import statement for Web IDL
Specs using Web IDL
Belated Regretts for telcon.
[widgets] Draft Minutes from 25 June 2009 Voice Conference
AppCache to Widget Converter
[widgets] dig sig RelaxNG schema
[WebIDL] Callback, PropertyOnly, NoInterfaceObject
[widgets] Draft Agenda for 25 June 2009 Voice Conference
- Leaving WebApps (was RE: [widgets] Draft Agenda for 25 June 2009 Voice Conference)
- Re: [widgets] Draft Agenda for 25 June 2009 Voice Conference
[cors] TAG request concerning CORS & Next Step(s)
- Re: [cors] TAG request concerning CORS & Next Step(s)
- Re: [cors] TAG request concerning CORS & Next Step(s)
Re: Why I don't attend the weekly teleconference (Was: Input on the agenda)
- Re: Why I don't attend the weekly teleconference (Was: Input on the agenda)
- dev.w3.org CVS access [was: Why I don't attend the weekly teleconference]
- Points of order on this WG
- Re: Points of order on this WG
- Re: Points of order on this WG
- Re: Points of order on this WG
- Re: Points of order on this WG
- Re: Points of order on this WG
- Re: Points of order on this WG
- Re: Points of order on this WG
- Re: Points of order on this WG
- Re: Points of order on this WG
- Re: Points of order on this WG
- Re: Points of order on this WG
- Re: Points of order on this WG
- Re: Points of order on this WG
- Berkeley DB license (was Re: Points of order on this WG)
- Re: Berkeley DB license (was Re: Points of order on this WG)
- Re: Berkeley DB license (was Re: Points of order on this WG)
- Re: Berkeley DB license (was Re: Points of order on this WG)
- Re: Berkeley DB license (was Re: Points of order on this WG)
- Re: Berkeley DB license (was Re: Points of order on this WG)
- Re: Berkeley DB license (was Re: Points of order on this WG)
- Re: Points of order on this WG
Request for comments: Delivery Context Ontology Last Call; Deadline 7 Aug 2009
[widgets] [preference element] question on the value attribute
- Re: [widgets] [preference element] question on the value attribute
- Re: [widgets] [preference element] question on the value attribute
Alpha Widget checker
[XHR] XMLHttpRequest name
Widgets 1.0: Packaging and Configuration questions
Re: [selectors-api] Names of querySelector() and querySelectorAll() methods
Rationale for using a relational database with SQL
Handling too few arguments in method calls
- Re: Handling too few arguments in method calls
- Re: Handling too few arguments in method calls
- Re: Handling too few arguments in method calls
Widgets 1.0: Packaging and Configuration LCWD review
Re: [selectors-api] Return value of lookupNamespaceURI
Re: [PrototypeRoot]
Input events, checkboxes and radio buttons
Re: [bindings] Regarding the algorithm of 4.2.2. Interface prototype object
Re: [Bindings] [[Delete]], hidden operations, missing arguments
Web IDL syntax
"W3C and APIs" writeup from TAG members
July 2008 f2f meeting minutes now publicly accessible
File API Feedback
- Re: File API Feedback
widgets spec
widgets feedback
widgets feedback
Request for Comments: FPWD of Widgets 1.0: Access Requests Policy spec
Request for Comments: FPWD of Widgets 1.0: URI Scheme spec
- Re: Request for Comments: FPWD of Widgets 1.0: URI Scheme spec
- Re: Request for Comments: FPWD of Widgets 1.0: URI Scheme spec
[widgets] Draft Minutes from 18 June 2009 Voice Conference
widgets feedback
widgets feedback
Fwd: Chat with Marcos Caceres
[widgets] RE: P&C Last Call comments 1..7+
Touch and gestures events
Dated URI for "Widgets 1.0: URI Scheme" seems to be broken
[P&C] Definitions: installation, instantiation
Regrets for Thrusday's Widgets call /eom
[widgets] P&C Last Call Period
[selectors-api] Transitioning to CR
- Re: [selectors-api] Transitioning to CR
- Re: [selectors-api] Transitioning to CR
[widgets] Draft Agenda for 18 June 2009 Voice Conference
[widgets] conformance requirements review
'scroll' and 'resize' events
Re: [WebIDL] On overloaded operations in an effective overload set
ISSUE-91: Origin and redirects [CORS]
[cors] origin and redirects
ISSUE-90: Exposing more (~infinite) response headers [CORS]
New WD of Use Cases and Requirements for Ontology and API for Media Object 1.0
Re: Restricting API access
[cors] Web application
[widgets] Last Call Comments
Window atttributes for timing info
[widgets] Comments on Widgets 1.0: Packaging and configuration, 9.1 Processing rules
File API - W3C Working Draft 7 June 2009
ISSUE-89: Reduce the length of the header names? [CORS]
Public call for prior art on Widget updates
Comments on Widgets spec
[widgets] Draft Minutes from 11 June 2009 f2f meeting
[widgets] Draft Minutes from 10 June 2009 f2f meeting
[widgets] Draft Minutes from 9 June 2009 f2f meeting
File API, Editor's Draft II
[widgets] Step 7 - Process the Configuration Document
[WebIDL] double
[WebIDL] double
[widgets] Elements are grouped by language:
[widgets] One element is allowed per language:
[widgets] Verify Zip archive
[widgets] Rule for Determining if a potential Zip archive is a Zip archive
[widgets] Rule for Identifying the media type of a file
[widgets] Rule for Identifying the Media Type of an Image
[widgets] Rule for Parsing a Non-negative Integer
[widgets] Rule for Getting Text Content with Normalized White Space
[widgets] Rule for Getting Text Content
[widgets] editorial style
[widgets] Rule for getting a single attribute value
[widgets] Rule for finding a file within a widget package
[widgets] Rule for dealing with an invalid Zip archive
[widgets] Rule for extracting file data from a file entry
[widgets] Editorial: 9x Processing
Redirect and Origin
Questions on A&E spec
[webstorage] Ambiguous Requirement for Key Ordering
[WebIDL] overloading and fallback
Review of widget access request
WebSocket question
Response to ACTION-348
XHR without user credentials (Was: Origin enables XSS to escalate to XSRF (was: security issue with XMLHttpRequest API compatibility))
- Re: XHR without user credentials
- Re: XHR without user credentials
- Re: XHR without user credentials
- Re: XHR without user credentials
- Re: XHR without user credentials
- Re: XHR without user credentials
- Re: XHR without user credentials
- Re: XHR without user credentials
- Re: XHR without user credentials
- Re: XHR without user credentials
- Re: XHR without user credentials
- XHR and sandboxed iframes (was: Re: XHR without user credentials)
- Re: XHR and sandboxed iframes (was: Re: XHR without user credentials)
- Re: XHR and sandboxed iframes (was: Re: XHR without user credentials)
- Re: XHR and sandboxed iframes (was: Re: XHR without user credentials)
- Re: XHR and sandboxed iframes
- Re: XHR without user credentials
- Re: XHR and sandboxed iframes (was: Re: XHR without user credentials)
- Re: XHR and sandboxed iframes (was: Re: XHR without user credentials)
- Re: XHR and sandboxed iframes (was: Re: XHR without user credentials)
- Re: XHR and sandboxed iframes (was: Re: XHR without user credentials)
- Re: XHR and sandboxed iframes (was: Re: XHR without user credentials)
- Re: XHR and sandboxed iframes (was: Re: XHR without user credentials)
- Re: XHR and sandboxed iframes (was: Re: XHR without user credentials)
- Re: XHR and sandboxed iframes (was: Re: XHR without user credentials)
- Re: XHR and sandboxed iframes (was: Re: XHR without user credentials)
- Re: XHR and sandboxed iframes (was: Re: XHR without user credentials)
- Re: XHR and sandboxed iframes (was: Re: XHR without user credentials)
- Re: XHR and sandboxed iframes (was: Re: XHR without user credentials)
- Re: XHR and sandboxed iframes (was: Re: XHR without user credentials)
- Re: XHR and sandboxed iframes (was: Re: XHR without user credentials)
- Re: XHR and sandboxed iframes (was: Re: XHR without user credentials)
- Re: XHR and sandboxed iframes (was: Re: XHR without user credentials)
- Re: XHR and sandboxed iframes (was: Re: XHR without user credentials)
- Re: XHR and sandboxed iframes
- Re: XHR without user credentials
- Re: XHR without user credentials
- Re: XHR without user credentials
- Re: XHR without user credentials
- Re: XHR without user credentials
- Re: XHR without user credentials
- Re: XHR without user credentials
- Re: XHR without user credentials
- Re: XHR without user credentials
- Re: XHR without user credentials
- Re: XHR without user credentials
CSRF: alternative solutions
Next DOM3 Events Telcon (Time and Day?)
Fwd: [widgets] P&C LC#2 comment regarding icons
New draft of Widgets: Access Requests Policy
Automated API specification generation
[widgets] Draft Minutes from 4 June 2009 Voice Conference
Widgets 1.0: Digital Signatures
- Re: Widgets 1.0: Digital Signatures
- Re: Widgets 1.0: Digital Signatures
- Re: Widgets 1.0: Digital Signatures
[DOM3Events] Use cases for Mutation Events
- Re: [DOM3Events] Use cases for Mutation Events
- Re: [DOM3Events] Use cases for Mutation Events
- Re: [DOM3Events] Use cases for Mutation Events
- RE: [DOM3Events] Use cases for Mutation Events
- to www-dom Re: [DOM3Events] Use cases for Mutation Events
- to www-dom Re: [DOM3Events] Use cases for Mutation Events
Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
- Re: Mutation events replacement
Origin enables XSS to escalate to XSRF (was: security issue with XMLHttpRequest API compatibility)
- Re: Origin enables XSS to escalate to XSRF (was: security issue with XMLHttpRequest API compatibility)
- Re: Origin enables XSS to escalate to XSRF (was: security issue with XMLHttpRequest API compatibility)
- Re: Origin enables XSS to escalate to XSRF (was: security issue with XMLHttpRequest API compatibility)
- Re: Origin enables XSS to escalate to XSRF (was: security issue with XMLHttpRequest API compatibility)
- Re: Origin enables XSS to escalate to XSRF (was: security issue with XMLHttpRequest API compatibility)
- Re: Origin enables XSS to escalate to XSRF (was: security issue with XMLHttpRequest API compatibility)
- Re: Origin enables XSS to escalate to XSRF (was: security issue with XMLHttpRequest API compatibility)
- Re: Origin enables XSS to escalate to XSRF (was: security issue with XMLHttpRequest API compatibility)
- Re: Origin enables XSS to escalate to XSRF (was: security issue with XMLHttpRequest API compatibility)
- Re: Origin enables XSS to escalate to XSRF (was: security issue with XMLHttpRequest API compatibility)
- Re: Origin enables XSS to escalate to XSRF (was: security issue with XMLHttpRequest API compatibility)
- Re: Origin enables XSS to escalate to XSRF (was: security issue with XMLHttpRequest API compatibility)
- Re: Origin enables XSS to escalate to XSRF (was: security issue with XMLHttpRequest API compatibility)
- Re: Origin enables XSS to escalate to XSRF
- Re: Origin enables XSS to escalate to XSRF (was: security issue with XMLHttpRequest API compatibility)
- Re: Origin enables XSS to escalate to XSRF (was: security issue with XMLHttpRequest API compatibility)
- Re: Origin enables XSS to escalate to XSRF (was: security issue with XMLHttpRequest API compatibility)
- Re: Origin enables XSS to escalate to XSRF (was: security issue with XMLHttpRequest API compatibility)
- Re: Origin enables XSS to escalate to XSRF (was: security issue with XMLHttpRequest API compatibility)
- Re: Origin enables XSS to escalate to XSRF (was: security issue with XMLHttpRequest API compatibility)
Attempt at consensus on the <access> model
[widgets] P&C Last Call comments, viewmodes, referencing other specs, guarantee of consistency
- Re: [widgets] P&C Last Call comments, viewmodes, referencing other specs, guarantee of consistency
- RE: [widgets] P&C Last Call comments, viewmodes, referencing other specs, guarantee of consistency
- Re: [widgets] P&C Last Call comments, viewmodes, referencing other specs, guarantee of consistency
[widgets] Draft Agenda for 4 June 2009 Voice Conference
[widgets] P&C LC, general comments
[widgets] P&C LC comments on I18N/L10N
"send data using the Web Socket" and UCS-2
[widgets] P&C Last Call comments, 7
Re: XBL2 Status?
[widgets] P&C Last Call comments, 6
[widgets] Moving Widgets 1.0: Digital Signature spec to Candidate Recommendation
- RE: [widgets] Moving Widgets 1.0: Digital Signature spec to Candidate Recommendation
- Re: [widgets] Moving Widgets 1.0: Digital Signature spec to Candidate Recommendation
[widgets] Please include a statement of purpose and user interaction expectations for <feature>
- Re: [widgets] Please include a statement of purpose and user interaction expectations for <feature>
- Re: [widgets] Please include a statement of purpose and user interaction expectations for <feature>
[widgets] What does it mean to have an unavailable API
- Re: [widgets] What does it mean to have an unavailable API
- Re: [widgets] What does it mean to have an unavailable API
- RE: [widgets] What does it mean to have an unavailable API
- Re: [widgets] What does it mean to have an unavailable API
- Re: [widgets] What does it mean to have an unavailable API
- RE: [widgets] What does it mean to have an unavailable API
- Re: [widgets] What does it mean to have an unavailable API
Re: [ElementTraversal]: Feature string for DOMImplementation.hasFeature(feature, version)?
[widgets] Purpose and utility of <feature> unclear
London F2F invitation
[widgets] P&C Last Call comments, 5
[widgets] P&C Last Call comments, zip-rel-path ABNF
[widgets] P&C Last Call comments, versioning
- Re: [widgets] P&C Last Call comments, versioning
[widgets] P&C Last Call comments, interoperability
- Re: [widgets] P&C Last Call comments, interoperability
[widgets] P&C Last Call comments, 4
[widgets] P&C Last Call comments, 3
[widgets] P&C Last Call comments, 2
[widgets] P&C Last Call comments, 1
[widgets] P&C Last Call comments, 0
[widgets] Implementing Google Wave with W3C Widgets
Feature names: Typo in example
[widgets] A&E test widget
[WebIDL] "module" in ECMAScript
[cors] Review
- Re: [cors] Review
- Re: [cors] Review
- Re: [cors] Review
- Re: [cors] Review
- Re: [cors] Review
- Re: [cors] Review
- Re: [cors] Review
- Re: [cors] Review
- Re: [cors] Review
- Re: [cors] Review
- Re: [cors] Review
- Re: [cors] Review
- Re: [cors] Review
- Re: [cors] Review
- Re: [cors] Review
- Re: [cors] Review
- Re: [cors] Review
- Re: [cors] Review
- Re: [cors] Review
- Re: [cors] Review
BONDI Approved Release 1.0
Request For Comments: Last Call WD of Widgets 1.0: Packaging and Configuration; deadline 19 June 2009
[widgets] Draft Minutes from 28 May 2009 Voice Conference
Re: [widgets] Regrets for 28 May 2009 Voice Conference
[DOM L3] Telecon today?
[widgets] Packaging call for review
[widgets] Public keys in widgets URI scheme?
- Re: [widgets] Public keys in widgets URI scheme?
- Re: [widgets] Public keys in widgets URI scheme?
- Re: [widgets] Public keys in widgets URI scheme?
[widgets] Draft Agenda for 28 May 2009 Voice Conference
- Re: [widgets] Draft Agenda for 28 May 2009 Voice Conference
- Re: [widgets] Draft Agenda for 28 May 2009 Voice Conference
Introduction: Peter-Paul Koch
[DOML3Events] keydown repeatedness
[widgets] Open in Browser?
Introduction: Rob Ennals from Intel
[webworkers] Tasks
EventSource editorial issues
[widgets] Access Requests Use Case: Restricted access to remote web services using white/black lists
[widgets] Widgets URI scheme... it's baaaack!
- Re: [widgets] Widgets URI scheme... it's baaaack!
- Re: [widgets] Widgets URI scheme... it's baaaack!
[widgets] Draft Minutes from 21 May 2009 Voice Conference
More complete draft for Widgets: Access Requests
- Re: More complete draft for Widgets: Access Requests
- Re: More complete draft for Widgets: Access Requests
- Re: More complete draft for Widgets: Access Requests
- [widgets] Call for Input: Use Cases and Requirements for Widgets Access Request spec
- Re: More complete draft for Widgets: Access Requests
- Re: More complete draft for Widgets: Access Requests
[widgets] P&C and window modes
FPWD for WAR?
[widgets] Declaring *W*A*R*
[widgets] Draft Agenda for 21 May 2009 Voice Conference
[widgets] Draft Minutes from 19 May 2009 Widgets Security VC
[widget] Security model
[widgets] Draft Agenda for 19 May 2009 Widgets Security VC
[widgets] Draft Minutes from 18 May 2009 Widgets Security VC
[admin] Documenting some of WebApps' Work Modes
[widgets] Security Model call on May 18 @ 13:00 Paris time
[widgets] Draft Minutes from 14 May 2009 Voice Conference
[widgets] Agenda for 14 May 2009 Voice Conference
- Re: [widgets] Agenda for 14 May 2009 Voice Conference
- Re: [widgets] Agenda for 14 May 2009 Voice Conference
- RE: [widgets] Agenda for 14 May 2009 Voice Conference
[widgets] Getting A&E spec to Last Call
[widgets] <access> element processing
Require that XPathNSResolver be implemented on Node
[widgets] window modes in P&C, was Re: Small question about latest version of "P&C specs" (11th Mar 2009)
- RE: [widgets] window modes in P&C, was Re: Small question about latestversion of "P&C specs" (11th Mar 2009)
- Re: [widgets] window modes in P&C, was Re: Small question about latestversion of "P&C specs" (11th Mar 2009)
FW: Patent licensing and avoiding late Exclusions of Essential Claims in the WebApps WG
- Re: FW: Patent licensing and avoiding late Exclusions of Essential Claims in the WebApps WG
- Re: FW: Patent licensing and avoiding late Exclusions of Essential Claims in the WebApps WG
[widgets] Draft minutes from 7 May 2009 Voice Conference
[widgets-digsig] minor editorial update
[widgets] i18n feedback
[widgets] P&C to do list
[widgets] Draft Agenda for 7 May 2009 Voice Conference
Working Vacation
Re: Next steps for XHR L1 spec?
Re: XHR and the storage mutex
setTimeout() in HTML5
ACTION-337: Review of access element
LCWD of Widgets 1.0: Digital Signatures published 30-Apr-2009
- Reminder: Comments for LCWD of Widgets 1.0: Digital Signatures due June 1
- RE: Reminder: Comments for LCWD of Widgets 1.0: Digital Signatures due June 1
- Re: Reminder: Comments for LCWD of Widgets 1.0: Digital Signatures due June 1
- Re: Reminder: Comments for LCWD of Widgets 1.0: Digital Signatures due June 1
- RE: Reminder: Comments for LCWD of Widgets 1.0: Digital Signatures due June 1
[widget-digsig] XML Signature Properties published
I18N proposals document review...
[widgets] Draft Minutes from 30 April 2009 Voice Conference
Widget instances and widget invocations
- Re: Widget instances and widget invocations
- Re: Widget instances and widget invocations
- Re: Widget instances and widget invocations
[widgets] Comments to <access> element text
[webidl] XMLHttpRequest interface object
Regretts Telecon Thursday 30 April
[widgets] dig sig and requirements ready for pub!
- Re: [widgets] dig sig and requirements ready for pub!
- Re: [widgets] dig sig and requirements ready for pub!
- Re: [widgets] dig sig and requirements ready for pub!
- Re: [widgets] dig sig and requirements ready for pub!
Widget URI ED
Preferences for the I18N model
[widgets] Requirements doc overhaul
[widgets] Draft Agenda for 30 April 2009 Voice Conference
I18N issue: case-sensitivity of locale subdirectories
- Re: I18N issue: case-sensitivity of locale subdirectories
- Re: I18N issue: case-sensitivity of locale subdirectories
- Re: I18N issue: case-sensitivity of locale subdirectories
[widget-digsig] Update to widget signature
[webidl] Callback confusion
[widgets] Dig Sig review in prep for LC
[NameCreator] definition buggy
Updates to Widget Signature
Storage 'length' and enumeration
- Re: Storage 'length' and enumeration
- Re: Storage 'length' and enumeration
- Re: Storage 'length' and enumeration
- Re: Storage 'length' and enumeration
- Re: Storage 'length' and enumeration
- Re: Storage 'length' and enumeration
- Re: Storage 'length' and enumeration
- Re: Storage 'length' and enumeration
- Re: Storage 'length' and enumeration
- Re: Storage 'length' and enumeration
- Re: Storage 'length' and enumeration
- Re: Storage 'length' and enumeration
- Re: Storage 'length' and enumeration
- Re: Storage 'length' and enumeration
- Re: Storage 'length' and enumeration
- Re: Storage 'length' and enumeration
- Re: Storage 'length' and enumeration
- Re: Storage 'length' and enumeration
[webstorage] disk space
[widgets] Publishing LCWD of Widgets Digital Signatures and new WD of Requirements
Proposal to update signature text in Packaging and Config, remove from Widget Signature
[webidl] definition of const string literal
[widgets] Identifying all security related issues with "core" Widgets specs
[webstorage] inactive documents
Re: DOM3 Events call today/tonight?
RE: [DOML3Events] ACTION-267 Proposal for event iterator
- RE: [DOML3Events] ACTION-267 Proposal for event iterator
Proposal for addition to WebStorage
- Re: Proposal for addition to WebStorage
- Re: Proposal for addition to WebStorage
- Re: Proposal for addition to WebStorage
[webstorage] storage event should be dispatched async
Fwd: [whatwg] Exposing EventTarget to JavaScript
addEventListener naming
[webstorage] events
[webstorage] fork bombing
Re: [Proposal] Empowering the Widget to ask fro "mode change" in A&E
[widget-digsig] Updated Widget Signature editors draft
Fwd: Proposal for new WG to specify "Concrete APIs"
Storage and widgets
[widgets] Proposal to Close: ISSUE-81: ECDSAwithSHA256 as required algorithm in place of DSAwithSHA256?
[widgets] Draft Minutes from 23 April 2003 Voice Conference
[widgets] <access> element
[widget-digsig] updated Widget Signature editors draft
Re: Small question about latest version of "P&C specs" (11th Mar 2009)
Re: Progress Events normative text
Re: [cors] Redirects
[widgets] Agenda for 23 April 2009 Voice Conference
agenda request: security considerations for access
Proposal for ISSUE-83
[webidl] DOMString
Re: [widgets] Screenshots and case sensitive file names
Re: [widgets] restrictions on XML base
Re: [Widgets] Widget Gallery RSS like sharing format
Re: [widgets] Base folder and resolution of relative paths
two-player game application
Widgets unconference at WWW 2009
[widgets] i18n proposals document
- Re: [widgets] i18n proposals document
- RE: [widgets] i18n proposals document
- Re: [widgets] i18n proposals document
- Re: [widgets] i18n proposals document
[widgets] Draft Minutes from 16 April 2009 Widgets Voice Conference
New Widgets A&E Editors Draft
Using xhr with file://
review of A&E
[widgets] dropping screenshot
[Widgets A&E] Removing show() and hide()
June F2F
[widget] [widget-digsig] Comment on WD of Widgets 1.0: Digital Signatures - use of Created property
Re: [Selectors] Selectors to Proposed Rec - call for consensus
New CfC Re: [Selectors API] Call for Consensus - approve John Resig's tests
[widgets] Agenda for 16 April 2009 Voice Conference
FYI: chartering discussion re security policy for APIs
Re: Simple approach for <access>
[widgets] Jar signing vs. XML signatures
- Re: [widgets] Jar signing vs. XML signatures
- Re: [widgets] Jar signing vs. XML signatures
- Re: [widgets] Jar signing vs. XML signatures
Re: Next steps for CORS?
HTML5 Origin (aka IETF Origin draft)
[Fwd: Re: Web Storage & SQL]
[widgets] blog post on recent Dig Sig spec
HTML 5 Database Storage Does Not Enable Chaining Transactions
- Re: HTML 5 Database Storage Does Not Enable Chaining Transactions
- Re: HTML 5 Database Storage Does Not Enable Chaining Transactions
Web Storage & SQL
- Re: Web Storage & SQL
- Re: Web Storage & SQL
- Re: Web Storage & SQL
Reminder: DOM3 Events Telcon Canceled
Re: Reminder: January 31 comment deadline for LCWD of Widgets 1.0: Packaging & Configuration spec
[widget-digsig] Pls review: Additional considerations on elliptic curve algorithms to consider
- RE: [widget-digsig] Pls review: Additional considerations on elliptic curve algorithms to consider
Content Security Policy - Updated Spec
[widgets] Synching Widgets DigSig with XML Signatures 1.1 and Signatures Properties
[webstorage] readTransaction clarification
[cors] security issue with XMLHttpRequest API compatibility
- Re: [cors] security issue with XMLHttpRequest API compatibility
- Re: [cors] security issue with XMLHttpRequest API compatibility
- Re: [cors] security issue with XMLHttpRequest API compatibility
- Re: [cors] security issue with XMLHttpRequest API compatibility
- Re: [cors] security issue with XMLHttpRequest API compatibility
- Re: [cors] security issue with XMLHttpRequest API compatibility
- Re: [cors] security issue with XMLHttpRequest API compatibility
- Re: [cors] security issue with XMLHttpRequest API compatibility
- Re: [cors] security issue with XMLHttpRequest API compatibility
- Re: [cors] security issue with XMLHttpRequest API compatibility
- Re: [cors] security issue with XMLHttpRequest API compatibility
- Re: [cors] security issue with XMLHttpRequest API compatibility
- Re: [cors] security issue with XMLHttpRequest API compatibility
- Re: [cors] security issue with XMLHttpRequest API compatibility
- Re: [cors] security issue with XMLHttpRequest API compatibility
- Re: [cors] security issue with XMLHttpRequest API compatibility
- Re: [cors] security issue with XMLHttpRequest API compatibility
- Re: [cors] security issue with XMLHttpRequest API compatibility
- Re: [cors] security issue with XMLHttpRequest API compatibility
- Re: [cors] security issue with XMLHttpRequest API compatibility
- Re: [cors] security issue with XMLHttpRequest API compatibility
- Re: [cors] security issue with XMLHttpRequest API compatibility
[widgets] remove update related methods form A&E
- Re: [widgets] remove update related methods form A&E
- Re: [widgets] remove update related methods form A&E
[widgets] dropping Asynchronous HTTP Requests and Storage
- Re: [widgets] dropping Asynchronous HTTP Requests and Storage
- Re: [widgets] dropping Asynchronous HTTP Requests and Storage
CORS for file-based web apps
Request for Review: Cross-Origin Resource Sharing
Re: Widgets 1.0 Packaging and Configuration: I18N comments...
- RE: Widgets 1.0 Packaging and Configuration: I18N comments...
[widgets] Zip endian issue?
[widgets] <update> element
Re: Widget Packaging and configuration LC review
Re: Do we need to rename the Origin header?
- Re: Do we need to rename the Origin header?
- Re: Do we need to rename the Origin header?
- Re: Do we need to rename the Origin header?
- Re: Do we need to rename the Origin header?
RE: ISSUE-83 (digsig should not be read at runtime): Instantiated widget should not be able to read digital signature [Widgets]
- Re: ISSUE-83 (digsig should not be read at runtime): Instantiated widget should not be able to read digital signature [Widgets]
- RE: ISSUE-83 (digsig should not be read at runtime): Instantiated widget should not be able to read digital signature [Widgets]
- Re: ISSUE-83 (digsig should not be read at runtime): Instantiated widget should not be able to read digital signature [Widgets]
- RE: ISSUE-83 (digsig should not be read at runtime): Instantiated widget should not be able to read digital signature [Widgets]
- Re: ISSUE-83 (digsig should not be read at runtime): Instantiated widget should not be able to read digital signature [Widgets]
- Re: ISSUE-83 (digsig should not be read at runtime): Instantiated widget should not be able to read digital signature [Widgets]
- Re: ISSUE-83 (digsig should not be read at runtime): Instantiated widget should not be able to read digital signature [Widgets]
- Re: ISSUE-83 (digsig should not be read at runtime): Instantiated widget should not be able to read digital signature [Widgets]
- Re: ISSUE-83 (digsig should not be read at runtime): Instantiated widget should not be able to read digital signature [Widgets]
- Re: ISSUE-83 (digsig should not be read at runtime): Instantiated widget should not be able to read digital signature [Widgets]
- Re: ISSUE-83 (digsig should not be read at runtime): Instantiated widget should not be able to read digital signature [Widgets]
- Re: ISSUE-83 (digsig should not be read at runtime): Instantiated widget should not be able to read digital signature [Widgets]
- RE: ISSUE-83 (digsig should not be read at runtime): Instantiated widget should not be able to read digital signature [Widgets]
- Re: ISSUE-83 (digsig should not be read at runtime): Instantiated widget should not be able to read digital signature [Widgets]
- RE: ISSUE-83 (digsig should not be read at runtime): Instantiated widget should not be able to read digital signature [Widgets]
[widgets] New WD of Widgets 1.0: Digital Signatures spec published on March 31
- RE: [widgets] New WD of Widgets 1.0: Digital Signatures spec published on March 31
- Re: [widgets] New WD of Widgets 1.0: Digital Signatures spec published on March 31
- Re: [widgets] New WD of Widgets 1.0: Digital Signatures spec published on March 31
[widgets] Draft Minutes from 2 April 2009 Voice Conference
Request for FPWD publication of Server-Sent Events, Web Sockets API, Web Storage, and Web Workers
- Re: Request for FPWD publication of Server-Sent Events, Web Sockets API, Web Storage, and Web Workers
- CfC: FPWD of Server-Sent Events, Web Sockets API, Web Storage, and Web Workers; deadline April 10
- Re: CfC: FPWD of Server-Sent Events, Web Sockets API, Web Storage, and Web Workers; deadline April 10
- Re: CfC: FPWD of Server-Sent Events, Web Sockets API, Web Storage, and Web Workers; deadline April 10
- Re: CfC: FPWD of Server-Sent Events, Web Sockets API, Web Storage, and Web Workers; deadline April 10
- Re: CfC: FPWD of Server-Sent Events, Web Sockets API, Web Storage, and Web Workers; deadline April 10
- Re: CfC: FPWD of Server-Sent Events, Web Sockets API, Web Storage, and Web Workers; deadline April 10
- Re: CfC: FPWD of Server-Sent Events, Web Sockets API, Web Storage, and Web Workers; deadline April 10
- Re: CfC: FPWD of Server-Sent Events, Web Sockets API, Web Storage, and Web Workers; deadline April 10
- Re: CfC: FPWD of Server-Sent Events, Web Sockets API, Web Storage, and Web Workers; deadline April 10
- Re: CfC: FPWD of Server-Sent Events, Web Sockets API, Web Storage, and Web Workers; deadline April 10
- Web Storage Scope and Charter (was: CfC: FPWD of Server-Sent Events, Web Sockets API, Web Storage, and Web Workers; deadline April 10)
- Re: Web Storage Scope and Charter (was: CfC: FPWD of Server-Sent Events, Web Sockets API, Web Storage, and Web Workers; deadline April 10)
- Re: Web Storage Scope and Charter
- Re: Web Storage Scope and Charter
- Re: Web Storage Scope and Charter
- Re: Web Storage Scope and Charter
- Re: Web Storage Scope and Charter
- Re: CfC: FPWD of Server-Sent Events, Web Sockets API, Web Storage, and Web Workers; deadline April 10
- Re: CfC: FPWD of Server-Sent Events, Web Sockets API, Web Storage, and Web Workers; deadline April 10
- Re: Web Storage Scope and Charter
- Re: Web Storage Scope and Charter
- Re: Web Storage Scope and Charter
- Re: CfC: FPWD of Server-Sent Events, Web Sockets API, Web Storage, and Web Workers; deadline April 10
- Re: Web Storage Scope and Charter
- Re: CfC: FPWD of Server-Sent Events, Web Sockets API, Web Storage, and Web Workers; deadline April 10
- Re: Web Storage Scope and Charter (was: CfC: FPWD of Server-Sent Events, Web Sockets API, Web Storage, and Web Workers; deadline April 10)
- Re: Web Storage Scope and Charter (was: CfC: FPWD of Server-Sent Events, Web Sockets API, Web Storage, and Web Workers; deadline April 10)
- Re: Web Storage Scope and Charter (was: CfC: FPWD of Server-Sent Events, Web Sockets API, Web Storage, and Web Workers; deadline April 10)
- Re: Web Storage Scope and Charter
- Re: Web Storage Scope and Charter
- Re: Web Storage Scope and Charter
- Re: CfC: FPWD of Server-Sent Events, Web Sockets API, Web Storage, and Web Workers; deadline April 10
- Re: CfC: FPWD of Server-Sent Events, Web Sockets API, Web Storage, and Web Workers; deadline April 10