- From: Anne van Kesteren via GitHub <sysbot+gh@w3.org>
- Date: Thu, 17 Jan 2019 15:43:42 +0000
- To: public-css-archive@w3.org
What I'm worried about is that on the HTML side we'll have this thing where we branch on element (and its attributes) and decide on a render algorithm. This render algorithm might then further branch on appearance. On the CSS side we might use appearance to decide on a render algorithm for the remaining elements. That feels a little circular and depending on how you resolve it you either end up with the Chromium or Firefox behavior. I guess what you want is some kind of algorithm that takes in the element and its set of properties, and then returns what kind of thing to render. However, that means CSS ends up depending on some HTML-specific thing or we'd define the whole thing in HTML. -- GitHub Notification of comment by annevk Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3526#issuecomment-455218506 using your GitHub account
Received on Thursday, 17 January 2019 15:43:43 UTC