On Jun 10, 2007, at 3:40 AM, Lachlan Hunt wrote:
Hi,
Apparently Firefox 3 has implemented new features for offline
resources, including rel=offline-resource and some new DOM APIs.
| Introduced support for link rel=offline-resource, which puts
| resources into the browser's offline cache.
Benjamin Hawkes-Lewis wrote:
I honestly don't think the property values are well-named. either is
confusing and vague; dont-want is a misspelled colloquialism. How
about one of the following possibilities:
captions: wanted
captions: unwanted
captions: no-preference
What happened to yes, no,
On Jun 11, 2007, at 2:24 AM, Robert O'Callahan wrote:
Maciej Stachowiak wrote:
I think the
Google Gears design for this works better than the Mozilla design,
because it lets offline mode use all the same URIs as regular mode,
so the offline support can be cleanly factored from the rest of the
On Fri, 08 Jun 2007 20:53:54 +0200, Michael A. Puls II
[EMAIL PROTECTED] wrote:
I believe Boris told me for FF, newline normalization (including
entities) is only done for parsing into the DOM and that any setting
of a string property in JS does zero newline normalization. So, if you
set \n\r,
At 0:02 -0400 10/06/07, Brian Campbell wrote:
On Jun 9, 2007, at 5:26 PM, Dave Singer wrote:
I have to confess I saw the BBC story about sign-language soon
after sending this round internally. But I need to do some study
on the naming of sign languages and whether they have ISO codes.
Is
On Tue, 25 Apr 2006, Henri Sivonen wrote:
Should apos; be a valid charater reference in text/html? If not,
what would be correct error handling?
I went with making it valid, since it's valid in XML.
That's problematic, because allowing it as a conforming entity reference
does
On Tue, 25 Apr 2006, Henri Sivonen wrote:
I assume number formats in attributes consistently do not allow
whitespace before and after. Am I right?
The spec says (for unsigned integers):
# A string is a valid non-negative integer if it consists of one of more
# characters in the range
On Sun, 7 May 2006, Simon Pieters wrote:
The conformance requirements section[1] states that:
HTML documents that use the new features described in this
specification and that are served over the wire (e.g. by HTTP) must be
sent as text/html and must start with the following DOCTYPE:
On 6/11/07, Anne van Kesteren [EMAIL PROTECTED] wrote:
On Fri, 08 Jun 2007 20:53:54 +0200, Michael A. Puls II
[EMAIL PROTECTED] wrote:
I believe Boris told me for FF, newline normalization (including
entities) is only done for parsing into the DOM and that any setting
of a string property in
Gears returns an error when you first try to setup an ambiguous
capture.
How do you do that when an ambiguity is discovered during a manifest update?
We hadn't thought about the case where the ambiguity is caused by a
manifest's new contents. Thanks for pointing that out.
what's the use
On Sun, 21 May 2006, Anne van Kesteren wrote:
Based on http://testsuite.org/html/elements/script/001.htm and
http://testsuite.org/html/elements/style/001.htm and the results in
Internet Explorer, Firefox and Opera it seems parsing can be made pretty
strict. The only real problem is script
11 matches
Mail list logo
