- From: Myles C. Maxfield via GitHub <sysbot+gh@w3.org>
- Date: Thu, 18 Apr 2019 18:46:37 +0000
- To: public-svg-issues@w3.org
This is an interesting idea. Is this really the only thing that requires the implementation to hold a DOM? This idea might not work very well with the OpenType use case because each glyph is represented by an element somewhere in the DOM with a magic `id` attribute. Therefore, holding a DOM is required to get O(1) access to an arbitrary glyph. Modifying an engine to not hold a DOM would require a fairly large architecture change in an engine that already holds a DOM. I believe there are already (at least) 3 engines that exist, and if they all hold DOMs, there may be some implementor pushback to that idea. Enforcing this constraint would make an existing DOM-based implementation more complicated, and if no one wants to update their engine's architecture, then it doesn't seem worth it. -- GitHub Notification of comment by litherum Please view or discuss this issue at https://github.com/w3c/svgwg/issues/669#issuecomment-484636898 using your GitHub account
Received on Thursday, 18 April 2019 18:46:38 UTC