| 00:50 | <0x4261756d> | Hi, several new html syntax parsing tests (for example the last 4 in plain-text-unsafe.dat introduced in commit e45db0ba20 or all the tests in processing-instructions.dat) break the README's requirement that "Then there must be a line that says "#errors"" because they don't have an #errors-section. |
| 09:28 | <Noam Rosenthal> | I'll see if I can prepare a fix for this, thanks for reporting |
| 09:40 | <Luke Warlow (back on the 18th)> | Ha I didn't know about this restriction. Isn't it easy to circumvent it in CSS with scroll timeline anyway? |
| 09:47 | <Noam Rosenthal> | Sure you can https://codepen.io/noamr/pen/NPdBvRN |
| 09:49 | <Noam Rosenthal> | https://github.com/web-platform-tests/wpt/pull/61436 |
| 10:12 | <Luke Warlow (back on the 18th)> | Well that seems like it shouldn't have been allowed per the lazy loading decision? Is that fixable? Or I guess if not we should imo just lift the restrictions on lazy loading images. |
| 10:13 | <Noam Rosenthal> | I think we'll find quite a few of these features that allow CSS to scroll-spy and I don't think anyone ever discussed guarding them with "JS is enabled" |
| 10:17 | <Noam Rosenthal> | ... it's a good discussion to have though. Not sure if enough people that are important to this discussion are actually at work in the next 4 weeks or so though :) |
| 10:57 | <Noam Rosenthal> | ... This can actually be a good topic for TAG to come up with a consensus definition of what the scope of "scripting is disabled" should be |
| 13:59 | <Noam Rosenthal> | ... This can actually be a good topic for TAG to come up with a consensus definition of what the scope of "scripting is disabled" should be |
| 14:31 | <0x4261756d> | nice, thanks! |
| 14:36 | <bkardell> | is there a link to somewhere where it says more? I am having trouble parsing this |
| 14:54 | <Dominic Farolino> | https://crbug.com/526451590 |
| 14:54 | <Dominic Farolino> | Thanks for filing that, Noam! |