Any chance this list is made available with links to the feature
implementations. Most of the players I know of have such a page at least
for SVG and the burry of SVG viewer will create holes, I believe.
paul
Antoine Quint wrote:
Hey Doug,
A couple of precisions
On 21 sept. 2006, at
Hi Mark,
thanks a lot for your review.
On Sep 21, 2006, at 15:18, Mark Baker wrote:
Editorial;
- sec 1, This interface should be This specification
- sec 3, I'd suggest s/apparition/display/
Applied.
Substantive;
- sec 3, regarding On devices that have no file system, the
user-agent MAY
On Wed, 20 Sep 2006 13:43:34 -, Web APIs Issue Tracker
[EMAIL PROTECTED] wrote:
My proposal is to throw an exception (INVALID_STATE_ERR) for every
member where this is relevant (as has been suggested before on this
list).
I have implemented this proposal in the editor's draft based
Hi, folks-
I'm following up on the action to research how Adobe Flash handles
cross-domain access.
This is done by the use of an XML file on the target server,
crossdomain.xml.
The security model is described in a PDF whitepaper [1]:
The Cross Domain Policy File mechanism is a simple XML
Hi folks,
I have a draft for the clipboard stuff. It's pretty rough and there is
plenty to do still, but it is at
http://dev.w3.org/cvsweb/2006/webapi/clipops/clipops.html?rev=1.6
comments welcome as always...
cheers
Chaals
--
Charles McCathieNevile, Opera Software: Standards Group
ISSUE-90: passwd seems underdefined in RFC2617
http://www.w3.org/2005/06/tracker/webapi/issues/90
Raised by: Anne van Kesteren
On product: XMLHttpRequest
For the open() method I was trying to come up with error handling for the user
and password arguments. It seems that user comes down to
* Web APIs Issue Tracker wrote:
ISSUE-90: passwd seems underdefined in RFC2617
http://www.w3.org/2005/06/tracker/webapi/issues/90
Raised by: Anne van Kesteren
On product: XMLHttpRequest
For the open() method I was trying to come up with error handling for the user
and password arguments. It
Anne van Kesteren wrote:
How is that defined? Is it possible to take window1.XMLHttpRequest
and use apply() to call it with window2 as |this|?
...
Sorry, it's the window from which you use the constructor.
That doesn't answer my question above. It just shifts the burden onto defining
I'm concerned about the open() method on the FileDialog interface.
It seems like it would make it possible, through an attack like the famous
fast clicking game, to cause a user to select a file (probably at random,
but from the user's home directory, so likely a confidential file).
I would
On Fri, 22 Sep 2006, Robin Berjon wrote:
I would feel much more comfortable if the FileList API was provided
merely as an extension to the HTMLInputElement interface, thus
requiring authors to use an input type=file control, and requiring
users to click the Browse button before the
Hi Ian,
On Sep 22, 2006, at 17:15, Ian Hickson wrote:
It seems like it would make it possible, through an attack like the
famous
fast clicking game, to cause a user to select a file (probably at
random,
but from the user's home directory, so likely a confidential file).
There are
On Fri, 22 Sep 2006 16:41:12 -, Boris Zbarsky [EMAIL PROTECTED] wrote:
That doesn't answer my question above. It just shifts the burden onto
defining what the window from which you use the constructor means.
Can you point out the problem in that definition?
Could we have a definition
Anne van Kesteren wrote:
On Fri, 22 Sep 2006 16:41:12 -, Boris Zbarsky [EMAIL PROTECTED] wrote:
That doesn't answer my question above. It just shifts the burden onto
defining what the window from which you use the constructor means.
Can you point out the problem in that definition?
Boris Zbarsky [EMAIL PROTECTED]
To repeat it a third time. If do something along the lines of:
var func = window1.XMLHttpRequest;
var req = new (func.apply(window2)();
or some such, which is the window from which you use the constructor?
window1 or window2?
If what I said is not possible
Jim Ley wrote:
It's a host object the apply is undefined in ECMA, so I see no reason
for the WEB API's WG to define it more than ECMA does.
Unless you want better interoperability than ECMA provides, of course. Which I
do.
I would encourage you to simply not support apply on such host
Here's a few remarks that strike me at first:
- I'm missing a copy-event... or do you really want to be as
MSIE-follower so as not having such and rely on the old method that
write directly to a clipboard singleton. If wishing to do so, I
recommend we try to follow Safari's way and spec [1]
Hi Paul,
thanks for looking at the draft and for your comments.
On Fri, 22 Sep 2006 22:33:54 -, Paul Libbrecht [EMAIL PROTECTED]
wrote:
Here's a few remarks that strike me at first:
- I'm missing a copy-event
that's just a straight bug I think, but I will look at it for the next
17 matches
Mail list logo
