- From: Steve Orvell via GitHub <sysbot+gh@w3.org>
- Date: Thu, 02 Aug 2018 17:27:44 +0000
- To: public-css-archive@w3.org
I think web developers generally prefer to set properties rather than attributes in imperative code. It's more straightforward since we need to know less about the underlying system (oh, this thing is only settable via attribute...). I don't feel like the `classList` like analog is needed for `partmap` right now, and it also seems easy to add later if we want. Therefore, simply reflecting to string seems simplest to me. That said, the `class` and `className` and `classList` seems like a reasonable precedent, if not the prettiest, for how to handle this. I wonder if *part* of the concern stems from the word "map" in `partmap` since that feels like it should reflect to something more like `classList`. What if we did something like change `partmap` to `forwardedparts` and reflect that to `forwardedPartsName` and then that leaves room more easily to add `forwardedPartsMap` in the future? If this seems like an ok compromise we can obviously massage the names =). -- GitHub Notification of comment by sorvell Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2414#issuecomment-410005571 using your GitHub account
Received on Thursday, 2 August 2018 17:28:27 UTC