The Khronos Group - a non-profit industry consortium to develop, publish and promote open standard, royalty-free media authoring and acceleration standards for desktop and handheld devices, combined with conformance qualification programs for platform and device interoperability.

If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

surely I cant be the only one having issues with chrome

This is hair pulling frustrating, this is an ongoing issue for months

firefox - never have issues

chrome - issues all the time dating back months, Ive had to firewall it from accessing the internet (which somehow it manages to find a way around) cause if its working with webgl, it will suddenly stop working an hour later, cause its installed a new (broken) version.

Ideally is there a place where I can find what the hells going on with chrome, something like thishttp://blog.chromium.org/ but with more frequent up to date info, also whats happening with their web audio api etc

Ive found this (& have posted there in the past) but I cant make sense eg surely theres gonna be a webgl forum there somewhere, is it just badly organized? or am I just nuts (dont answer that)http://code.google.com/p/chromium/issues/list

Re: surely I cant be the only one having issues with chrome

Posted here also (but no answers) http://code.google.com/p/chromium/is...etail?id=80731
Perhaps cause its not a bug, its not the appropriate forum, but their site is so confusing I cant work out where to ask.
Im trying to find how I can turn on debugging with chrome, this can can help me track down this bug

gl working
canvas.width = WIDTH; // this is screwing up the gl context
gl not working

I set it to 0,0 size so the user doesnt see an ugly black box when the apps loading (I could set it to 1,1 I suppose)

I guess what chrome is doing is, its creating the GLcontext & window etc OK (even with a 0,0 size) but later on
when canvas.width = 1000; (or whatever size the player wants) is called it does some checking & goes hey its currently sized 0,0, he doesnt actually want that since nothing will be visible, Ill be a nice boy and destroy it.