[IME] WebIDL bugs

Hi, I spotted a few bugs in the WebIDL fragments of the Input Method Editor API draft [1]that I'm reporting below. I'm happy to bring the required changes directly to the draft if that's preferred. -- interface HTMLElement … Object getInputContext (); }; should be partial i

[Bug 17303] New: Fix editorial issues from Tobie

https://www.w3.org/Bugs/Public/show_bug.cgi?id=17303 Summary: Fix editorial issues from Tobie Product: WebAppsWG Version: unspecified Platform: PC OS/Version: All Status: NEW Severity: normal Priority: P2 C

Re: [IndexedDB] Normative content arguably informative in IndexedDB LC draft

Thanks for finding this. I filed https://www.w3.org/Bugs/Public/show_bug.cgi?id=17303 / Jonas On Wed, May 30, 2012 at 10:17 AM, Tobie Langel wrote: > Hi, > > Section 6 (Privacy) and 7 (Authorization) of the IndexedDB LC draft[1] > feel very informative, yet they're not marked as such. > > Is the

[Bug 17262] send function should have async interface

https://www.w3.org/Bugs/Public/show_bug.cgi?id=17262 Takashi Toyoshima changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|INVALI

Re: [admin] Mail List Policy, Usage, Etiquette, etc. & Top-posting

On 30/05/2012 00:56, Julian Reschke wrote: > On 2012-05-29 16:53, Glenn Maynard wrote: >> On Tue, May 29, 2012 at 9:22 AM, Arthur Barstow > > wrote: >> >> * Messages should be encoded usingplain text >> >> >> >> No,

Re: Feedback on Quota Management API

On 6/1/12 12:07 PM, "Kinuko Yasuda" wrote: > Makes sense, ok let's keep it. Then we will have symmetric four >methods, request and query for each type. Following up on the conversation on Quota Management API and the recent changes which were agreed upon, I'm wondering whether we shouldn't also

Re: Feedback on Quota Management API

On Mon, Jun 4, 2012 at 11:01 AM, Tobie Langel wrote: > Finally, I feel it's slightly misleading to have an interface called > "info" which enables changes (through `requestQuota`). Wouldn't "settings" > or similar be more appropriate? As in: > >    navigator.persistentStorageSettings.queryUsageAnd

Re: Feedback on Quota Management API

On 6/4/12 11:17 AM, "Anne van Kesteren" wrote: >On Mon, Jun 4, 2012 at 11:01 AM, Tobie Langel wrote: >> Finally, I feel it's slightly misleading to have an interface called >> "info" which enables changes (through `requestQuota`). Wouldn't >>"settings" >> or similar be more appropriate? As in: >

Re: [manifest] Is the Webapp Manifest spec ready for FPWD?

On 6/2/12 6:54 AM, "Fabrice Desre" wrote: >On 06/01/2012 02:36 PM, Tobie Langel wrote: >> On Jun 1, 2012, at 9:58 PM, "Marcos Caceres" > > wrote: >> >>> Sounds good. AFAICT, Moz's proposal doesn't really cover packaging >>> either ... Not in the sense of wrapping the app

Standards for Web applications on mobile devices: May 2012 updates

Hi all, The time of my quarterly release of “Standards for Web Applications on Mobile” has come again; the May 2012 edition of the document is now available at: http://www.w3.org/2012/05/mobile-web-app-state/ It also incorporates all the changes that have taken place on the various relevant specs

Re: [manifest] Is the Webapp Manifest spec ready for FPWD?

On Fri, Jun 1, 2012 at 12:40 PM, Marcos Caceres wrote: > > > On 1 Jun 2012, at 18:18, Adam Barth wrote: > > > On Fri, Jun 1, 2012 at 6:43 AM, Marcos Caceres wrote: > >> On 31 May 2012, at 23:23, Adam Barth wrote: > >>> Is anyone besides Mozilla interested in implementing this > specification?

[Bug 17306] New: The initial value of timestamp is not defined

