[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Public WebGL] Proposed change to WebGL Event definition
- To: Chris Marrin <email@example.com>
- Subject: Re: [Public WebGL] Proposed change to WebGL Event definition
- From: Kenneth Russell <firstname.lastname@example.org>
- Date: Tue, 19 Oct 2010 10:22:57 -0700
- Cc: public webgl <email@example.com>
- Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1287508979; bh=EwDfj67hQfEJo1k30uiGjH7AMjI=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type:Content-Transfer-Encoding; b=aJOoBwl1kd1KGpk0QEyxPScV0XJq7VwOoek35FIGaomH6LGCZkf9wxaZGq6WEGYsC lmldIwjPOfkT1kCjxuGfw==
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=eBkcYeCbRmXCscJjOV6jtlpQXsKpFqbYCZs8JTRL5HE=; b=FnuhM3Q7+Ci+kxZMomdWO5+mCkXygr8Vc6/uE13VHemC+LjaAItxWNjj7yUzK4TW0T 91AtZ+AgTt43xLeRHCvQ==
- Domainkey-signature: a=rsa-sha1; c=nofws; d=google.com; s=beta; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=LImMET9RBIlBnXeHS7psFs+gSum5eOZ+77mTmUYIRi6zb9IVJCqBio0PPoQ1fxhBSI nuEfQUIHcRIFygzA5Zgg==
- In-reply-to: <044681C5-76B1-4D4B-AF5C-4BD34203350B@apple.com>
- References: <33F15A1B-FF87-44F1-ABA3-632494FA649A@apple.com> <AANLkTikLAH9-fhr0qmsjUnZLyMxwGT4pkq69GO8smQfirstname.lastname@example.org> <817D1DD8-125C-44B0-95FF-C288EECB06E0@apple.com> <AANLkTikbe2Rd5-EvxyXjdjruFVgNrayhy2CcVAdgr967@mail.gmail.com> <BAB0DBAA-252E-41CB-A41F-9ABD93248AAC@apple.com> <AANLkTimjbRTS_N2UXja9JRgqX-7AxnA2Rvset-v1j-X9@mail.gmail.com> <10C92111-C1E5-429F-AF48-D4737C07BCEE@apple.com> <FE76D408-FDF8-4CB1-9BB0-4AEC13C9DC49@apple.com> <AANLkTi=qSet-f=Wy99Wqcghfedp8+98K70d632xQbuZemail@example.com> <AANLkTi=dwwjBO5mPz_2PJGyHY2gfR6qQCK5abcT7HrFy@mail.gmail.com> <044681C5-76B1-4D4B-AF5C-4BD34203350B@apple.com>
- Sender: firstname.lastname@example.org
On Sat, Sep 4, 2010 at 6:57 AM, Chris Marrin <email@example.com> wrote:
> On Sep 3, 2010, at 10:08 PM, Cedric Vivier wrote:
> On Sat, Sep 4, 2010 at 09:40, Kenneth Russell <firstname.lastname@example.org> wrote:
>> On Fri, Sep 3, 2010 at 10:16 AM, Chris Marrin <email@example.com> wrote:
>> > I've revised the event section (5.14). Please review.
>> Sorry for not realizing this before, but the "NOT_AVAILABLE" status
>> code seems pretty useless, because if the web browser is so old that
>> it doesn't support WebGL, then it definitely won't support delivery of
>> the webglcontextcreationerror event.
> NOT_AVAILABLE "WebGL is not implemented or not enabled in this browser"
> I think the current meaning is confusing (and indeed useless).
> IIRC the original planned intent for this status code, meaning should be
> something like :
> "WebGL is currently disabled or temporarily unavailable because of high
> resource usage by other tabs/programs."
> I think that's another status code. Perhaps reasons for failure are:
> - WebGL is not implemented (the event will never fire)
> - WebGL is disabled by the browser
> - WebGL is disabled by request of the user
> - Hardware is insufficient for running WebGL content
> - System is unable to run WebGL content because of other system constraints.
> Maybe it is a bad idea to have status codes. There could be many more
> reasons for not being able to use WebGL content. So maybe we should do as
> Ken suggests and only have a status message. That way the user agent can put
> any necessary recommendations into the string. The browsers would have L11N
> issues, but that is probably manageable.
> The unfortunate thing is that, if you don't have WebGL support at all, this
> event will never fire. You will simply get a null return from getContext().
> You' have to set up a timer and if it fires without any event being
> generated you know you don't have WebGL. That's a hack.
> I think the right way to handle that is to add a media query for WebGL.
> We've made a proposal to add media queries for CSS animations, transitions,
> and transforms. These are all supported in WebKit today. It would be easy to
> add one for 'webgl'. You can run the query from JS and know you don't have
> WebGL without having to call getContext(). But the really nice thing about
> media queries is that you can use them in CSS style sheets. If WebGL is
> missing you can style the page differently for, for instance, not take up
> the space for the WebGL canvas.
> So the proposal is to get rid of statusCode and add a media query for
> 'webgl'. I will talk to dino, who is pushing the media query extensions
> spec, about this as well.
Resurrecting this thread. I would like to remove the status codes from
WebGLContextEvent for the reasons I cited earlier. Are there any
objections to my doing so?
You are currently subscribed to firstname.lastname@example.org.
To unsubscribe, send an email to email@example.com with
the following command in the body of your email: