Closed RSpace closed 5 years ago
@ngokevin Actually there's a big problem with how React initializes custom elements and how antialias is initialised that wasn't there in earlier versions of A-Frame.
When React encounters the <a-scene>
custom element, it first creates the element without passing the props in as attributes:
el = ownerDocument.createElement(this._currentElement.type);
Immediately after, it then sets the props as attributes:
this._updateDOMProperties(null, props, transaction);
However, the first line triggers the init
method in a-scene
, which looks for the antialias
attribute, which hasn't been set yet by React at this point:
I just want to be able to control if antialising it enable or not from the outside, in my A-Frame React app. Any suggestions?
antialias has moved to the renderer component in 0.9.0 coming soon, thanks!
I already added this once: https://github.com/ngokevin/aframe-react/pull/68/files
It was removed later in an unrelated refactor it seems. Need it back now :)