- From: Doug Schepers via GitHub <sysbot+gh@w3.org>
- Date: Sun, 21 Apr 2024 21:45:01 +0000
- To: public-svg-issues@w3.org
This seems pretty obvious to me. I can see no benefit to keeping the old behavior, and seriously doubt any existing content is using the old behavior. In any case, we should favor the utility for authors over mindless adherence to "backwards compatibility". There's historically been a lot of reluctance among browser vendors to change or improve their SVG implementations, but if that inertia can be overcome, I think this would be an excellent change (modulo the details to be worked out, of course). This is one of those cases where a small amount of work by standards and implementers could save authors and tools a disproportionate amount of work and frustration. -- GitHub Notification of comment by shepazu Please view or discuss this issue at https://github.com/w3c/svgwg/issues/941#issuecomment-2068210618 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 21 April 2024 21:45:02 UTC