Renderer warns about options.element when canvas is explicitely specified
See original GitHub issueWhen I create a new Renderer
by specifying the canvas
property and leaving the element
property empty, I get a warning saying:
Matter.js: Render.create: options.element was undefined, render.canvas was created but not appended
As far as I’m concerned, I do not see why we would specify element
if we are already telling it the canvas to use.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:4
- Comments:10 (3 by maintainers)
Top Results From Across the Web
Change default canvas size in matterjs - javascript
[Matter] warn: No "render.element" passed, "render.canvas" was not inserted into document. Which according to the docs: render.element ...
Read more >10 Rendering — HTML5 - W3C
An element is being rendered if it is in a Document , either its parent node is itself being rendered or it is...
Read more >The Script element - HTML: HyperText Markup Language
This attribute explicitly indicates that certain operations should be blocked on the fetching of the script. The operations that are to be ...
Read more >View API | Vega
A View instantiates a Vega dataflow graph and provides a component for visualization rendering and interaction. When initialized with a container DOM element, ......
Read more >Working with Plot and Renderers — HoloViews v1.15.3
The association between an Element or container and the backend specific ... like hv.render the hv.save function also allows specifying an explicit backend....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
yea I’m having the same issue
As far as I can tell, this has been fixed in edge release (0.14.1). Therefore, I’m going to close this issue. Thanks!