WebApps-ACTION-734: Start cfc to publish ui events as a "gutted" wg note

WebApps-ACTION-734: Start cfc to publish ui events as a "gutted" wg note http://www.w3.org/2008/webapps/track/actions/734 Assigned to: Arthur Barstow

WebApps-ACTION-735: Check that the d3e tests are in gh or mercurial, and if needed fix

WebApps-ACTION-735: Check that the d3e tests are in gh or mercurial, and if needed fix http://www.w3.org/2008/webapps/track/actions/735 Assigned to: Travis Leithead

WebApps-ACTION-736: Work with adrian to find a replacement tc for alex and d3e

WebApps-ACTION-736: Work with adrian to find a replacement tc for alex and d3e http://www.w3.org/2008/webapps/track/actions/736 Assigned to: Arthur Barstow

WebApps-ACTION-737: Create a new bugzilla component for inner text

WebApps-ACTION-737: Create a new bugzilla component for inner text http://www.w3.org/2008/webapps/track/actions/737 Assigned to: Arthur Barstow

WebApps-ACTION-738: Start a cfc to publish a "gutted" wg note of the fullscreen api

WebApps-ACTION-738: Start a cfc to publish a "gutted" wg note of the fullscreen api http://www.w3.org/2008/webapps/track/actions/738 Assigned to: Arthur Barstow

WebApps-ACTION-739: Start a cfc to publish a proposed recommendation of idb

WebApps-ACTION-739: Start a cfc to publish a proposed recommendation of idb http://www.w3.org/2008/webapps/track/actions/739 Assigned to: Arthur Barstow

WebApps-ACTION-740: Issue a call for test facilitator for ime spec

WebApps-ACTION-740: Issue a call for test facilitator for ime spec http://www.w3.org/2008/webapps/track/actions/740 Assigned to: Arthur Barstow

WebApps-ACTION-741: Ask cjk interest group and others about ime (use cases, tests, etc.)

WebApps-ACTION-741: Ask cjk interest group and others about ime (use cases, tests, etc.) http://www.w3.org/2008/webapps/track/actions/741 Assigned to: Charles McCathie Nevile

WebApps-ACTION-742: Re sse test results, followup on the timeouts with the 2 test facilitators

WebApps-ACTION-742: Re sse test results, followup on the timeouts with the 2 test facilitators http://www.w3.org/2008/webapps/track/actions/742 Assigned to: Arthur Barstow

WebApps-ACTION-744: Work on moving web idl v1 to rec

WebApps-ACTION-744: Work on moving web idl v1 to rec http://www.w3.org/2008/webapps/track/actions/744 Assigned to: Yves Lafon

WebApps-ACTION-743: Try to find someone to help yves, cam and boris on web idl v1

WebApps-ACTION-743: Try to find someone to help yves, cam and boris on web idl v1 http://www.w3.org/2008/webapps/track/actions/743 Assigned to: Charles McCathie Nevile

WebApps-ACTION-746: Determine kris' availability to work on the web messaging and web sockets implemenation reports

WebApps-ACTION-746: Determine kris' availability to work on the web messaging and web sockets implemenation reports http://www.w3.org/2008/webapps/track/actions/746 Assigned to: Adrian Bateman

WebApps-ACTION-745: Followup with simon re running the web workers tests

WebApps-ACTION-745: Followup with simon re running the web workers tests http://www.w3.org/2008/webapps/track/actions/745 Assigned to: Arthur Barstow

WebApps-ACTION-747: Start a cfc to gut xhr l2 and publish a wg note

WebApps-ACTION-747: Start a cfc to gut xhr l2 and publish a wg note http://www.w3.org/2008/webapps/track/actions/747 Assigned to: Arthur Barstow

WebApps-ACTION-748: Mark file list as feature @ risk

WebApps-ACTION-748: Mark file list as feature @ risk http://www.w3.org/2008/webapps/track/actions/748 Assigned to: Arun Ranganathan

WebApps-ACTION-749: Start a cfc to publish file api lcwd

WebApps-ACTION-749: Start a cfc to publish file api lcwd http://www.w3.org/2008/webapps/track/actions/749 Assigned to: Arthur Barstow

WebApps-ACTION-750: Deleted the uc in file api that starts with "data should be able to be stored ..."

WebApps-ACTION-750: Deleted the uc in file api that starts with "data should be able to be stored ..." http://www.w3.org/2008/webapps/track/actions/750 Assigned to: Arun Ranganathan

