| 05:21 | <zcorpan> | Domenic: https://wptserve.readthedocs.org/en/latest/pipes.html#sub |
| 05:23 | <zcorpan> | Domenic: simplest is to use .sub.html or .sub.js |
| 05:24 | <zcorpan> | <iframe src="http://{{domains[www1]}}:{{ports[http][0]}}/etc"></iframe> |
| 05:25 | <zcorpan> | Domenic: also http://testthewebforward.org/docs/ |
| 05:27 | <zcorpan> | http://testthewebforward.org/docs/test-format-guidelines.html#tests-involving-multiple-origins in particular |
| 05:28 | <zcorpan> | Domenic: also please avoid using any external servers like navigating to google.com |
| 09:28 | <Ms2ger> | Calling the DOM Living Standard "dom-ls" is... confusing :) |
| 10:15 | <jgraham> | Ms2ger: Wait, what? Who's doing that? |
| 10:15 | <Ms2ger> | CSS |
| 10:18 | <jgraham> | Oh, well then |
| 10:23 | <MikeSmit1> | zcorpan: https://github.com/validator/validator/issues/184#issuecomment-160922241 |
| 10:26 | <MikeSmit1> | about the message that's reported for stray p end tags caused by a p element with an implied end tag getting closed |
| 10:27 | <MikeSmit1> | I agree the message reported for that is suboptimal but not sure it's worth adding more complication to the parser error-reporting behavior to deal with it |
| 10:27 | <zcorpan> | MikeSmit1: this has been discussed before. iirc, my proposal was to keep track of implicitly closed tags, and give an info or warning about the last start tag with the same name when finding a stray end tag |
| 10:27 | <zcorpan> | and fix the message to not be confusing |
| 10:27 | <MikeSmit1> | ok yeah I vaguely recall this now |
| 10:28 | <zcorpan> | or maybe remember the thing that closed the p, i dunno |
| 10:30 | <MikeSmith> | well regardless I'm not gonna try to mess with it much for now but instead will wait to hsivonen lands the other lower-level parser change I think he's been meaning to make |
| 10:31 | <zcorpan> | <p><ul></ul></p>: Misnested tags! No open p element found. The last <p> start tag was here, it was closed by <ul> here |
| 10:31 | <MikeSmith> | yeah |
| 10:32 | <zcorpan> | maybe that sort of message can be useful in general: <div></div></div> |
| 10:36 | <MikeSmith> | hmm |
| 10:36 | <MikeSmith> | yeah, good point |
| 15:37 | <zcorpan> | suddenly, consensus |
| 15:38 | <jgraham> | ? |
| 18:51 | <ato> | Remind me again where I can find the codes available for use in ReSpec references? |
| 19:07 | <miketaylr> | ato: http://www.specref.org/? |
| 19:08 | <ato> | miketaylr: Merci! |
| 19:08 | <miketaylr> | de nada |