On 2/28/11, Anne van Kesteren ann...@opera.com wrote:
On Fri, 25 Feb 2011 18:47:54 +0100, Garrett Smith dhtmlkitc...@gmail.com
wrote:
Your example is simple. But some common cases of synth events are
complicated. UI Events aren't so bad but MouseEvents and especially
TouchEvents are a lot of
On Sat, 26 Feb 2011 16:15:25 +0100, Doug Schepers schep...@w3.org wrote:
I will remove my objection to publish DOM Core if: 1) conflicts (rather
than extensions) are removed from the draft, or reconciled with changes
in DOM3 Events; and 2) for those changes that have broad consensus, we
can
Hi, Kang-Hao.
On 2011/02/28 21:31, Kang-Hao (Kenny) Lu wrote:
Hello Makoto,
(Cc+ public-webapps)
(11/02/25 15:16), Makoto Kato wrote:
Hi,
This is simple sample. This behavior is different on all web browsers
when input element has composition/preedit string for IME.
A relevant question
On Tue, 01 Mar 2011 09:00:27 +0100, Garrett Smith dhtmlkitc...@gmail.com
wrote:
Mouse.click(document.body, {clientX : 10});
Yeah, that would be simpler. However, we do not really have this pattern
anywhere in browser APIs and I believe last time we played with objects
(for namespace
On Mon, Feb 28, 2011 at 11:57 PM, Maciej Stachowiak m...@apple.com wrote:
For what it's worth, I think this is a useful draft and a useful technology.
Hotlinking prevention is of considerable interest to Web developers, and
doing it via server-side Referer checks is inconvenient and
+dveditz and +bsterne because they have strong opinions about CSP.
Adam
On Tue, Mar 1, 2011 at 12:26 AM, Adam Barth w...@adambarth.com wrote:
On Mon, Feb 28, 2011 at 11:57 PM, Maciej Stachowiak m...@apple.com wrote:
For what it's worth, I think this is a useful draft and a useful technology.
On Mon, 28 Feb 2011 17:59:45 +0100, Adrian Bateman
adria...@microsoft.com wrote:
Something boxed out at the start of the Events section would be great
for now.
Added:
https://bitbucket.org/ms2ger/dom-core/changeset/a997dac35d91
Hopefully we can make sure that the drafts are aligned and if
On Tue, Mar 1, 2011 at 7:23 PM, Anne van Kesteren ann...@opera.com wrote:
On Tue, 01 Mar 2011 09:00:27 +0100, Garrett Smith dhtmlkitc...@gmail.com
wrote:
Mouse.click(document.body, {clientX : 10});
Yeah, that would be simpler. However, we do not really have this pattern
anywhere in
On Tue, 01 Mar 2011 08:51:24 +0100, Maciej Stachowiak m...@apple.com
wrote:
What conflicts or contradictions exist currently? Does anyone have a
list?
Some time ago I put a list in the draft:
http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#dom-events
Glenn Maynard and I are still
On Tue, Mar 1, 2011 at 12:48 AM, Ojan Vafai o...@chromium.org wrote:
On Tue, Mar 1, 2011 at 7:23 PM, Anne van Kesteren ann...@opera.com wrote:
On Tue, 01 Mar 2011 09:00:27 +0100, Garrett Smith dhtmlkitc...@gmail.com
wrote:
Mouse.click(document.body, {clientX : 10});
Yeah, that would be
On Tue, 01 Mar 2011 09:59:59 +0100, Jonas Sicking jo...@sicking.cc wrote:
We're also using it in IndexedDB, though I don't think this has gotten
into the spec drafts yet. But it is in the firefox implementation and
I *think* in the chrome implementation.
The issue raised with it last time (by
On 3/1/11 3:48 AM, Ojan Vafai wrote:
Mouse.click(document.body, {clientX : 10});
...
The Chromium extension APIs use this pattern and I think it's gone over
well in that space. For example, see chrome.contextMenus.create at
http://code.google.com/chrome/extensions/contextMenus.html. I
On Mon, 28 Feb 2011 18:49:48 +0100, Garrett Smith dhtmlkitc...@gmail.com
wrote:
| DOM Core defines the event and document model the Web platform uses.
That says that DOM Core defines two different things: events and DOM.
Some things might implement DOM Events Core (or a subinterface
thereof)
I have been following the development behind IndexedDB with interest. Thank you
all for your efforts.
I understand that the initial version of IndexedDB will not support indexing
array values.
May I suggest an alternative derived from my home-brew server database evolved
from experience using
On Tue, Mar 1, 2011 at 7:34 AM, Joran Greef jo...@ronomon.com wrote:
I have been following the development behind IndexedDB with interest. Thank
you all for your efforts.
I understand that the initial version of IndexedDB will not support
indexing array values.
May I suggest an alternative
I do think Content Security Policy offers a good opportunity to address
the use cases Anne brought up.
CSP already has a directive, frame-ancestors, that restricts the context
in which a resource can be embedded as a iframe, frame or object
to a list of origins. Perhaps we should expand the
On Mon, Feb 28, 2011 at 4:59 PM, Charles Pritchard ch...@jumis.com wrote:
On 2/28/2011 4:10 PM, Eric Uhrhane wrote:
On Mon, Feb 28, 2011 at 2:54 PM, Charles Pritchardch...@jumis.com
wrote:
I'd like some clarification on the intent of the FileSystem API:
requestFileSystem permanent,
On Mon, Feb 28, 2011 at 6:21 PM, Glenn Maynard gl...@zewt.org wrote:
On Mon, Feb 28, 2011 at 7:41 PM, Eric Uhrhane er...@google.com wrote:
Sorry--I meant to push this over to public-webapps, as Ian suggested.
[+cc public-webapps, whatwg-BCC]
Currently (reviewing for context), the spec tries
Adam wrote:
There's been a bunch of discussion on the public-web-security mailing
list about the scope of CSP. Some folks think that CSP should be a
narrow feature targeted at mitigating cross-site scripting. Other
folks (e.g., as articulated in
http://w2spconf.com/2010/papers/p11.pdf)
On Tue, Mar 1, 2011 at 1:13 PM, Eric Uhrhane er...@google.com wrote:
What would you suggest for limitations? If we're requiring
virtualization, it seems to me that we could be quite liberal.
I'd suggest only the restrictions that are required for the API: no
, ., .., and no filenames
3. Otherwise, create an event that uses the MessageEvent interface, with
the event name message [...]
4. If the event name buffer has a value other than the empty string,
change the type of the newly created event to equal the value of the event
name buffer.
I'd suggest consistently saying the
On Tue, Mar 1, 2011 at 11:37 AM, Glenn Maynard gl...@zewt.org wrote:
On Tue, Mar 1, 2011 at 1:13 PM, Eric Uhrhane er...@google.com wrote:
What would you suggest for limitations? If we're requiring
virtualization, it seems to me that we could be quite liberal.
I'd suggest only the
Anne van Kesteren wrote:
http://dvcs.w3.org/hg/from-origin/raw-file/tip/Overview.html
And although it might end up being part of the Content Security Policy
work I think it would be useful if publish a Working Draft of this work
to gather more input, committing us nothing.
What do you
On Tue, Mar 1, 2011 at 3:33 PM, Nathan nat...@webr3.org wrote:
(rather than controlled only by user agents which choose to follow the
specs offering
an artificial screen).
If user agents deliberately ignore the specs to allow embedding where
authors don't want it to, they can do it with any
Glenn Maynard wrote:
On Tue, Mar 1, 2011 at 3:33 PM, Nathan nat...@webr3.org wrote:
(rather than controlled only by user agents which choose to follow the specs
offering
an artificial screen).
If user agents deliberately ignore the specs to allow embedding where
authors don't want it to,
On Tue, Mar 1, 2011 at 8:51 AM, Boris Zbarsky bzbar...@mit.edu wrote:
The big worry here is that you have to be _very_ careful to define behavior
properly. It's not an issue for extension APIs, where you can assume that
the caller will do sane (and probably non-malicious) things. But for a
On Tue, 1 Mar 2011, Aryeh Gregor wrote:
On Tue, Mar 1, 2011 at 8:51 AM, Boris Zbarsky bzbar...@mit.edu wrote:
The big worry here is that you have to be _very_ careful to define
behavior properly. It's not an issue for extension APIs, where you
can assume that the caller will do sane (and
On Tue, 1 Mar 2011, Anne van Kesteren wrote:
On Sat, 26 Feb 2011 16:15:25 +0100, Doug Schepers schep...@w3.org wrote:
I would still like to help edit that specification, to bring a
slightly different perspective and approach, and to coordinate between
DOM3 Events and DOM Core, and I
On 3/1/11 12:26 AM, Adam Barth wrote:
From-Origin is closely related to one of the proposed CSP
features, namely frame-ancestors, which also controls how the
given resource can be embedded in other documents:
Also similar to X-Frame-Options; I'd hate to end up with all three
mechanisms. I'd be
On 3/1/11, Anne van Kesteren ann...@opera.com wrote:
On Mon, 28 Feb 2011 18:49:48 +0100, Garrett Smith dhtmlkitc...@gmail.com
wrote:
| DOM Core defines the event and document model the Web platform uses.
That says that DOM Core defines two different things: events and DOM.
Some things might
On Tue, Mar 1, 2011 at 5:18 PM, Makoto Kato m_k...@ga2.so-net.ne.jp wrote:
On Safari 5, even if textbox has IME composition string, text into textbox
can be replaced by DOM/script. But other browser's behaviors are different,
and this is no specification when textbox has composition string.
On 01 Mar 2011, at 7:27 PM, Jeremy Orlow wrote:
1. Be able to put an object and pass an array of index names which must
reference the object. This may remove the need for a complicated indexing
spec (perhaps the reason why this issue has been pushed into the future) and
give developers all
32 matches
Mail list logo