WebApps-ACTION-751: Followup with cameron re pr 27 and the web idl test suite

WebApps-ACTION-751: Followup with cameron re pr 27 and the web idl test suite http://www.w3.org/2008/webapps/track/actions/751 Assigned to: Yves Lafon

WebApps-ACTION-752: Do edits on file system spec

WebApps-ACTION-752: Do edits on file system spec http://www.w3.org/2008/webapps/track/actions/752 Assigned to: Arun Ranganathan

WebApps-ACTION-753: Find an msdn page that describes this

WebApps-ACTION-753: Find an msdn page that describes this http://www.w3.org/2008/webapps/track/actions/753 Assigned to: Travis Leithead

WebApps-ACTION-754: Work with doug and chaals re fuzzy pointers stuff for web annotations wg

WebApps-ACTION-754: Work with doug and chaals re fuzzy pointers stuff for web annotations wg http://www.w3.org/2008/webapps/track/actions/754 Assigned to: Frederick Hirsch

WebApps-ACTION-755: Solve the rest of the problems related to robust targeting of changing documents.

WebApps-ACTION-755: Solve the rest of the problems related to robust targeting of changing documents. http://www.w3.org/2008/webapps/track/actions/755 Assigned to: Robin Berjon

WebApps-ACTION-756: Make sure webapps has good communication flow with indieui group re editing

WebApps-ACTION-756: Make sure webapps has good communication flow with indieui group re editing http://www.w3.org/2008/webapps/track/actions/756 Assigned to: Charles McCathie Nevile

WebApps-ACTION-757: Collect the various minutes and make them as coherent as the reality of the meeting.

WebApps-ACTION-757: Collect the various minutes and make them as coherent as the reality of the meeting. http://www.w3.org/2008/webapps/track/actions/757 Assigned to: Charles McCathie Nevile

WebApps-ACTION-758: Ask accesibility people about imes

WebApps-ACTION-758: Ask accesibility people about imes http://www.w3.org/2008/webapps/track/actions/758 Assigned to: Charles McCathie Nevile

ISSUE-187: Https://github.com/w3c/uievents/issues/20

ISSUE-187: Https://github.com/w3c/uievents/issues/20 http://www.w3.org/2008/webapps/track/issues/187 Raised by: On product:

WebApps-ACTION-759: Look into next f2f

WebApps-ACTION-759: Look into next f2f http://www.w3.org/2008/webapps/track/actions/759 Assigned to: Charles McCathie Nevile

ISSUE-117: In Widget P&C Spec, need to clarify in the spec that dir attribute does not apply to attributes that are IRIs, Numeric, Keywords, etc. The dir attribute only affects human readable strings.

ISSUE-117: In Widget P&C Spec, need to clarify in the spec that dir attribute does not apply to attributes that are IRIs, Numeric, Keywords, etc. The dir attribute only affects human readable strings. http://www.w3.org/2008/webapps/track/issues/117 Raised by: On product:

ISSUE-118 (dispatchEvent links): Consider allowing dispatchEvent for generic event duplication for links [DOM3 Events]

ISSUE-118 (dispatchEvent links): Consider allowing dispatchEvent for generic event duplication for links [DOM3 Events] http://www.w3.org/2008/webapps/track/issues/118 Raised by: Doug Schepers On product: DOM3 Events Simon Pieters wrote in

ISSUE-119 (input/keyboard locale): Consider adding input/keyboard locale to text and keyboard events [DOM3 Events]

ISSUE-119 (input/keyboard locale): Consider adding input/keyboard locale to text and keyboard events [DOM3 Events] http://www.w3.org/2008/webapps/track/issues/119 Raised by: Doug Schepers On product: DOM3 Events This is a proposal for a new 'locale' property on the TextEvent and KeyboardEvent

ISSUE-120 (scroll basic event): Consider returning 'scroll' from UIEvent to Event interface [DOM3 Events]

ISSUE-120 (scroll basic event): Consider returning 'scroll' from UIEvent to Event interface [DOM3 Events] http://www.w3.org/2008/webapps/track/issues/120 Raised by: Doug Schepers On product: DOM3 Events 'scroll' was moved from the Event interface to the UIEvent interface, so UIEvents are grou

ISSUE-121 (beforeInput): Consider generalizing the 'textInput' event to cover all user-initiated changes [DOM3 Events]

