- From: Rob Eisenberg via GitHub <sysbot+gh@w3.org>
- Date: Thu, 26 Sep 2024 01:09:02 +0000
- To: public-css-archive@w3.org
I would hesitate to call the attribute `export` without exploring a few other things we might want to do in the future. For example, there are a bunch of PoCs for HTML modules and some of them propose using the `export` attribute to indicate what should be exposed from the module. Maybe the same attribute can be used, and the browser can figure it out based on context. I don't know enough about HTML parser implementations to know whether that's possible or would be considered acceptable. I'd like to keep the broader modularity story of HTML in mind while working through this though, if only to make sure we don't end up painting ourselves into a corner and then have to do something very strange for HTML modules. -- GitHub Notification of comment by EisenbergEffect Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10939#issuecomment-2375538972 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 26 September 2024 01:09:03 UTC