- From: Stephen Chenney via GitHub <noreply@w3.org>
- Date: Thu, 28 May 2026 15:15:13 +0000
- To: public-svg-issues@w3.org
I've filed and issue with the CSS WG and included the potential ways to address the problem. https://github.com/w3c/csswg-drafts/issues/13976 To repeat, I see at least 3 options: (a) Always apply image orientation EXIF data in <feImage> (b) Use the CSS image-orientation property from the element with the filter property for that instance of the filter. (c) Define an attribute on <feImage> to control the orientation (analogous to the CSS property). Option (b) is messy to implement in Chrome but could be done. I prefer option (c) because it is very obvious in how it applies and would be consistent across instances of the filter. I have implemented option (a) in Chrome to fix the privacy problem but the web-compat issues may force a roll-back. Once it makes it onto the CSS agenda we should be able to decide on the preferred behavior and then I can draft the Spec for discussion here. So maybe remove the Agenda+ until CSS handles it. Or we can resolve it here and let CSS follow along. In particular, I'm curious what the SVG community thinks about option (c), the attribute approach. -- GitHub Notification of comment by schenney-chromium Please view or discuss this issue at https://github.com/w3c/svgwg/issues/819#issuecomment-4565532924 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 28 May 2026 15:15:14 UTC