BlackBerry 9700 browser:
(Kartikaya Gupta from RIM e-mailed me off list about this to tell me,
I'm unable to verify these results myself without access to the
device.)
Baseline Tests: HTML/CSS2.1:PASS
Additional Tests: HTML/CSS3: PASS
Additional Tests: XHTML
On Tue, 13 Oct 2009, Garrett Smith wrote:
I would like to see input from Palm, RIM, Opera, and other developers
of mobile browsers and touch screen devices on this thread.
As a RIM developer, we do not currently support touch events in our browser; we
just map them to mouse events where a
On Mon, 29 Dec 2008 17:24:03 +1100, Charles McCathieNevile
cha...@opera.com wrote:
On Mon, 29 Dec 2008 13:33:35 +1100, Kartikaya Gupta
lists.weba...@stakface.com wrote:
On Mon, 29 Dec 2008 11:30:42 +1100, Charles McCathieNevile
cha...@opera.com wrote:
Please review and send
On Sun, 19 Jul 2009 08:05:32 + (UTC), Ian Hickson i...@hixie.ch wrote:
On Sat, 18 Jul 2009, Kartikaya Gupta wrote:
I was wondering if the test suite for selectors-api to could be modified
to include #FF (uppercase) as a valid red value in addition to
(255, 0, 0), #ff
On Thu, 12 Feb 2009 07:03:22 +0100, Simon Pieters sim...@opera.com wrote:
On Wed, 11 Feb 2009 21:14:44 +0100, Kartikaya Gupta
lists.weba...@stakface.com wrote:
I updated to Safari 3.2 on Windows (which looks it also has WebKit
525.27.1) and you're right, it is now showing number
On Wed, 11 Feb 2009 10:06:14 -0800, Darin Adler da...@apple.com wrote:
However, when I do this:
var e = document.createEvent('Events');
alert( typeof e.timeStamp );
I get number in Opera and Firefox, and object in Webkit.
I get number in WebKit.
-- Darin
On Wed, 11 Feb 2009 10:58:00 -0800, Darin Adler da...@apple.com wrote:
On Feb 11, 2009, at 10:51 AM, Kartikaya Gupta wrote:
Interesting. What version did you try on? I used Chrome 1.0.154.48
and Safari 3.1 (525.13) on Windows.
The relevant version is the WebKit version rather than
On Thu, 05 Feb 2009 01:21:09 +0100, Charles McCathieNevile cha...@opera.com
wrote:
Hi folks,
this is a call for consensus to move the Selectors API [1] to Candidate
Recommendation, following the end of the last call.
[1] http://dev.w3.org/2006/webapi/selectors-api/
One minor fix:
On Mon, 26 Jan 2009 10:07:08 -0500, Arthur Barstow art.bars...@nokia.com
wrote:
WebApps WG Members - this is a Call for Consensus (CfC) to publish
the Element Traversal errata as proposed by Cameron:
http://lists.w3.org/Archives/Public/public-webapps/2009JanMar/
0168.html
As with
On Mon, 29 Dec 2008 11:30:42 +1100, Charles McCathieNevile cha...@opera.com
wrote:
Please review and send brickbats, comments, etc. before I ask for a
consensus to publish last call. Especially appreciated are examples and
test cases :)
1. s/are not be/are not/
2. Section 2.2,
Found an issue in DOM2 Range that doesn't seem to be addressed anywhere that I
could find:
Section 2.12.1 (handling insertions) says that the boundary point offset should
only be adjusted if the insertion point's offset is strictly less than it.
However, the first example they give doesn't do
On Wed, 10 Dec 2008 16:28:25 +0100, Anne van Kesteren [EMAIL PROTECTED]
wrote:
Actually, clearing it when you invoke send() should be enough. Made that
change to the editor drafts.
I see the change in the XHR2 draft, but not the XHR draft.
Also, will the IDL be updated to reflect
The editor's draft of the XHR spec doesn't say when to clear the error flag.
Based on experimentation I'm guessing it's supposed to be cleared in step 21 of
the open() algorithm. Is this correct?
Also, will the IDL be updated to reflect exceptions thrown from the various
methods and property
On Mon, 24 Nov 2008 14:51:53 +, Kartikaya Gupta [EMAIL PROTECTED] wrote:
On Mon, 24 Nov 2008 15:10:03 +0100, Lachlan Hunt [EMAIL PROTECTED] wrote:
Kartikaya Gupta wrote:
Also, I noticed that the draft still points to public-webapps as the
discussion list. Should that be updated
On Tue, 02 Dec 2008 15:41:23 +0100, Anne van Kesteren [EMAIL PROTECTED]
wrote:
Also, I have the same question for XHR that I had for Selectors-API:
what module/java-package will it be in?
I'd hope non-ECMAScript languages have a better API for dealing with HTTP
:-) In other words,
On Mon, 1 Dec 2008 11:12:13 +1100, Cameron McCormack [EMAIL PROTECTED] wrote:
Done:
http://dev.w3.org/2006/webapi/WebIDL/#idl-modules
http://dev.w3.org/2006/webapi/WebIDL/#Prefix
http://dev.w3.org/2006/webapi/WebIDL/#java-modules
The example in the java-modules section has a
On Fri, 28 Nov 2008 21:42:08 +1100, Cameron McCormack [EMAIL PROTECTED] wrote:
Alternatively: is it worth hard coding a Java package prefix into the
spec, so that [JavaPackage] is not normally needed? (This could map a
module called âdomâ to org.w3c.dom, and other modules at the top
A couple of questions I have after quickly looking over the WebIDL spec:
1. Although no mention is made of case-sensitivity in the spec, I assume that
all the tokens are case sensitive. Is this correct? By tokens I'm including the
names/values of the extended attributes (e.g. PutFowards,
On Thu, 17 Jul 2008 17:51:42 -0700, Jonas Sicking [EMAIL PROTECTED] wrote:
As for when the events fire (note that this is just clarifications of
the spec, not changes to it):
For events that fire after the mutation takes place I propose that we
add a concept of a compound operation and
On Tue, 15 Jul 2008 12:39:16 +0200, Sergey Ilinsky [EMAIL PROTECTED] wrote:
Specific concerns:
1) If DOMNodeRemovedFromDocument is fired after the mutation, then in
the listener for this event there is no way to know where Node was
removed from.
(This does not apply to
On Tue, 15 Jul 2008 11:20:17 -0400, Boris Zbarsky [EMAIL PROTECTED] wrote:
Kartikaya Gupta wrote:
The same problem applies to batching up mutations and firing them at the
end; there might be operations whose mutation events get discarded because
some other mutation happens to the tree
21 matches
Mail list logo
