5 ms·
This is so awesome, and render beautifully in Firefox, but I can't seem to get the "orbs" (the actual objects) to render themselves in Chrome. Is anyone else ha
by mcescalante 11y ago
This is so awesome, and render beautifully in Firefox, but I can't seem to get the "orbs" (the actual objects) to render themselves in Chrome. Is anyone else having this difficulty? Disabled all blockers and everything.
- bpicolo 11y agoSame. Chrome didn't actually render the balls.
- rspeer 11y agoI see tiny little pulsating pixels in Chrome, which briefly show an orbit if you manage to mouse over their exact pixel. I was going to comment on the usability problem. EDIT: But now Chromium at least is doing fine.
- FigBug 11y agoRenders fine on my PC (Chrome 43), only renders the earth and anything I click on with my Mac (Chrome 43)
- girvo 11y agoChrome on OSX here, it originally rendered the orbs, but then once the Earth was rendered they disappeared.
- trhaynes 11y agoJust updated Chrome on OS X, no balls for me!
- sunnid 11y agoUsing Chrome on Linux works just fine.
- Kiro 11y agoThis reminds me that not only do you need to develop for different browsers, you also need to test the same browser on different operating systems. I can't count the amount of times Chrome has rendered stuff differently on PC and Mac (pure CSS things, don't even want to think about the differences in JS/WebGL).
- restalis 11y ago"you also need to test the same browser on different operating systems" Doesn't this denote a defect on the browser's part?
- kenbellows 11y agoRegardless of where the defect originates, if you want people to be able to use your product in different environments, you gotta test in different environments. The user won't care whether your product looks like crap because of a browser defect or because of a product defect; all they know is that it looks like crap. Of course, strike a balance; don't bother developing for IE6 on WinXP anymore.