Will <canvas> improve scalability and portability ?

Hi @anvaka , I found SVG implementation very handy, however, did you considered to support also rendering of graph on html5 ?

I thought that for expanded-on-demand graphs it would be a really good approach, for drawing only visibile elements on the canvas, instead of progressively adding new elements on the DOM.

Basically, I see graphs as a google maps, so that you can zoom on more details only on the portion you are interested in - perfect for exploring hair-balls.

Or do you have any particular reason for which you choose not to support ?

Possible to use the layout part to compute position of elements, and a new module for rendering of elements that check which are in the viewports and does the rendering ?

No files or tests are named. Start by reviewing the existing SVG rendering and layout portions referenced in the issue, then assess the proposed canvas renderer for drawing only visible elements in expanded-on-demand graphs. Done would require an agreed implementation scope and rendering approach.

Written by the indexing model from the issue text.