- From: Satoru Takagi via GitHub <sysbot+gh@w3.org>
- Date: Mon, 12 Nov 2018 07:42:14 +0000
- To: public-svg-issues@w3.org
@dirkschulze In the context of svgwg, the forked gecko implementation does not satisfy the requirements of svgwg. By the way, where is the requirement stated? Well, I remember that this specification was created based on the task of listing requirements for SVG 2 when most browser vendors participated, but unfortunately the current browser vendor's The situation seems to have changed. As you can see from the discussion in bugzilla, this seems to be falling into a chicken or egg dilemma. This situation does not seem to change as long as multiple implementations with polyfill or authoring tool do not meet the requirements. At least we feel that contributing by native implementation to browsers is no longer difficult. -- GitHub Notification of comment by satakagi Please view or discuss this issue at https://github.com/w3c/svgwg/issues/306#issuecomment-437785249 using your GitHub account
Received on Monday, 12 November 2018 07:42:20 UTC