Bug 179772 - Artifacts left behind when animating objects without anti-aliasing turned on
Summary: Artifacts left behind when animating objects without anti-aliasing turned on
Status: RESOLVED CONFIGURATION CHANGED
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebGL (show other bugs)
Version: Safari 11
Hardware: Mac macOS 10.13
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-11-16 08:53 PST by Justin Biard
Modified: 2024-01-17 01:18 PST (History)
3 users (show)

See Also:

Attachments
Screenshot of the issue and fix with anti-aliasing turned on (51.55 KB, image/png)
2017-11-16 08:53 PST, Justin Biard 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Justin Biard 2017-11-16 08:53:04 PST 
Created attachment 327065 [details]
Screenshot of the issue and fix with anti-aliasing turned on

When following the introduction to Three.js located here (https://threejs.org/docs/index.html#manual/introduction/Creating-a-scene) on Safari 11.0.1 on macOS 10.13.1 there are pixel artifacts leftover in the canvas. Turning on anti-aliasing clears these artifacts and renders as expected. See attached screenshot for an example.

// This leaves screen artifacts in Safari (see attached screenshot)
var renderer = new THREE.WebGLRenderer();


// Fixes the issue in Safari
var renderer = new THREE.WebGLRenderer({ antialias: true });
Comment 1 Justin Biard 2017-11-16 13:03:18 PST 
Also worth noting that this was on a Late 2014 Mac Mini.
Comment 2 Kimmo Kinnunen 2024-01-17 01:18:27 PST 
Should be fixed now