- From: Daniel Holbert via GitHub <sysbot+gh@w3.org>
- Date: Mon, 31 Jan 2022 22:53:25 +0000
- To: public-css-archive@w3.org
It's interesting to think about generalizing this to html and to iframes, however: (1) you can already sort-of solve this for html and iframes by simply communicating via `postMessage` and JS. (2) if we nonetheless were to generalize this feature to support html and iframes, then that would complicate or prevent the usage of the spec's current `#param()` syntax for encoding this information in the fragment identifier, since the fragment identifier might change if e.g. someone clicks an in-page link to scroll to an anchor further down in the iframe (and that's not great if that inadvertent in-page navigation causes a bunch of color-variables to be nerfed or changed). -- GitHub Notification of comment by dholbert Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6988#issuecomment-1026291486 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 31 January 2022 22:53:27 UTC