ISSUE-121 (beforeInput): Consider generalizing the 'textInput' event to cover all user-initiated changes [DOM3 Events] http://www.w3.org/2008/webapps/track/issues/121 Raised by: Doug Schepers On product: DOM3 Events >From by >

ISSUE-122 (add mousewheel): Consider adding 'mousewheel' again [DOM3 Events]

ISSUE-122 (add mousewheel): Consider adding 'mousewheel' again [DOM3 Events] http://www.w3.org/2008/webapps/track/issues/122 Raised by: Doug Schepers On product: DOM3 Events Defining the 'mousewheel' event and interface was an early decision by the group, and this was specified along with the

ISSUE-123 (feature strings): Rationale for feature strings [DOM3 Events]

ISSUE-123 (feature strings): Rationale for feature strings [DOM3 Events] http://www.w3.org/2008/webapps/track/issues/123 Raised by: Doug Schepers On product: DOM3 Events Simon Pieters : [[ What's the use case for extended featur

ISSUE-124 (reword examples): Remove RFC2119 keywords from examples [DOM3 Events]

ISSUE-124 (reword examples): Remove RFC2119 keywords from examples [DOM3 Events] http://www.w3.org/2008/webapps/track/issues/124 Raised by: Doug Schepers On product: DOM3 Events Simon Pieters : [[ RFC2119 keywords in examples is

ISSUE-125 (DOM Views): Consider dropping DOM Views reference for HTML5 defaultView [DOM3 Events]

ISSUE-125 (DOM Views): Consider dropping DOM Views reference for HTML5 defaultView [DOM3 Events] http://www.w3.org/2008/webapps/track/issues/125 Raised by: Doug Schepers On product: DOM3 Events Simon Pieters : [[ { The defaultV

ISSUE-126 (isTrusted): Consider changing 'trusted' to 'isTrusted' [DOM3 Events]

ISSUE-126 (isTrusted): Consider changing 'trusted' to 'isTrusted' [DOM3 Events] http://www.w3.org/2008/webapps/track/issues/126 Raised by: Doug Schepers On product: DOM3 Events Simon Pieters : [[ Gecko has a property called isTr

ISSUE-127 (cancelBubble / srcElement): Consider adding cancelBubble and srcElement [DOM3 Events]

ISSUE-127 (cancelBubble / srcElement): Consider adding cancelBubble and srcElement [DOM3 Events] http://www.w3.org/2008/webapps/track/issues/127 Raised by: Doug Schepers On product: DOM3 Events Simon Pieters : [[ Looking at [6]

ISSUE-128 (preventDefault): Define preventDefault to account for pre-propagation default actions [DOM3 Events]

ISSUE-128 (preventDefault): Define preventDefault to account for pre-propagation default actions [DOM3 Events] http://www.w3.org/2008/webapps/track/issues/128 Raised by: Doug Schepers On product: DOM3 Events Simon Pieters : [[

ISSUE-129 (event constructors): Revist event constructors [DOM3 Events]

ISSUE-129 (event constructors): Revist event constructors [DOM3 Events] http://www.w3.org/2008/webapps/track/issues/129 Raised by: Doug Schepers On product: DOM3 Events Simon Pieters : [[ An idea for creating events is to suppor

ISSUE-130 (Web IDL): Consider using Web IDL for the IDL fragments [DOM3 Events]

ISSUE-130 (Web IDL): Consider using Web IDL for the IDL fragments [DOM3 Events] http://www.w3.org/2008/webapps/track/issues/130 Raised by: Doug Schepers On product: DOM3 Events Simon Pieters : [[ I think this specification shoul

ISSUE-131 (defaultView load ): Define load event to fire on defaultView [DOM3 Events]

ISSUE-131 (defaultView load ): Define load event to fire on defaultView [DOM3 Events] http://www.w3.org/2008/webapps/track/issues/131 Raised by: Doug Schepers On product: DOM3 Events Simon Pieters : [[ { Note: for legacy reason

ISSUE-132 (event.returnValue): Consider adding event.returnValue [DOM3 Events]

ISSUE-132 (event.returnValue): Consider adding event.returnValue [DOM3 Events] http://www.w3.org/2008/webapps/track/issues/132 Raised by: Doug Schepers On product: DOM3 Events Hallvord R. M. Steen : [[ IE lets you prevent the de

ISSUE-133 (keyCode and charCode): Consider specifying keyCode and charCode [DOM3 Events]

