Mostly I like the new API (no surprise to Ian I'm sure).
http://www.whatwg.org/specs/web-apps/current-work/#sql
A few comments. I think putting the currentRow accessors directly on
the ResultSet is a bit of an odd choice. It seems like it could be
confusing that myResultSet[0] returns the
Why not text/xml+cache-manifest?
(Admittedly I can see a problem with this: '+' means addition but '-' does
not mean subtraction so it looks quite funny).
Chris
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ian Hickson
Sent: Friday, September 21, 2007
How much, if any, support is planned is Firefox 3 for HTML 5 and
especially WebForms 2.0 features? Looking at the prodyct requirements
document it doesn't seem like anything is likely to make thi release. Is
that accurate?
Has Mozilla given any indication of supporting this stuff (or subset
I do not share your reservations. The file contents does not constitute its
property and, unlike properties, much work is actually needed to extract it.
Therefore the name chosen seems very appropriate.
How is the character encoding determined when the file is read as text? An
arbitrary file is
I agree with both Maciej's points, and want the second one more than he did.
Additional comments:
4.12.3, step 3:
I don't think you should implicitly join active transactions unless
you're inside a callback from a previous executeSql call. Otherwise
all code that wants to call executeSql needs
The callback syntax is nice but the implicit thread-global transaction
is confusing and can lead to programmer error and unneeded database
locking.
Commonly there is a implicit transaction per query if there is no
explicit transaction created. I think this is what developers will
expect,
window.onerror
There needs to be a way to capture errors on the window.
A method that passes an Error to the handler. One possible solution
would be to leverage the existing event system:
addEventListener( error, genericErrorEventHandler, false );
function genericErrorEventHandler( errorEvent
On 9/20/07, Asbjørn Ulsberg [EMAIL PROTECTED] wrote:
On Tue, 11 Sep 2007 22:22:55 +0200, Garrett Smith [EMAIL PROTECTED]
wrote:
interface HTMLFormElement {
string getDataSetString(); raises FileException
string toJSONString(); raises FileException
};
I like the idea, but not this
On Sep 22, 2007, at 8:48 AM, Křištof Želechovski wrote:
I do not share your reservations. The file contents does not
constitute its
property and, unlike properties, much work is actually needed to
extract it.
Therefore the name chosen seems very appropriate.
How is the character encoding
On Sep 22, 2007, at 8:04 AM, Křištof Želechovski wrote:
Why not text/xml+cache-manifest?
(Admittedly I can see a problem with this: '+' means addition but
'-' does
not mean subtraction so it looks quite funny).
If the manifest format ends up being XML, it should be application/
On 22/09/2007, Garrett Smith [EMAIL PROTECTED] wrote:
Host objects are not quite javascript objects, so it wouldn't be an
override of Object.prototype. AFAIK, Host objects are not req'd to
support Object.prototype.
In Gecko, these host objects are either very well duck typed, or they
are
On Sep 22, 2007, at 9:32 AM, Aaron Boodman wrote:
I agree with both Maciej's points, and want the second one more than
he did.
Additional comments:
4.12.3, step 3:
I don't think you should implicitly join active transactions unless
you're inside a callback from a previous executeSql call.
12 matches
Mail list logo
