Cameron McCormack:
> I don’t know how important it is to keep the HTML interfaces in the
> org.w3c.dom.html package, but it definitely seems important to keep
> DOM Core and Events interfaces in org.w3c.dom and org.w3c.dom.events.
Ian Hickson:
> Why? How does it affect black-box compliance of Web-
Hi Anselm.
Cameron McCormack:
> > I think you should define this instead using named properties. It
> > doesn’t seem to be useful to define an interface that has attributes
> > with particular names and types if they might not exist at all (or might
> > exist but be different types).
Anselm R Ga
On Thu, Jul 2, 2009 at 12:48 PM, Ian Hickson wrote:
> We don't need to. After it has expired it would act exactly like one of
> these URIs with a bogus handle. e.g. if the URIs created by this API are
> of the form local-file:93875, and that is the only particular one that has
> ever been handed ba
On Thu, 2 Jul 2009, Jonas Sicking wrote:
>
> This would be a more interesting discussion if someone could actually
> come up with a spec for localURL :)
Other than lifetime, is there anything major missing from the description
I sent originally?
http://lists.w3.org/Archives/Public/public-webap
On Thu, 02 Jul 2009 18:38:03 +0200, Jonas Sicking wrote:
On Thu, Jul 2, 2009 at 2:58 AM, Anne van Kesteren
wrote:
I tend to think that if we are going to introduce a URL scheme to point
to file data on the system we should not be adding the data URL method.
As far as I can tell there are n
Giovanni Campagna wrote:
Then we need a discussion about the possibility of having a spec for
XMLSerializer, having already DOM3LS.
Which probably needs changes similar to what Henri proposed to actually
work correctly with HTML5.
-Boris
On Thu, Jul 2, 2009 at 2:58 AM, Anne van Kesteren wrote:
> I tend to think that if we are going to introduce a URL scheme to point to
> file data on the system we should not be adding the data URL method. As far
> as I can tell there are no benefits to introducing it as it will only
> increase m
The draft minutes from the July 2 Widgets voice conference are
available at the following and copied below:
http://www.w3.org/2009/07/02-wam-minutes.html
WG Members - if you have any comments, corrections, etc., please send
them to the public-webapps mail list before 9 July 2009 (the next
Hi Marcos,
Marcos Caceres wrote:
[...]
Comment 1: relative can't be absolute
-
[...]
Fixed. Used your text.
OK.
Comment 2: links resolution in e.g. start file
-
The specification implies but does not define how links in documents other
than the configuration document are to be h
On 2.7.2009 15.18, "ext Marcos Caceres" wrote:
> Hi,
> At the last teleconf, it was requested that I prepare a list of P&C
> work items that could be distributed among those WG members helping
> with the standardization of widgets. Here are a parts of emails that
> need responding to (order does
Hi,
At the last teleconf, it was requested that I prepare a list of P&C
work items that could be distributed among those WG members helping
with the standardization of widgets. Here are a parts of emails that
need responding to (order does not denote priority, though Josh's
comments seem to be mos
On Tue, Jun 30, 2009 at 10:27 AM, wrote:
> On 29.6.2009 13.30, "ext Marcos Caceres" wrote:
>> Right. I've moved everything and renamed examples > "Localization examples".
>>
>>> This would make the material flow better and have all the concepts defined
>>> before they are used.
>>
>> I will need
2009/7/1 Arthur Barstow :
> b. Dig Sig testing - call for inputs for testable assertion list
Yesterday I was dabbling with openssl and xmlsec1:
http://www.aleksey.com/pipermail/xmlsec/2009/008686.html
Still trying to come up with a helloworld example where I (the author)
sign with a private key a
X=posted. PLEASE, if you feel a need to reply (can't think why you would),
trim the reply to the list that might care.
(and not contactable. Regrets for everything)
cheers
Chaals
--
Charles McCathieNevile Opera Software, Standards Group
je parle français -- hablo español -- jeg lærer no
I tend to think that if we are going to introduce a URL scheme to point to file
data on the system we should not be adding the data URL method. As far as I can
tell there are no benefits to introducing it as it will only increase memory
usage when used by authors and the uses it has can be perfe
On Jul 2, 2009, at 12:11, Giovanni Campagna wrote:
2009/7/2 Cameron McCormack :
Henri Sivonen:
Gecko bug:
https://bugzilla.mozilla.org/show_bug.cgi?id=500937
The proposed patch there and (based on black-box testing) WebKit
solve
the issue by running the HTML serialization algorithm when th
2009/7/2 Cameron McCormack :
> Henri Sivonen:
>> Gecko bug:
>> https://bugzilla.mozilla.org/show_bug.cgi?id=500937
>>
>> The proposed patch there and (based on black-box testing) WebKit solve
>> the issue by running the HTML serialization algorithm when the owner
>> document of the input node is an
On Jul 2, 2009, at 12:38 AM, Ian Hickson wrote:
On Thu, 2 Jul 2009, Cameron McCormack wrote:
I don’t know how important it is to keep the HTML interfaces in the
org.w3c.dom.html package, but it definitely seems important to keep
DOM
Core and Events interfaces in org.w3c.dom and org.w3c.dom
Hi Cameron,
2009/7/2 Cameron McCormack :
> Anselm R Garbe:
>> For example, we are using a Map-like object that exposes file metadata
>> which differs among different files (eg an MP3 file has totally
>> different metadata than an executable), but the metadata might also
>> contain commonly used at
On Thu, 2 Jul 2009, Cameron McCormack wrote:
>
> I don’t know how important it is to keep the HTML interfaces in the
> org.w3c.dom.html package, but it definitely seems important to keep DOM
> Core and Events interfaces in org.w3c.dom and org.w3c.dom.events.
Why? How does it affect black-box com
20 matches
Mail list logo
