- From: Noam Rosenthal via GitHub <sysbot+gh@w3.org>
- Date: Fri, 05 Jun 2020 10:04:44 +0000
- To: public-css-archive@w3.org
> @noamr again, it's not just overriding, it's also reading as linked above. There's various different ways this will end up being exposed. Sure, I meant reading/overriding - anything that enables reading directly or indirectly. > The tricky aspect is when metadata can be overridden, as it can be here. If the internal representation still has non-default metadata you would need to take that into account somehow. I.e., if an image was rotated 90 degrees and an API asked for it not to be rotated, it would have to remain rotated at 90 degrees. Model-wise that follows from the preceding paragraph, but in implementations that might be a bit trickier. I think that the overriding features in this case should be disabled for the opaque resource. E.g. CSS image-orientation would simply not apply, maybe even regarded as invalid style. I think that would be reasonable implementation-wise. -- GitHub Notification of comment by noamr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5165#issuecomment-639383158 using your GitHub account
Received on Friday, 5 June 2020 10:05:01 UTC