Re: CfC: publish new WDs of XHR and XHR2; deadline 18 August

Arthur Barstow: > This is a Call for Consensus (CfC) to publish new WDs of the XHR and > XHR2 specs. > > As with all of our CfCs, positive response is preferred and > encouraged and silence will be assumed to be assent. The deadline > for comments is August 18. +1 for publishing. The copyright y

proposal to expose word breaker through JavaScript: range.expand()

I proposed to expand a range to word boundary. Here is the related webkit bug. Below is the spec. Appreciated any feedbacks. *Syntax*: expands the range to the 'unit' boundary. interface Range { void expand(in DOMString uint) } *Parameters*: un

Re: [File API] events vs callbacks

On Thu, Aug 13, 2009 at 11:33 AM, Anne van Kesteren wrote: > On Thu, 13 Aug 2009 19:24:30 +0200, Jonas Sicking wrote: >> Does this match implementations? I'm pretty sure that mozilla's >> implementation supports reading from ftp (as long as it's same-origin >> with the page making the request). Is

Re: [File API] events vs callbacks

On Thu, 13 Aug 2009 19:24:30 +0200, Jonas Sicking wrote: > Does this match implementations? I'm pretty sure that mozilla's > implementation supports reading from ftp (as long as it's same-origin > with the page making the request). Is that not the case with other > implementations? Ah, did not th

Re: Widget Accessibility

Simon, On Aug 13, 2009, at 1:45 PM, ext Simon Harper wrote: As far as I can see, the browser is the (JavaScript+HTML) interpreter, therefore a richer accessibility bridge is required, which will not be addressed by ARIA alone. If you have any specific accessibility-related requirements for an

Re: Widget Accessibility

Hi there Marcos, sorry for the delay in responding - I've been thinking about this... It seems to me that the current aspects of accessibility and notification is built in general for content, yet we are trying to use it in the context of applications. If the Web 'page' is going to presen

Re: [File API] events vs callbacks

On Thu, Aug 13, 2009 at 3:38 AM, Anne van Kesteren wrote: > On Wed, 12 Aug 2009 21:06:38 +0200, Jonas Sicking wrote: >> On Wed, Aug 12, 2009 at 12:01 PM, Anne van Kesteren >> wrote: >>> Because we'd need to define how this works and define that non-GET, >>> non-null send(), setRequestHeader(), etc

Re: CfC: publish new WDs of XHR and XHR2; deadline 18 August

I support this. / Jonas On Thursday, August 13, 2009, Arthur Barstow wrote: > This is a Call for Consensus (CfC) to publish new WDs of the XHR and XHR2 > specs. > > As with all of our CfCs, positive response is preferred and encouraged and > silence will be assumed to be assent. The deadline f

[widgets] Draft Minutes from 13 August 2009 Voice Conf

The draft minutes from the August 13 Widgets voice conference are available at the following and copied below: http://www.w3.org/2009/08/13-wam-minutes.html WG Members - if you have any comments, corrections, etc., please send them to the public-webapps mail list before 20 August 2009 (the

Close ACTION-357

Hi Art, My action http://www.w3.org/2008/webapps/track/actions/357 can be closed. The table that was requested was provided in Widgets 1.0: Window Modes and Media Query Extensions http://dev.w3.org/2006/waf/widgets-wm/Overview.src.html. I didn't do it, but it does meet the original request relat

Re: [P&C] utf8-char in Zip-rel-path

Marcin Hanclik wrote: Hi Marcos, Thanks with remark: 1. deleted the P&C's ABNF definition of utf8-char. OK. 2. added "The utf8-char rule is defined in section 4 of [UTF-8]." I think it needs further refinement, since section 4 of [UTF-8] is for the full range of utf-8, i.e. starting w

RE: [P&C] Low-level internationalization, XML deserialization, IRI or URI, IRI normalization

Hi Marcos, Thanks for your comments. >>Which developers in particular did you have in mind? I meant developers who could develop widgets "by hand", without any automation. (These may the same people as here: http://lists.w3.org/Archives/Public/public-device-apis/2009Apr/0013.html) >>How do you >

Re: [P&C] Low-level internationalization, XML deserialization, IRI or URI, IRI normalization

Marcin Hanclik wrote: Hi Marcos, Thanks for your comments. I think we should ask i18n for guidance. Let's ask them. To Step 7, I've added "If doc is encoded in a format that is unsupported by the user agent, then the user agent must terminate this algorithm and treat this widget package a

RE: [P&C] Low-level internationalization, XML deserialization, IRI or URI, IRI normalization

Hi Marcos, Thanks for your comments. >> I think we should ask i18n for guidance. Let's ask them. >>To Step 7, I've added "If doc is encoded in a format that is >>unsupported by the user agent, then the user agent must terminate this >>algorithm and treat this widget package as an invalid Zip arc

RE: [P&C] utf8-char in Zip-rel-path

Hi Marcos, Thanks with remark: >>1. deleted the P&C's ABNF definition of utf8-char. OK. >>2. added "The utf8-char rule is defined in section 4 of [UTF-8]." I think it needs further refinement, since section 4 of [UTF-8] is for the full range of utf-8, i.e. starting with control characters, AS

Re: DnD vs CnP (was Copy/Paste Events)

Le 13-août-09 à 13:34, Ian Hickson a écrit : So I'm saying is that, regardless of whether you use voice, keyboard, touch or mouse... There are two distinct concepts at play here. I disagree. The drag and drop model allows the user to drag to the clipboard and paste from the clipboard. This is

Re: Copy/Paste Events

(trimmed cc list) On Tue, 4 Aug 2009, Sebastian Markb�ge wrote: > On Mon, Aug 3, 2009 at 1:06 PM, Ian Hickson wrote: > > > > > > It seems that nobody has bothered to implement this part of the spec > > > even when implementing Drag & Drop so it must not make sense. > > > > This part of the spe

Re: [widgets] Test Suite for Packaging and Configuration

On Mon, Aug 10, 2009 at 1:36 PM, Scott Wilson wrote: > > On 10 Aug 2009, at 10:00, Marcos Caceres wrote: >> >> Secondly, although some elements are not exposed as part of A&E (e.g., >> icon and license), there are still conformance requirements as to how >> the user agent is supposed to expose the

Re: CfC: publish new WDs of XHR and XHR2; deadline 18 August

On Aug 13, 2009, at 6:42 AM, Barstow Art (Nokia-CIC/Boston) wrote: This is a Call for Consensus (CfC) to publish new WDs of the XHR and XHR2 specs. As with all of our CfCs, positive response is preferred and encouraged and silence will be assumed to be assent. The deadline for comments is Augus

Re: CfC: publish new WDs of XHR and XHR2; deadline 18 August

On Aug 13, 2009, at 3:42 AM, Arthur Barstow wrote: This is a Call for Consensus (CfC) to publish new WDs of the XHR and XHR2 specs. As with all of our CfCs, positive response is preferred and encouraged and silence will be assumed to be assent. The deadline for comments is August 18. I

CfC: publish new WDs of XHR and XHR2; deadline 18 August

This is a Call for Consensus (CfC) to publish new WDs of the XHR and XHR2 specs. As with all of our CfCs, positive response is preferred and encouraged and silence will be assumed to be assent. The deadline for comments is August 18. -Regards, Art Barstow Begin forwarded message: From

Re: [File API] events vs callbacks

On Wed, 12 Aug 2009 21:06:38 +0200, Jonas Sicking wrote: > On Wed, Aug 12, 2009 at 12:01 PM, Anne van Kesteren > wrote: >> Because we'd need to define how this works and define that non-GET, >> non-null send(), setRequestHeader(), etc. are all not having any effect >> for filedata URLs. That

Re: [File API] feedback on August 1/5 draft

On Thu, 13 Aug 2009 02:02:30 +0200, Arun Ranganathan wrote: > Anne van Kesteren wrote: >> I think [FileData.url] also should only be available on File. > > This would probably be fine, although for filedata: URLs, we don't > *need* a mediaType (we could just define octet stream or something on

Re: RFC: WebApp timing

Hi, Michael, Good point indeed. On Thu, Aug 13, 2009 at 12:49 AM, Michael Nordman wrote: > >> interface Window { > > >> readonly attribute Timing >> >> pageTiming; > > >> }; > > The pageTiming attribute represents t

Re: RFC: WebApp timing

Hi, Gregg, On Thu, Aug 13, 2009 at 12:07 AM, Gregg Tavares wrote: > > > On Wed, Aug 12, 2009 at 6:12 PM, Zhiheng Wang wrote: > >> Hello, >> >>We recently started a draft to provide timing-related APIs in browsers. >> The goal is to add the missing pieces in webapp latency measurements >> us

Re: RFC: WebApp timing

Hi, Bil, On Wed, Aug 12, 2009 at 11:13 PM, Bil Corry wrote: > Zhiheng Wang wrote on 8/12/2009 8:12 PM: > >The first cut of the draft is attached below. It's sketchy but should > > hold much of our ideas. We are > > still actively working on it. Any interest and feedback on the draft are > >

Re: RFC: WebApp timing

interface Window { readonly attribute Timing pageTiming; }; The pageTiming attribute represents the timing information related to the > current top-level browsing context. Each top-level browser context must have > a un

Re: RFC: WebApp timing

On Wed, Aug 12, 2009 at 6:12 PM, Zhiheng Wang wrote: > Hello, > >We recently started a draft to provide timing-related APIs in browsers. > The goal is to add the missing pieces in webapp latency measurements using > Javascript. As a starter, right now we've only include a > minimum set of int