587911 - Demos do not play.

Status: RESOLVED DUPLICATE of bug 586588

(Core :: Graphics: CanvasWebGL, defect, P1)

Description

[Gary [:streetwolf52]]

User-Agent:       Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b4pre) Gecko/20100816 Minefield/4.0b4pre
Build Identifier: 20100816142344

Loading the various demos results in nothing playing.

Partial Regression:

 http://hg.mozilla.org/mozilla-central/rev/34c42da84827 
     produced a crash

 http://hg.mozilla.org/mozilla-central/rev/022b9e8492a1
     console error messages with every nightly since and today's hourly.

Error: uncaught exception: [Exception... "Not enough arguments"  nsresult: "0x80570001 (NS_ERROR_XPC_NOT_ENOUGH_ARGS)"  location: "JS frame :: http://www.iquilezles.org/apps/shadertoy/effect.js :: createGLTexture :: line 17"  data: no]

Demos did work on 7/26/2010, the last time I ran them

Reproducible: Always




Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b4pre) Gecko/20100816 Minefield/4.0b4pre - Build ID: 20100816142344

Comment 1

[Alice0775 White]

Maybe duplication of Bug 586588

Comment 2

[Gary [:streetwolf52]]

(In reply to comment #1)
> Maybe duplication of Bug 586588

Sure looks like a dupe and the time frame of the API change is after the demos last worked for me.

How many sites are still using the old API which 4.0b4pre no longer support?  Does IE9, Chrome, Opera, etc allow the old API?  Unless the number of sites using the old API is very small why penalize the user?

Comment 3

[Benoit Jacob [:bjacob] (mostly away)]

(In reply to comment #0)
> User-Agent:       Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b4pre)
> Gecko/20100816 Minefield/4.0b4pre
> Build Identifier: 20100816142344
> 
> Loading the various demos results in nothing playing.
> 
> Partial Regression:
> 
>  http://hg.mozilla.org/mozilla-central/rev/34c42da84827 
>      produced a crash
> 
>  http://hg.mozilla.org/mozilla-central/rev/022b9e8492a1
>      console error messages with every nightly since and today's hourly.

These two changesets are not WebGL-related. If you still get the crash, please file a separate bug against the relevant component (I don't know which one it is); about the console error messages, you can always file a bug against the relevant component (Core/graphics) and the developer will tell you if this message is normal...

> 
> Error: uncaught exception: [Exception... "Not enough arguments"  nsresult:
> "0x80570001 (NS_ERROR_XPC_NOT_ENOUGH_ARGS)"  location: "JS frame ::
> http://www.iquilezles.org/apps/shadertoy/effect.js :: createGLTexture :: line
> 17"  data: no]

Indeed Alice has it right, replying to next comment...

Comment 4

[Benoit Jacob [:bjacob] (mostly away)]

(In reply to comment #2)
> (In reply to comment #1)
> > Maybe duplication of Bug 586588
> 
> Sure looks like a dupe and the time frame of the API change is after the demos
> last worked for me.

Indeed, dupe :-)

> 
> How many sites are still using the old API which 4.0b4pre no longer support? 

Unfortunately, lots of them still are; despite postings on the WebGL mailing list and blog posts on planet-webgl.org, well ahead of time, and despite coordination with other webGL implementers, see below;

> Does IE9, Chrome, Opera, etc allow the old API?

Chrome does no longer allow it. We made sure to be in sync. I'm not sure about Safari but since it shares this WebKit code, I would guess it's the same as Chrome. I don't know about Opera. As for IE9, they don't support WebGL at all.

> Unless the number of sites
> using the old API is very small why penalize the user?

This is an experimental, draft spec. For a while we've been supporting both the old and new APIs, to let websites adapt, but that meant quite crufty code on our part, so I think everybody was happy to be able to get rid of that.