ISSUE-133 (keyCode and charCode): Consider specifying keyCode and charCode [DOM3 Events] http://www.w3.org/2008/webapps/track/issues/133 Raised by: Doug Schepers On product: DOM3 Events Simon Pieters : [[ Please specify keyCode

ISSUE-134 (optional useCapture): Consider making useCapture parameter of add/removeEventListener optional [DOM3 Events]

ISSUE-134 (optional useCapture): Consider making useCapture parameter of add/removeEventListener optional [DOM3 Events] http://www.w3.org/2008/webapps/track/issues/134 Raised by: Doug Schepers On product: DOM3 Events Sergey Ilinsky

ISSUE-135 (DOMAttributeChangeRequestEvent): Consider adding DOMAttributeChangeRequestEvent

ISSUE-135 (DOMAttributeChangeRequestEvent): Consider adding DOMAttributeChangeRequestEvent http://www.w3.org/2008/webapps/track/issues/135 Raised by: Doug Schepers On product: James Craig : [[ The following proposal is for cons

ISSUE-136 (getCoordsAt): Consider adding MouseEvent.getCoordsAt(element)

ISSUE-136 (getCoordsAt): Consider adding MouseEvent.getCoordsAt(element) http://www.w3.org/2008/webapps/track/issues/136 Raised by: Doug Schepers On product: Jonathan Watt : [[ Background: Positioning elements based off the po

ISSUE-137 (IME-keypress): Should keypress events fire when using an IME? [DOM3 Events]

ISSUE-137 (IME-keypress): Should keypress events fire when using an IME? [DOM3 Events] http://www.w3.org/2008/webapps/track/issues/137 Raised by: Doug Schepers On product: DOM3 Events Hallvord R. M. Steen : [[ current spec text

ISSUE-138 (keyboard mapping): Define "keyboard mapping" [DOM3 Events]

ISSUE-138 (keyboard mapping): Define "keyboard mapping" [DOM3 Events] http://www.w3.org/2008/webapps/track/issues/138 Raised by: Doug Schepers On product: DOM3 Events Hallvord R. M. Steen : [[ what exactly does the spec mean whe

ISSUE-139 (clarify key repeat): Define which events repeat when a key is held down [DOM3 Events]

ISSUE-139 (clarify key repeat): Define which events repeat when a key is held down [DOM3 Events] http://www.w3.org/2008/webapps/track/issues/139 Raised by: Doug Schepers On product: DOM3 Events Hallvord R. M. Steen : [[ spec cu

ISSUE-140 (textInput keydown keypress): textInput event as default action of both keydown and keypress? [DOM3 Events]

ISSUE-140 (textInput keydown keypress): textInput event as default action of both keydown and keypress? [DOM3 Events] http://www.w3.org/2008/webapps/track/issues/140 Raised by: Doug Schepers On product: DOM3 Events Hallvord R. M. Steen

ISSUE-141 (IME examples): IME examples [DOM3 Events]

ISSUE-141 (IME examples): IME examples [DOM3 Events] http://www.w3.org/2008/webapps/track/issues/141 Raised by: Doug Schepers On product: DOM3 Events Hallvord R. M. Steen : [[ In the text about Input Method Editors [1], the exam

ISSUE-142 (multiple keypress): one keydown might fire multiple keypress/textInput events [DOM3 Events]

ISSUE-142 (multiple keypress): one keydown might fire multiple keypress/textInput events [DOM3 Events] http://www.w3.org/2008/webapps/track/issues/142 Raised by: Doug Schepers On product: DOM3 Events Hallvord R. M. Steen : [[ S

ISSUE-143 (editorial d3e): DOM3 Events section 3 editorial errors [DOM3 Events]

ISSUE-143 (editorial d3e): DOM3 Events section 3 editorial errors [DOM3 Events] http://www.w3.org/2008/webapps/track/issues/143 Raised by: Doug Schepers On product: DOM3 Events Daniel Barclay : [[ In reading the Document Obje

ISSUE-144 (propagation exceptions): exceptions in handlers during event propagation [DOM3 Events]

ISSUE-144 (propagation exceptions): exceptions in handlers during event propagation [DOM3 Events] http://www.w3.org/2008/webapps/track/issues/144 Raised by: Doug Schepers On product: DOM3 Events Sergey Ilinsky in : [[ How do ex

ISSUE-145 (event handler ordering): Ordering event handlers registered by different means [DOM3 Events]

