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
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
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 to...@fb.com wrote:
Hi,
Section 6 (Privacy) and 7 (Authorization) of the IndexedDB LC draft[1]
feel very informative, yet they're not marked as such.
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17262
Takashi Toyoshima toyos...@chromium.org changed:
What|Removed |Added
Status|RESOLVED|REOPENED
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 art.bars...@nokia.com
mailto:art.bars...@nokia.com wrote:
* Messages should be encoded usingplain text
http://en.wikipedia.org/wiki/Plain_text
On 6/1/12 12:07 PM, Kinuko Yasuda kin...@chromium.org 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
On Mon, Jun 4, 2012 at 11:01 AM, Tobie Langel to...@fb.com 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:
On 6/4/12 11:17 AM, Anne van Kesteren ann...@annevk.nl wrote:
On Mon, Jun 4, 2012 at 11:01 AM, Tobie Langel to...@fb.com 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
On 6/2/12 6:54 AM, Fabrice Desre fabr...@mozilla.com wrote:
On 06/01/2012 02:36 PM, Tobie Langel wrote:
On Jun 1, 2012, at 9:58 PM, Marcos Caceres w...@marcosc.com
mailto:w...@marcosc.com wrote:
Sounds good. AFAICT, Moz's proposal doesn't really cover packaging
either ... Not in the sense of
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
On Fri, Jun 1, 2012 at 12:40 PM, Marcos Caceres w...@marcosc.com wrote:
On 1 Jun 2012, at 18:18, Adam Barth w...@adambarth.com wrote:
On Fri, Jun 1, 2012 at 6:43 AM, Marcos Caceres w...@marcosc.com wrote:
On 31 May 2012, at 23:23, Adam Barth w...@adambarth.com wrote:
Is anyone besides
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
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:
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
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
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
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
On 6/4/12 6:41 PM, Fabrice Desre fabr...@mozilla.com wrote:
Hi Tobie,
On 06/04/2012 03:03 AM, Tobie Langel wrote:
On 6/2/12 6:54 AM, Fabrice Desré fabr...@mozilla.com wrote:
We're working on pre-loading the appcache at install time when the
appcache path is specified in the manifest. See
On 6/4/12 9:16 PM, Fabrice Desre fabr...@mozilla.com wrote:
On 06/04/2012 10:38 AM, Tobie Langel wrote:
On 6/4/12 6:41 PM, Fabrice Desre fabr...@mozilla.com wrote:
Hi Tobie,
On 06/04/2012 03:03 AM, Tobie Langel wrote:
On 6/2/12 6:54 AM, Fabrice Desré fabr...@mozilla.com wrote:
We're
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17308
Ted Mielczarek [:ted] t...@mielczarek.org changed:
What|Removed |Added
Status|NEW |RESOLVED
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17307
Ted Mielczarek [:ted] t...@mielczarek.org changed:
What|Removed |Added
Status|NEW |RESOLVED
On Jun 1, 2012, at 6:45 PM, Chris Pearce cpea...@mozilla.com 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
On Wed, 4 Apr 2012, Rafael Weinstein wrote:
On Mon, Apr 2, 2012 at 3:21 PM, Dimitri Glazkov dglaz...@chromium.org wrote:
Perhaps lost among other updates was the fact that I've gotten the
first draft of HTML Templates spec out:
On Mon, Jun 4, 2012 at 2:42 PM, Ian Hickson i...@hixie.ch wrote:
On Wed, 4 Apr 2012, Rafael Weinstein wrote:
On Mon, Apr 2, 2012 at 3:21 PM, Dimitri Glazkov dglaz...@chromium.org
wrote:
Perhaps lost among other updates was the fact that I've gotten the
first draft of HTML Templates spec
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 much
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 mode, also
Just to be clear: what you are objecting to is the addition of formal
API for this.
You're generally supportive of adding a template 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
On Mon, Jun 4, 2012 at 3:50 PM, Ian Hickson i...@hixie.ch 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
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 template element whose
contents would parse the way we're discussing here -- and given that, a
webdev could trivially
On Mon, Jun 4, 2012 at 4:38 PM, Ian Hickson i...@hixie.ch 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 template element whose
contents would parse the way we're
On Tue, Jun 5, 2012 at 9:13 AM, Jer Noble jer.no...@apple.com wrote:
On Jun 1, 2012, at 6:45 PM, Chris Pearce cpea...@mozilla.com wrote:
Because we exit fullscreen when the fullscreen element is removed from
the document, so if you dispatch events to the context element, the
On Jun 4, 2012, at 10:43 PM, Robert O'Callahan rob...@ocallahan.org wrote:
On Tue, Jun 5, 2012 at 9:13 AM, Jer Noble jer.no...@apple.com wrote:
On Jun 1, 2012, at 6:45 PM, Chris Pearce cpea...@mozilla.com wrote:
Because we exit fullscreen when the fullscreen element is removed from the
32 matches
Mail list logo
