| 12:15 | <gsnedders|ooo> | I'd like to see some document of principles on specification. Like, "what do we do when we have complex behaviour that isn't interoperable but we don't expect to become interoperable in the short to medium term" |
| 12:16 | <gsnedders|ooo> | Because normally we'd revert new features if they didn't get implementation traction to stop the spec from being a lie, but when they're implemented everywhere but not interoperable it's much less clear. |
| 22:40 | <Alystair> | Who do I bribe to get an RFC for a CSS :visible pesudo-class, so one could do something like :visible:last-child without the assistance of JS? |
| 22:41 | <Alystair> | I have cake, and pie. |
| 22:44 | <TabAtkins> | Unfortunately, the laws of logic. |
| 22:46 | <TabAtkins> | Alystair: https://wiki.csswg.org/faq#selectors-that-depend-on-layout, but sub "depends on styling" in for "depends on layout". |
| 22:47 | <Alystair> | dang |
| 22:49 | <Alystair> | I guess that explains why :hover can create a repaint loop in some circumstances if you position your mouse just right :p |
| 22:50 | <TabAtkins> | Yup. |
| 22:51 | <TabAtkins> | Theoretically we could offer it in the snapshot profile, so querySelector() could use it, but that's it. |