ISSUE-145 (event handler ordering): Ordering event handlers registered by different means [DOM3 Events] http://www.w3.org/2008/webapps/track/issues/145 Raised by: Doug Schepers On product: DOM3 Events Sergey Ilinsky in : [[ Has

ISSUE-146 (capture-phase targets): Capture-phase listeners invoked on targets [DOM3 Events]

ISSUE-146 (capture-phase targets): Capture-phase listeners invoked on targets [DOM3 Events] http://www.w3.org/2008/webapps/track/issues/146 Raised by: Doug Schepers On product: DOM3 Events Sergey Ilinsky in : [[ As far as I kno

ISSUE-147 (event re-dispatching): re-dispatching an event that already has its flow started [DOM3 Events]

ISSUE-147 (event re-dispatching): re-dispatching an event that already has its flow started [DOM3 Events] http://www.w3.org/2008/webapps/track/issues/147 Raised by: Doug Schepers On product: DOM3 Events Sergey Ilinsky in : [[ I

ISSUE-148 (modularize d3e): Consider modularizing DOM3 Events [DOM3 Events]

ISSUE-148 (modularize d3e): Consider modularizing DOM3 Events [DOM3 Events] http://www.w3.org/2008/webapps/track/issues/148 Raised by: Doug Schepers On product: DOM3 Events Garrett Smith in : [[ I think we're all well aware of t

ISSUE-149 (missing key values): The multiply and other key values are missing [DOM3 Events]

ISSUE-149 (missing key values): The multiply and other key values are missing [DOM3 Events] http://www.w3.org/2008/webapps/track/issues/149 Raised by: Doug Schepers On product: DOM3 Events Travis Leithead : [[ During implementa

ISSUE-150: [widgets] Email and param name and value as 'Keyword attributes' is causing confusion in Widgets P&C Spec

ISSUE-150: [widgets] Email and param name and value as 'Keyword attributes' is causing confusion in Widgets P&C Spec http://www.w3.org/2008/webapps/track/issues/150 Raised by: On product:

ISSUE-151: [widgets] P&C Spec.... If feature-name is not a valid IRI, and required-feature is true, then the user agent must treat this widget as an invalid widget package. but doesnt say anything abo

ISSUE-151: [widgets] P&C Spec If feature-name is not a valid IRI, and required-feature is true, then the user agent must treat this widget as an invalid widget package. but doesnt say anything about the case when it is not required. http://www.w3.org/2008/webapps/track/issues/151 Raised b

ISSUE-152: [widgets] P&C test suite needs a few more XML entity cases to check for well-formed XML

ISSUE-152: [widgets] P&C test suite needs a few more XML entity cases to check for well-formed XML http://www.w3.org/2008/webapps/track/issues/152 Raised by: On product:

ISSUE-173 (ericu): terminal FileWriter progress events should be queued [File API: Writer]

ISSUE-173 (ericu): terminal FileWriter progress events should be queued [File API: Writer] http://www.w3.org/2008/webapps/track/issues/173 Raised by: Eric Uhrhane On product: File API: Writer When a FileWriter successfully completes a write, currently it: * dispatches a write event * sets read

WebApps-ISSUE-179 (DOMException): DOM Core uses INVALID_STATE_ERR (DOMException) where D3E uses DISPATCH_REQUEST_ERR (EventException)

WebApps-ISSUE-179 (DOMException): DOM Core uses INVALID_STATE_ERR (DOMException) where D3E uses DISPATCH_REQUEST_ERR (EventException) http://www.w3.org/2008/webapps/track/issues/179 Raised by: Jacob Rossi On product: DOM Core uses INVALID_STATE_ERR (DOMException) where D3E uses DISPATCH_REQU

WebApps-ISSUE-181 (FileError-Name): Use case for FileError and FileException name attribute [File API]

WebApps-ISSUE-181 (FileError-Name): Use case for FileError and FileException name attribute [File API] http://www.w3.org/2008/webapps/track/issues/181 Raised by: Adrian Bateman On product: File API FileError [1] and FileException [2] both define a DOMString attribute called name that contains

WebApps-ISSUE-182 (OperationNotAllowed): File API introduces a new OperationNotAllowed exception where other specs have an error code [File API]

WebApps-ISSUE-182 (OperationNotAllowed): File API introduces a new OperationNotAllowed exception where other specs have an error code [File API] http://www.w3.org/2008/webapps/track/issues/182 Raised by: Adrian Bateman On product: File API The File API adds an OperationNotAllowed exception wit

