HTML Media Capture draft from Device APIs and Policy Working Group

Hello WebApps WG, The Device APIs and Policy Working Group has published a new draft called HTML Media Capture on which we think we'll need to coordinate with your group: http://www.w3.org/TR/2010/WD-html-media-capture-20100720/ That document defines a mechanism to bind an input type=file

[Bug 10211] New: Remove the no host-specific component requirement for targetOrigin, see implementor discussion in http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2010-July/027136.html and su

http://www.w3.org/Bugs/Public/show_bug.cgi?id=10211 Summary: Remove the no host-specific component requirement for targetOrigin, see implementor discussion in http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/20

[Bug 10213] The definition of absolute url makes https:foo not an absolute url, since its behavior depends on whether the base is https: or not. Is that desired? In particular, using this defini

http://www.w3.org/Bugs/Public/show_bug.cgi?id=10213 Simon Pieters sim...@opera.com changed: What|Removed |Added CC||public-webapps@w3.org

[CORS] What constitutes a network error?

Hi All, There are a lot of algorithms in the CORS spec that contains steps like: If there is a network error do X However I haven't been able to find a clear definition of what counts as a network error. Does this include successful HTTP requests that return 4xx or 5xx status codes? Or just

Re: New draft of FileSystem API posted

Hi Eric, Thanks for brushing up the draft. We had some internal discussion about the API details and came up with a question regarding is{File,Directory} attributes of Entry interface. It seems like user agent needs to be able to tell if a given entry is file or directory synchronously (or from