https://www.w3.org/Bugs/Public/show_bug.cgi?id=17306 Summary: The initial value of timestamp is not defined Product: WebAppsWG Version: unspecified Platform: PC OS/Version: Linux Status: NEW Severity: normal Priorit

[Bug 17308] New: Gamepad.id should be DOMString, not string

https://www.w3.org/Bugs/Public/show_bug.cgi?id=17308 Summary: Gamepad.id should be DOMString, not string Product: WebAppsWG Version: unspecified Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority:

[Bug 17307] New: Investigate if double[] should be used for axes and buttons

https://www.w3.org/Bugs/Public/show_bug.cgi?id=17307 Summary: Investigate if double[] should be used for axes and buttons Product: WebAppsWG Version: unspecified Platform: PC OS/Version: Linux Status: NEW

[Bug 17309] New: It is not defined what the value of Gamepad.index should be after disconnecting the gamepad

https://www.w3.org/Bugs/Public/show_bug.cgi?id=17309 Summary: It is not defined what the value of Gamepad.index should be after disconnecting the gamepad Product: WebAppsWG Version: unspecified Platform: PC OS/Version: Linux

[Bug 17310] New: The target of gamepad(dis)connected events is not defined

https://www.w3.org/Bugs/Public/show_bug.cgi?id=17310 Summary: The target of gamepad(dis)connected events is not defined Product: WebAppsWG Version: unspecified Platform: PC OS/Version: Linux Status: NEW Se

[Bug 17311] New: The dictionary for GamepadEvent's ctor isn't defined

https://www.w3.org/Bugs/Public/show_bug.cgi?id=17311 Summary: The dictionary for GamepadEvent's ctor isn't defined Product: WebAppsWG Version: unspecified Platform: PC OS/Version: Linux Status: NEW Severity: normal

Re: [manifest] Is the Webapp Manifest spec ready for FPWD?

On 6/4/12 6:41 PM, "Fabrice Desre" wrote: >Hi Tobie, > >On 06/04/2012 03:03 AM, Tobie Langel wrote: >> On 6/2/12 6:54 AM, "Fabrice Desré" wrote: >>> We're working on pre-loading the appcache at install time when the >>> appcache path is specified in the manifest. See >>> https://bugzilla.mozilla

Re: [manifest] Is the Webapp Manifest spec ready for FPWD?

On 6/4/12 9:16 PM, "Fabrice Desre" wrote: >On 06/04/2012 10:38 AM, Tobie Langel wrote: >> On 6/4/12 6:41 PM, "Fabrice Desre" wrote: >> >>> Hi Tobie, >>> >>> On 06/04/2012 03:03 AM, Tobie Langel wrote: On 6/2/12 6:54 AM, "Fabrice Desré" wrote: > We're working on pre-loading the appcac

[Bug 17308] Gamepad.id should be DOMString, not string

https://www.w3.org/Bugs/Public/show_bug.cgi?id=17308 Ted Mielczarek [:ted] changed: What|Removed |Added Status|NEW |RESOLVED Resolution|

[Bug 17307] Investigate if double[] should be used for axes and buttons

https://www.w3.org/Bugs/Public/show_bug.cgi?id=17307 Ted Mielczarek [:ted] changed: What|Removed |Added Status|NEW |RESOLVED Resolution|

Re: [whatwg] Fullscreen events dispatched to elements

On Jun 1, 2012, at 6:45 PM, Chris Pearce wrote: > Because we exit fullscreen when the fullscreen element is removed from the > document, so if you dispatch events to the context element, the > "fullscreenchange" event never bubbles up to the containing document in the > exit-on-remove case. A

Re: [webcomponents] HTML Parsing and the element

On Wed, 4 Apr 2012, Rafael Weinstein wrote: > On Mon, Apr 2, 2012 at 3:21 PM, Dimitri Glazkov wrote: > > > > Perhaps lost among other updates was the fact that I've gotten the > > first draft of HTML Templates spec out: > > > > http://dvcs.w3.org/hg/webcomponents/raw-file/tip/spec/templates/index

