- From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
- Date: Thu, 14 Dec 2017 09:45:57 +0000
- To: public-css-archive@w3.org
If the question is "why can't we add this selector?" the answer is "because that's not how browsers work". If the question is "why don't we change how browsers work", we're going to need a separate discussion, and **very** substantive supporting arguments. I am not familiar ith EQCSS. Maybe it is a good proposal, and presenting it to browser vendors and the CSSWG could be a worthy endeavor, if you think it is possible to implement at reasonable cost and solves a sufficiently important problem (there's a balance between these two things). Please open a separate issue about that if you want to pursue it. Either way, **this** issue is not about EQCSS or some other way of overhauling browser architecture. It is about "can we have :overflowed-content?" And the answer, given the current state of browser architecture is that no, we cannot. -- GitHub Notification of comment by frivoal Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2011#issuecomment-351660204 using your GitHub account
Received on Thursday, 14 December 2017 09:46:02 UTC