For example, on a page like this one, in Safari 7 it's antialiased, but in Firefox 29 (OS X 10.9) it's not.
Firefox does seem to have the capability to antialias. If I set the about:config setting "webgl.msaa-force" to "true", then it is antialiased.
Is there any way to make Firefox antialias for my particular webpage, without relying on the user to mess with their about:config?
I'm using three.js, and it has an "antialias" flag, but it seems to only make a difference on Safari, not Firefox.
If WebGL is disabled in Firefox it may be because your video drivers need updating.
In WebGL anti-aliasing is a request, not a requirement Ideally detecting if antialiasing is enabled should be possible with WebGL context`s antialias property. So if antialias === true antialiasing would be considered to be on. However, it is not as simple as that.
The short answer is "no".
It's up the browser whether or not to support anti aliasing. Many drivers crash with antialiasing under certain conditions so browsers often disable antialiasing on those machines.
Note that the antialias
flag is true
by default. In other words the default for WebGL is to antialias though it's still up to the browser. Specifically setting antialias
to true
could at most act as a hint (hey, I really want antialiasing please) but I know of no browsers that use it as a hint. They generally turn antialiasing on if they can.
On the other hand, setting antialias
to false
does specifically mean "do NOT antialias".
You can try to do anti-aliasing yourself. For example you can render at a higher resolution and using CSS to display the canvas smaller in which case the browser will most likely bilinear interpolation when compositing your WebGL into the page. You could also render to a texture and then apply some kind of anti-aliasing filter to it when rendering it to the canvas.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With