Re: [webcomponents] HTML Parsing and the element

On Mon, Jun 4, 2012 at 2:42 PM, Ian Hickson wrote: > On Wed, 4 Apr 2012, Rafael Weinstein wrote: >> On Mon, Apr 2, 2012 at 3:21 PM, Dimitri Glazkov >> wrote: >> > >> > Perhaps lost among other updates was the fact that I've gotten the >> > first draft of HTML Templates spec out: >> > >> > http:/

Re: Proposal: Document.parse() [AKA: Implied Context Parsing]

On Fri, 25 May 2012, Rafael Weinstein wrote: > > Now's the time to raise objections to UA's adding support for this > feature. For the record, I very much object to Document.parse(). I think it's a terrible API. We should IMHO resolve the use case of "generate a DOM tree from script" using a mu

Re: [webcomponents] HTML Parsing and the element

On Mon, 4 Jun 2012, Tab Atkins Jr. wrote: > > > > [...] We could do this by having the parser insert a fake node into > > the stack of open elements just for this purpose, I think. That is, > > when switching insertion mode in response to the first start tag > > inside the template insertion mod

Re: Proposal: Document.parse() [AKA: Implied Context Parsing]

Just to be clear: what you are objecting to is the addition of formal API for this. You're generally supportive of adding a element whose contents would parse the way we're discussing here -- and given that, a webdev could trivially polyfil Document.parse(). I.e. you're ok with the approach of t

Re: [webcomponents] HTML Parsing and the element

On Mon, Jun 4, 2012 at 3:50 PM, Ian Hickson wrote: > On Mon, 4 Jun 2012, Tab Atkins Jr. wrote: >> > >> > [...] We could do this by having the parser insert a fake node into >> > the stack of open elements just for this purpose, I think. That is, >> > when switching insertion mode in response to th

Re: Proposal: Document.parse() [AKA: Implied Context Parsing]

On Mon, 4 Jun 2012, Rafael Weinstein wrote: > > Just to be clear: what you are objecting to is the addition of formal > API for this. > > You're generally supportive of adding a element whose > contents would parse the way we're discussing here -- and given that, a > webdev could trivially pol

Re: Proposal: Document.parse() [AKA: Implied Context Parsing]

On Mon, Jun 4, 2012 at 4:38 PM, Ian Hickson wrote: > On Mon, 4 Jun 2012, Rafael Weinstein wrote: >> >> Just to be clear: what you are objecting to is the addition of formal >> API for this. >> >> You're generally supportive of adding a element whose >> contents would parse the way we're discussin

Re: [whatwg] Fullscreen events dispatched to elements

On Tue, Jun 5, 2012 at 9:13 AM, Jer Noble wrote: > On Jun 1, 2012, at 6:45 PM, Chris Pearce wrote: > > > Because we exit fullscreen when the fullscreen element is removed from > the document, so if you dispatch events to the context element, the > "fullscreenchange" event never bubbles up to the

Re: [whatwg] Fullscreen events dispatched to elements

On Jun 4, 2012, at 10:43 PM, Robert O'Callahan wrote: > On Tue, Jun 5, 2012 at 9:13 AM, Jer Noble wrote: > On Jun 1, 2012, at 6:45 PM, Chris Pearce wrote: > > > Because we exit fullscreen when the fullscreen element is removed from the > > document, so if you dispatch events to the context e

Re: [whatwg] Fullscreen events dispatched to elements

On Tue, Jun 5, 2012 at 5:57 PM, Jer Noble wrote: > > Actually, in WebKit, we explicitly also message the document from which > the element was removed in that case. I don't see why this behavior > couldn't be standardized. > > > > Did you inform the spec editor(s) when you decided to make this c

Re: [whatwg] Fullscreen events dispatched to elements

On Jun 4, 2012, at 11:23 PM, Robert O'Callahan wrote: > If you implemented that proposal as-is then authors would usually need a > listener on the document as well as the element, and as Chris pointed out, > it's simpler to just always listen on the document. > > Is that true for the Webkit i