RE: [widgets] Potential bug in Rule for Identifying the Media Type of a File

Hi Marcos, These are my remarks as discussed yesterday on the call. Comment a) 6.A.If all characters in the extension are outside the two ranges, then go to step 5 in this algorithm. Should be 6.A.If any of the characters in the extension is outside the two ranges, then go to step 5 in this

Re: propose an API to return Range in textarea etc. form control nodes (similar functionality as document.caretRangeFromPoint)

(sorry for the spam, send last time using the wrong 'from' email address to the public mailing lists) Hi Maciej: Thanks for your comments. I have a question about interface CaretPosition: In case of form control node, such as textarea, the 'offset' is the character offset within the textarea

Re: propose an API to return Range in textarea etc. form control nodes (similar functionality as document.caretRangeFromPoint)

On Oct 16, 2009, at 10:23 AM, Xiaomei Ji wrote: Hi Maciej: Thanks for your comments. I have a question about interface CaretPosition: In case of form control node, such as textarea, the 'offset' is the character offset within the textarea under mouse, 'offsetKind' is control, what is

DataCache - revised editor's draft available

Hello all, Based on the feedback from WebApps WG [1], I went back and rewrote the draft of the DataCache API to make it possible to benefit from HTML5's AppCache implementations. Here's the latest draft of this API: http://dev.w3.org/2006/webapi/DataCache/ I note that there were several

Re: propose an API to return Range in textarea etc. form control nodes (similar functionality as document.caretRangeFromPoint)

Hi Maciej: Thanks for your quick reply. Then, I have other questions: 1. Why we would like to differentiate whether the node is a 'document' node or a 'control' node? Can such differentiation be achived by existing flags in node instead of offsetKind? 2. If we expose the control node, how to

Re: [ElementTraversal]: Feature string for DOMImplementation.hasFeature(feature, version)?

Hi all, Just thought I'd check again. Has this been discussed or resolved? We're planning on having a Xerces-J release in December and would be nice if we could provide this to users (assuming the spec plans to adopt it). Thanks. Michael Glavassevich XML Parser Development IBM Toronto Lab

Re: Touch and gestures events

Hi, Kari- That's very cool stuff. Thanks for letting us know about that... I hope that if we do indeed standardize multitouch and gesture events, you will lend us your practical experience in specifying them. It's great that you've opened the source on the multitouch stuff... I don't

Re: Touch and gestures events

On Fri, Oct 16, 2009 at 10:46 AM, kari.hiit...@nokia.com wrote: On 10/15/09 21:04, ext João Eiras jo...@opera.com wrote: Hi, I suppose that the interest Olli mentioned was ours (Nokia). Unfortunately there was a long delay before we were able to participate the discussion and release

Re: Touch and gestures events

I am aware that Apple has rotation and scaling. Must these necessarily be coupled to the input device (touch)? Could the rotation/scale be independent of that (much like a contextmenu event is independent of the input device or method that that device triggers it (recall old mac IE, where

Re: [ElementTraversal]: Feature string for DOMImplementation.hasFeature(feature, version)?

Hi, Michael- Sorry for the tardy response. This was an unfortunate oversight. I've now added this to the proposed errata [1]. Please let me know if this suits your needs. [1] http://www.w3.org/2008/12/REC-ElementTraversal-20081222-errata#S1 Regards- -Doug Schepers W3C Team Contact, SVG

[Bug 7938] New: SECURITY_ERR when disallowing Database open is inconsistent with QUOTA_EXCEEDED_ERR for disallowing setItem

http://www.w3.org/Bugs/Public/show_bug.cgi?id=7938 Summary: SECURITY_ERR when disallowing Database open is inconsistent with QUOTA_EXCEEDED_ERR for disallowing setItem Product: WebAppsWG Version: unspecified