DOM2 Traversal and Range has a number of problems, and really needs a
rewrite. However, in the absence of the resources to do that, I realised
that we could settle for releasing some errata. Arguably we as a working
group have somewhat the authority to do that, so here's a proposal for a
Hi WebAPI Fans-
This is a reminder that we will have a DOM 3 Events telcon today, 14
May. Please reply to public-webapi@w3.org to express regrets if you
cannot attend.
The regular time is Wednesdays, 18:30-20:00 UTC. See the DOM3 Events
wiki page for timezones adjustments. [1]
The tentative
Ian Hickson wrote:
DOM2 Range says of the insertNode() method that A node may be inserted
into a Range using the following method. However, if the range is
collapsed, according to a strict reading of the specification, calling
insertNode() actually inserts the node _after_ the range. I propose
Hi all:
Need to pick uo my son from college and thus unable to join. Will try
towards the later part of the call.
Carmelo
On Wed, 14 May 2008 13:41:45 +0200, Doug Schepers [EMAIL PROTECTED] wrote:
This is a reminder that we will have a DOM 3 Events telcon today, 14
May. Please reply to public-webapi@w3.org to express regrets if you
cannot attend.
Can't attend. Leaving at 6 here (4PM UTC) for a hosted dinner.
Hi, Folks-
I have a conflict later on in the call, so it will be a short D3E
telcon. I plan to end at 3:30.
Thanks-
-Doug
Doug Schepers wrote (on 5/14/08 7:41 AM):
Hi WebAPI Fans-
This is a reminder that we will have a DOM 3 Events telcon today, 14
May. Please reply to
* Julian Reschke wrote:
Peter Michaux wrote:
I think all XMLHttpRequest headers should be specified as blank when
the object is created. Then the JavaScript can add any headers it
needs to add. If, when the call to send() occurs, some essential
header(s) is missing the XHMLHttpRequest object
On Tue, 13 May 2008 23:21:57 +0200, Jonas Sicking [EMAIL PROTECTED] wrote:
Access-Control is developed by a wholly different WG though (at least
until the two groups merge).
Has it been properly announced to the members, and other participants,
of that WG that this meeting is taking place?
Ian Hickson wrote:
I propose that we change the spec to explicitly say that if you call insertNode() on a
collapsed range, the end point offset is increased by one
Increased at what point in time, exactly? Specifically, if there is a
DOMNodeInserted listener that repositions the range when
Also have a conflict at this time. This makes two weeks in a row :(
I send my regrets that I cannot attend this week.
Status:
* Very little progress on DOM L3 Events action items--expect to have completed
a few of those by next telecom.
-Original Message-
From: [EMAIL PROTECTED]
Hi all,
I made some testing on WinXP using IE7, FF3pre, Opera9.5b, Safari3.1
http://mozilla.pettay.fi/moztests/events/browser-keyCodes.htm
-Olli
On Thu, 08 May 2008 12:05:23 +0200, Ian Hickson [EMAIL PROTECTED] wrote:
We have had requests to fire some kind of identifiable event when typing
occurs during IME processing for use cases like the following:
1) To resize an area based on user typing, even during IME entry (yes,
this
works
On Wed, 14 May 2008 22:17:39 +0200, Hallvord R. M. Steen
[EMAIL PROTECTED] wrote:
I think all UAs I tested send keyup events - perhaps that's all we need
though?
(Sorry, ignore that. Only IE does - I should have re-tested before sending
the E-mail..)
--
Hallvord R. M. Steen
Core QA
On Wed, May 14, 2008 at 6:15 PM, Ian Hickson [EMAIL PROTECTED] wrote:
To my knowledge, very little Web content relies on this spec at all.
That's why Acid3 tested it, to make it interoperable enough that it could
be used. :-)
I thought Acid3 tested things that have been written down for at
* Hallvord R. M. Steen wrote:
I've never really written English specification prose before (though I've
been an avid reader of W3C TRs) so please give this stuff a critical but
patient review ;-)
I don't think it is useful to discuss specification prose if it's
unclear what is to be
On Wed, May 14, 2008 at 9:02 PM, Ian Hickson [EMAIL PROTECTED] wrote:
As I said in the very first e-mail on this subject, that's what I'd like
to do. However, that's a significantly higher cost (years vs weeks) than
releasing an errata, and it was my impression that the Mozilla community
On Wed, 14 May 2008, Robert Sayre wrote:
On Wed, May 14, 2008 at 9:02 PM, Ian Hickson [EMAIL PROTECTED] wrote:
As I said in the very first e-mail on this subject, that's what I'd
like to do. However, that's a significantly higher cost (years vs
weeks) than releasing an errata, and it
FYI, I just changed the HTML5 spec to use 'loadstart' instead of 'begin'
for the first ProgressEvent. It turns out the reason I used 'begin' is
that an older version of Progress Events used 'begin', and this was
changed without me noticing.
Is there a place where I can track what feedback
Ian Hickson wrote:
DOM2 Range doesn't define anything to this level of detail yet,
unfortunately.
Indeed. The wonders of Conway's Law...
Nevertheless, this question is somewhat important in terms of deciding where the
range should be positioned.
For example regular old insertions and
19 matches
Mail list logo
