Not sure if this is the same issue as the year old fonts not working but In chrome I never get readable text and got it once in Firefox but then no more.
No errors in the nodejs server so I think its something on the browser, Chrome has some messages in the console:
WebGL: INVALID_VALUE: enableVertexAttribArray: index out of range
WebGL: INVALID_VALUE: vertexAttribPointer: index out of range
Firefox has none.
Using the following browsers:
Version 43.0.2357.65 (64-bit)
Firefox 38.0
on Fedora 20.
======Some more info=======
Works "fine" if I start a new firefox profile: firefox -new-instance -p
After a reboot I noticed it works in my default profile until I reload it. Maybe something to do with plugins installed (firebug maybe). but starting a fresh new profile fixed it. Reloading won't break it either.
Please let me know if I can be of any assistance, this looks like a valuable tool as it can "record" what your code does and inspect it later with some information about local variables and code flow.
Not sure if this is the same issue as the year old fonts not working but In chrome I never get readable text and got it once in Firefox but then no more.
No errors in the nodejs server so I think its something on the browser, Chrome has some messages in the console: WebGL: INVALID_VALUE: enableVertexAttribArray: index out of range WebGL: INVALID_VALUE: vertexAttribPointer: index out of range Firefox has none.
Using the following browsers: Version 43.0.2357.65 (64-bit) Firefox 38.0 on Fedora 20.
======Some more info=======
Works "fine" if I start a new firefox profile: firefox -new-instance -p
After a reboot I noticed it works in my default profile until I reload it. Maybe something to do with plugins installed (firebug maybe). but starting a fresh new profile fixed it. Reloading won't break it either.
Please let me know if I can be of any assistance, this looks like a valuable tool as it can "record" what your code does and inspect it later with some information about local variables and code flow.