- From: Brian Birtles via GitHub <sysbot+gh@w3.org>
- Date: Thu, 12 Apr 2018 13:53:15 +0000
- To: public-css-archive@w3.org
Discussed on 2018-04-12: * We prefer the simplicity of always parsing using current realm document from when the `KeyframeEffect` was created. * Can't target non-secure context from secure context * Would prefer to be able to target content in iframes (birtles thinks this is common) * Need to spec if we use quirks mode or not (birtles thinks Firefox might match the mode of the document of the current realm of the KeyframeEffect) -- but it doesn't have a big impact on quirks mode, basically supporting unitless lengths or not. Probably prefer to require always parsing in strict mode. * For custom properties there is a potential mismatch between the set of allowed values in different contexts (depending on where the property is registered and with what type). * One optional is for implementations to store the original string for custom properties and re-parse when the document of the target element changes and produce a suitable console warning at that point. * flackr would strongly prefer we just parse using the original context and if different documents define different types for properties then the value becomes invalid in the new context. -- GitHub Notification of comment by birtles Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2366#issuecomment-380812881 using your GitHub account
Received on Thursday, 12 April 2018 13:53:17 UTC