ISSUE-2 (OnFoo Attributes): Event Handler Attributes (onfoo Attributes) and Add/Remove Event Listener [DOM3 Events]

ISSUE-2 (OnFoo Attributes): Event Handler Attributes (onfoo Attributes) and Add/Remove Event Listener [DOM3 Events] http://www.w3.org/2008/webapps/track/issues/ Raised by: Doug Schepers On product: DOM3 Events Should Event Handler attributes (so-called 'onfoo attributes') be exposed in the A

ISSUE-3 (eventType): [Progress] eventType [Progress events]

ISSUE-3 (eventType): [Progress] eventType [Progress events] http://www.w3.org/2008/webapps/track/issues/ Raised by: Olli Pettay On product: Progress events Shouldn't there be an eventType so you can use document.createEvent to make these? See http://www.w3.org/mid/[EMAIL PROTECTED]

ISSUE-4 (SpecContent): Should specifications decide what counts as content for transfer? [Progress Events]

ISSUE-4 (SpecContent): Should specifications decide what counts as content for transfer? [Progress Events] http://www.w3.org/2008/webapps/track/issues/ Raised by: Charles McCathieNevile On product: Progress Events Currently the spec says that the bytes counted for total/loaded are exclusive o

ISSUE-5 (Unexpanded Entities): Wording for the Treatment of Unexpanded Entity References and Entity Replacement Markup [Element Traversal]

ISSUE-5 (Unexpanded Entities): Wording for the Treatment of Unexpanded Entity References and Entity Replacement Markup [Element Traversal] http://www.w3.org/2008/webapps/track/issues/ Raised by: Doug Schepers On product: Element Traversal In

ISSUE-6 (Element Traversal Nodelist): Should the ElementTraversal Interface Have a Nodelist? [Element Traversal]

ISSUE-6 (Element Traversal Nodelist): Should the ElementTraversal Interface Have a Nodelist? [Element Traversal] http://www.w3.org/2008/webapps/track/issues/ Raised by: Doug Schepers On product: Element Traversal Daniel Glazman requested that a nodelist or item accessor be added to the ET spe

ISSUE-7 (Transfer Old Issues): Transferring old WebAPI and WAF [All Products]

ISSUE-7 (Transfer Old Issues): Transferring old WebAPI and WAF [All Products] http://www.w3.org/2008/webapps/track/issues/ Raised by: Doug Schepers On product: All Products Should We transfer old issues from WebAPI and WAF to this Tracker?

ISSUE-8 (mouseenter/leave): Adding mouseenter and mouseleave Events [DOM3 Events]

ISSUE-8 (mouseenter/leave): Adding mouseenter and mouseleave Events [DOM3 Events] http://www.w3.org/2008/webapps/track/issues/ Raised by: Doug Schepers On product: DOM3 Events 'mouseenter' and 'mouseleave' events are similar to 'mouseover' and 'mouseout' events, but do not bubble. Should we

ISSUE-9 (Wheeling Units): How should wheel events represent pixel/line wheeling units? [DOM3 Events]

ISSUE-9 (Wheeling Units): How should wheel events represent pixel/line wheeling units? [DOM3 Events] http://www.w3.org/2008/webapps/track/issues/ Raised by: Doug Schepers On product: DOM3 Events Olli Pettay raised an issue about there being different types of wheeling/scrolling units; perhaps

ISSUE-10 (client-server): Client and Server model [Access Control]

ISSUE-10 (client-server): Client and Server model [Access Control] http://www.w3.org/2008/webapps/track/issues/ Raised by: Arthur Barstow On product: Access Control [[ This issue was created on 2008-01-04 as Issue #20 in the Web Applications Formats (WAF) WG and is copied in totality to the We

ISSUE-11 (security-model): What is the Security Model for the access-control spec? [Access Control]

ISSUE-11 (security-model): What is the Security Model for the access-control spec? [Access Control] http://www.w3.org/2008/webapps/track/issues/ Raised by: Arthur Barstow On product: Access Control [[ This issue was created on 2008-01-15 as Issue #21 in the Web Applications Formats (WAF) WG a

ISSUE-12 (access-control-policy-path): IIS and Access-Control-Policy-Path [Access Control]

ISSUE-12 (access-control-policy-path): IIS and Access-Control-Policy-Path [Access Control] http://www.w3.org/2008/webapps/track/issues/ Raised by: Anne van Kesteren On product: Access Control [[ This issue was created on 2008-06-06 as Issue #25 in the Web Applications Formats (WAF) WG and is

