- From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
- Date: Thu, 26 Aug 2021 03:23:38 +0000
- To: public-css-archive@w3.org
My comment above used to be in the pull request, but I moved it here since it's more a question about the general approach than about the details of the PR. Over there, @zcorpan said: > @frivoal that happens so rarely that I think it's a non-problem. The property behaves differently for different kinds of widgets, how would you define it without listing them? As far as I can tell, there's a generic logic which applies to most widget types, and a few are special cased. We can continue to define in the css spec what you do in those special cases, but frame the rest generically, and let HTML own the full list. Wouldn't that work? Potentially, we could even simplify further, as we don't seem to have many different types of special cases, but just two buckets: those where we care about authorProps and those where we don't. We could just define these two buckets here, and let HTML define the full list and say which widget goes in what bucket. -- GitHub Notification of comment by frivoal Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3526#issuecomment-906062642 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 26 August 2021 03:23:40 UTC