- From: Ryosuke Niwa via GitHub <sysbot+gh@w3.org>
- Date: Fri, 28 Sep 2018 23:57:25 +0000
- To: public-css-archive@w3.org
> > Also, I would tend to try to keep the part mapping syntax close to the desugaring syntax in javascript, so I'd voice a weak preference for part="keepAlike, oldName:newName" and by extension oldName-:newName-. I do see very valid use cases for exposedparts to perform prefixing operations for sub-components, I'd strongly suggest to keep this in v1. > Ooh, that's a pretty reasonable critique. While I do often find myself having to think for a moment to remember the correct ordering for destructuring, having CSS use a related syntax at least means that I'd only have to learn this once. @fergald , @rniwa, what do y'all think? Yeah, @grorg and I had some discussion today, and came up with almost identical syntax with `exportparts' content attribute. So it would read like `<sub-component exportparts="a:b c"` would mean that exporting the part "a" defined in the subcomponent as part "b" of this component, and forward-declare "c". I think that's probably the best syntax we've come up with so far. -- GitHub Notification of comment by rniwa Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2368#issuecomment-425596891 using your GitHub account
Received on Friday, 28 September 2018 23:57:26 UTC