ISSUE-13 (opting-into-cookies): Opting into cookies [Access Control]

ISSUE-13 (opting-into-cookies): Opting into cookies [Access Control] http://www.w3.org/2008/webapps/track/issues/ Raised by: Anne van Kesteren On product: Access Control [[ This issue was created on 2008-06-06 as Issue #26 in the Web Applications Formats (WAF) WG and is copied in totality to t

ISSUE-14 (opt-into-methods-headers): Opting into methods/headers [Access Control]

ISSUE-14 (opt-into-methods-headers): Opting into methods/headers [Access Control] http://www.w3.org/2008/webapps/track/issues/ Raised by: Anne van Kesteren On product: Access Control [[ This issue was created on 2008-06-06 as Issue #27 in the Web Applications Formats (WAF) WG and is copied in

ISSUE-17: Widgets (not just widget engines) should be able to specify which proxies they communicate through

ISSUE-17: Widgets (not just widget engines) should be able to specify which proxies they communicate through http://www.w3.org/2008/webapps/track/issues/ Raised by: Josh Soref On product: From: http://lists.w3.org/Archives/Public/public-webapps/2008AprJun/0440.html > 5:00 PM and as a should

ISSUE-18 (api-availability): Need to efine a mechanism to check for the availability of an API [Widgets]

ISSUE-18 (api-availability): Need to efine a mechanism to check for the availability of an API [Widgets] http://www.w3.org/2008/webapps/track/issues/ Raised by: Marcos Caceres On product: Widgets This issue was first

ISSUE-19: Widgets digital Signatures spec does not meet required use cases and requirements [Widgets]

ISSUE-19: Widgets digital Signatures spec does not meet required use cases and requirements [Widgets] http://www.w3.org/2008/webapps/track/issues/ Raised by: Marcos Caceres On product: Widgets R11. Digital Signature A conforming specification must specify a means to digitally sign resources i

ISSUE-20 (Content multi-view): Current model does not allow multiple views [Widgets]

ISSUE-20 (Content multi-view): Current model does not allow multiple views [Widgets] http://www.w3.org/2008/webapps/track/issues/ Raised by: Marcos Caceres On product: Widgets The problem with the way that is currently specified is that it does not allow for multiple "views" of content. For

ISSUE-21: should Widgets 1.0 allow fallback for element? [Widgets]

ISSUE-21: should Widgets 1.0 allow fallback for element? [Widgets] http://www.w3.org/2008/webapps/track/issues/ Raised by: Marcos Caceres On product: Widgets Currently, only one element is allowed in a configuration document. This means that authors can't point to alternative representations

ISSUE-22 (Is SHA1 good enough?): Is sha1 as a DigestMethod strong enough for Widgets digital signatures?

ISSUE-22 (Is SHA1 good enough?): Is sha1 as a DigestMethod strong enough for Widgets digital signatures? http://www.w3.org/2008/webapps/track/issues/ Raised by: Josh Soref On product: The widgets 1.0: Digital Signature specification currently mandates that the DigestValue be calculated using

ISSUE-23 (Key Indentifier Case): Should Key Identifiers prioritize uppercase characters [DOM3 Events]

ISSUE-23 (Key Indentifier Case): Should Key Identifiers prioritize uppercase characters [DOM3 Events] http://www.w3.org/2008/webapps/track/issues/ Raised by: Doug Schepers On product: DOM3 Events In the current draft of Key Identifiers, including the new algorithm wording, there is a bias tow

ISSUE-24 (Allow List Scope): Which headers should be allowed in the Allow List? [Access Control]

ISSUE-24 (Allow List Scope): Which headers should be allowed in the Allow List? [Access Control] http://www.w3.org/2008/webapps/track/issues/ Raised by: Doug Schepers On product: Access Control What is the full range of headers that should be allowed in AC? What is the process to add them?

ISSUE-34: What happens when one runs out of storage space when decompressing a widget? [Widgets]

ISSUE-34: What happens when one runs out of storage space when decompressing a widget? [Widgets] http://www.w3.org/2008/webapps/track/issues/ Raised by: Josh Soref On product: Widgets When extracting the file data from a file entry, there is a chance that the storage device may run out of sp

ISSUE-35: SVG as an icon format. [Widgets]

