I agree with Jacob. I find this part of the spec... puzzling.
Since there is currently no way to differentiate between a copy and a
dragstart, you could potentially cause unnecessary UI flicker if you
added/changed elements during dragstart and removed them during dragend to
make a visual
On Jul 27, 2009, at 05:37 , Travis Leithead wrote:
Adding WWW-DOM to widen the audience a bit.
Having the attributes not be read only and allowing their
modification before the Event is dispatched seems better to me.
But changing this for DOM Events in general seems like a larger
issue
The OpenSocial spec also defines a set of views for gadgets[1] and I
was wondering how these relate to Widget modes as defined in [2].
Here's a quick stab at relating the two specs:
gadgets.views.ViewType.CANVAS = application (or fullscreen?)
gadgets.views.ViewType.HOME = floating
On Sat, 27 Jun 2009 08:57:06 +0200, Cameron McCormack c...@mcc.id.au wrote:
I’d like to know what specs are currently using Web IDL, so that I can
keep abreast of what features are being used and help to review them.
This is what I have so far:
[...]
Are there any others people are aware
On Thu, 16 Jul 2009 12:16:00 +0200, Simon Pieters sim...@opera.com wrote:
On Tue, 30 Jun 2009 09:07:22 +0200, Cameron McCormack c...@mcc.id.au
wrote:
Cameron McCormack:
Following are my half baked proposals.
I’ve now baked all of these proposals into the spec, except for the one
about
Robin Berjon wrote:
Do other implementers care to chime in with what they do, and if they'd
find this change acceptable?
As I recall Gecko's behavior, it works more or less like this:
1) Properties listed as readonly in the DOM 2 Events IDL are in
fact readonly.
2) init*Event may be
For the JS framework MooTools, I'm currently implementing a model where you
can pass an object to an event constructor: new Event({ foo: 'bar', foo2:
'bar' });
Any uninitialized properties would fall back to defaults. This would be
comparable to named parameters found in many languages. You could
http://dev.w3.org/html5/webstorage/#the-storage-interface
Web Storage how to check for support?
How can one in a script check for UA support?
How about either of the following, they both worked as expected for me.
// Check for the Storage interface
if (window.Storage) { ... }
// Check
On Mon, Jul 27, 2009 at 3:40 PM, Scott
Wilsonscott.bradley.wil...@gmail.com wrote:
The OpenSocial spec also defines a set of views for gadgets[1] and I was
wondering how these relate to Widget modes as defined in [2].
Here's a quick stab at relating the two specs:
Joseph,
thanks for that,
had tried document but not window
regards
~:
On 27 Jul 2009, at 16:41, Joseph Pecoraro wrote:
http://dev.w3.org/html5/webstorage/#the-storage-interface
Web Storage how to check for support?
How can one in a script check for UA support?
How about either of the
On Sun, Jul 26, 2009 at 11:29 PM, Marcin
Hanclikmarcin.hanc...@access-company.com wrote:
Hi,
Given the fact that
Rule names are case insensitive.
http://tools.ietf.org/html/rfc5234#section-2.1
it could potentially be better to rename the rule from utf8-char to
something else, since it
2009/7/25 Marcin Hanclik marcin.hanc...@access-company.com:
Hi Marcos, All,
Regarding the usage of IRI in the widget configuration document, I do not
know which speicification is responsible for mandating the IRI normalization.
It is possible that I simply have not yet found the proper
On Mon, Jul 20, 2009 at 6:41 PM, Marcin
Hanclikmarcin.hanc...@access-company.com wrote:
Dear All,
Following the discussions (as below) about the topic of the required
attribute on access element, I would like to provide a few comments to the
current WARP WD.
Historically access element
On Tue, Jul 21, 2009 at 7:40 PM, Marcos Caceresmarc...@opera.com wrote:
On Jul 21, 2009, at 7:27 PM, Scott Wilson scott.bradley.wil...@gmail.com
wrote:
+1
Sounds sensible - I've had a hard time figuring out what to do about these
without the view modes spec being completed.
I guess
http://dev.w3.org/html5/webstorage/#user-tracking
Treating persistent storage as cookies: mozilla safari
anyone been able to clear localStorage via cookie preferences in
mozilla or safari?
regards
Jonathan Chetwynd
testcase:
https://bug506639.bugzilla.mozilla.org/attachment.cgi?id=390836
Marcos,
I am quite well aware of the purported purposes of w3 lists, with
somewhat over a decade's experience.
however there are rather serious security and privacy concerns, and if
the current UA implementations have not followed the specifications**,
and these need to be fed back to
On Jul 25, 2009, at 1:18 PM, Aaron Boodman wrote:
On Fri, Jul 24, 2009 at 6:51 PM, Nikunj R. Mehtanikunj.me...@oracle.com
wrote:
It appears that Database, SQLTransactionCallback,
SQLTransactionErrorCallback, SQLVoidCallback, SQLTransaction,
SQLStatementCallback, and SQLStatementErrorCallback
On Mon, Jul 27, 2009 at 11:55 AM, Nikunj R.
Mehtanikunj.me...@oracle.com wrote:
On Jul 25, 2009, at 1:18 PM, Aaron Boodman wrote:
On Fri, Jul 24, 2009 at 6:51 PM, Nikunj R. Mehtanikunj.me...@oracle.com
wrote:
It appears that Database, SQLTransactionCallback,
SQLTransactionErrorCallback,
On Jul 27, 2009, at 12:55 PM, Nikunj R. Mehta wrote:
On Jul 25, 2009, at 1:18 PM, Aaron Boodman wrote:
But using workers is a large burden: they are
completely separate JavaScript environments that share nothing with
the main web page. Having to use that for simpler use cases would be
very
On Jul 27, 2009, at 12:43 PM, Aaron Boodman wrote:
On Mon, Jul 27, 2009 at 11:55 AM, Nikunj R.
Mehtanikunj.me...@oracle.com wrote:
On Jul 25, 2009, at 1:18 PM, Aaron Boodman wrote:
On Fri, Jul 24, 2009 at 6:51 PM, Nikunj R. Mehtanikunj.me...@oracle.com
wrote:
There is a brand new
On Jul 27, 2009, at 12:54 PM, Maciej Stachowiak wrote:
On Jul 27, 2009, at 12:55 PM, Nikunj R. Mehta wrote:
snip
JavaScript actually lets you write a series of nested callbacks in a
way that looks almost like straight-line code, by using function
expressions:
On Jul 27, 2009, at 2:14 PM, Nikunj R. Mehta wrote:
And mine did get awkward, very quickly. I found it really hard to
keep myself sane through the development of asynchronous code that
executes transactionally and involves multiple sql statements.
My argument is that the program logic
On Mon, Jul 27, 2009 at 2:03 PM, Sebastian
Markbågesebast...@calyptus.eu wrote:
I agree with Jacob. I find this part of the spec... puzzling.
so, one advantage of not distinguishing is that it enables people w/o
mice to trigger drag events.
if you don't do this, you effectively block such users
timeless said:
so, one advantage of not distinguishing is that it enables people w/o mice
to trigger drag events.
Do you have any data on how many people would be browsing with neither mouse
nor touch capabilities? Are you mostly referring to non-touch mobile users?
if you don't do this,
On Mon, Jul 27, 2009 at 2:32 PM, Maciej Stachowiakm...@apple.com wrote:
On Jul 27, 2009, at 2:14 PM, Nikunj R. Mehta wrote:
And mine did get awkward, very quickly. I found it really hard to keep
myself sane through the development of asynchronous code that executes
transactionally and
On Jul 27, 2009, at 7:45 PM, Jonas Sicking wrote:
On Mon, Jul 27, 2009 at 2:32 PM, Maciej Stachowiakm...@apple.com
wrote:
On Jul 27, 2009, at 2:14 PM, Nikunj R. Mehta wrote:
And mine did get awkward, very quickly. I found it really hard to
keep
myself sane through the development of
On Mon, Jul 27, 2009 at 8:07 PM, Nikunj R. Mehtanikunj.me...@oracle.com wrote:
On Jul 27, 2009, at 7:45 PM, Jonas Sicking wrote:
On Mon, Jul 27, 2009 at 2:32 PM, Maciej Stachowiakm...@apple.com wrote:
On Jul 27, 2009, at 2:14 PM, Nikunj R. Mehta wrote:
And mine did get awkward, very
27 matches
Mail list logo