ISSUE-35: SVG as an icon format. [Widgets] http://www.w3.org/2008/webapps/track/issues/ Raised by: Marcos Caceres On product: Widgets Unsure as to how SVG is going to work as an icon format in regards to interactivity (eg. input events, javascript, animation, network connections, etc)?

ISSUE-36: Is the file API going to be part of Widgets 1.0? [Widgets]

ISSUE-36: Is the file API going to be part of Widgets 1.0? [Widgets] http://www.w3.org/2008/webapps/track/issues/ Raised by: Marcos Caceres On product: Widgets A few months ago Opera proposed a fileIO API for standardization [1]. It was discussed that widgets could make use of this API. The i

ISSUE-37: [Progress] Use unsigned long long for .loaded and .total

ISSUE-37: [Progress] Use unsigned long long for .loaded and .total http://www.w3.org/2008/webapps/track/issues/ Raised by: Olli Pettay On product: Since Progress Events is used also for , unsigned long long would be better than unsigned long. http://lists.w3.org/Archives/Public/public-webapp

ISSUE-38: DOM 3 Events abort/error bubble, ProgressEvent abort/error do not [Progress Events]

ISSUE-38: DOM 3 Events abort/error bubble, ProgressEvent abort/error do not [Progress Events] http://www.w3.org/2008/webapps/track/issues/ Raised by: Philip Jägenstedt On product: Progress Events The DOM 3 abort/error events (http://www.w3.org/TR/DOM-Level-3-Events/events.html) bubble, while

ISSUE-39 (Mutate Mutations): Consider Changing Ordering of DOM3 Events [DOM3 Events]

ISSUE-39 (Mutate Mutations): Consider Changing Ordering of DOM3 Events [DOM3 Events] http://www.w3.org/2008/webapps/track/issues/ Raised by: Doug Schepers On product: DOM3 Events >From http://lists.w3.org/Archives/Public/public-webapps/2008JulSep/0146.html : "Currently, the spec says, "Many s

ISSUE-41 (New Non-NS Event Methods): Should all event methods have namespaced and non-namespaced equivalents?

ISSUE-41 (New Non-NS Event Methods): Should all event methods have namespaced and non-namespaced equivalents? http://www.w3.org/2008/webapps/track/issues/41 Raised by: Doug Schepers On product: >From Olli Pettay in >http://lists.w3.org/Archives/Public/public-webapps/2008JulSep/0260.html: [[

ISSUE-42 (simpler custom events): Should we simplify custom events? [DOM3 Events]

ISSUE-42 (simpler custom events): Should we simplify custom events? [DOM3 Events] http://www.w3.org/2008/webapps/track/issues/42 Raised by: Doug Schepers On product: DOM3 Events >From Cameron McCormack in >http://lists.w3.org/Archives/Public/www-svg/2005Oct/0005.html: I'd like to make anothe

ISSUE-43 (FireEvents): When should the events defined by DOM3 Events fire? [DOM3 Events]

ISSUE-43 (FireEvents): When should the events defined by DOM3 Events fire? [DOM3 Events] http://www.w3.org/2008/webapps/track/issues/43 Raised by: Ian Hickson On product: DOM3 Events Right now DOM3 Events describes a lot of events, like click and dblclick and so on, but doesn't actually have

ISSUE-44 (EventsAndWindow): Should DOM3 Events cover the interaction of events and the Window object? [DOM3 Events]

ISSUE-44 (EventsAndWindow): Should DOM3 Events cover the interaction of events and the Window object? [DOM3 Events] http://www.w3.org/2008/webapps/track/issues/44 Raised by: Ian Hickson On product: DOM3 Events We need to decide whether HTML5 or DOM3 Events (or another spec) defines how events

ISSUE-45 (Extensible metadata): Do we need an extensible metadata hook? [Widgets]

ISSUE-45 (Extensible metadata): Do we need an extensible metadata hook? [Widgets] http://www.w3.org/2008/webapps/track/issues/45 Raised by: Marcos Caceres On product: Widgets Krzysztof Maczyński recommended that we need some kind of generic extensible metadata hook. If there a use case for s

ISSUE-46 (i18n Span-Like Element): Need to define a for i18n purposes in configuration document [Widgets]

ISSUE-46 (i18n Span-Like Element): Need to define a for i18n purposes in configuration document [Widgets] http://www.w3.org/2008/webapps/track/issues/46 Raised by: Marcos Caceres On product: Widgets We need an element that can be used generically inside other elements in the Configuration Do

  1   2   >