| 15:16 | <Ms2ger> | MikeSmith, hey, https://w3c-test.org/resources/WebIDLParser.js has disappeared |
| 15:32 | <Ms2ger> | jgraham, any chance you can merge https://github.com/w3c/testharness.js/pull/13 ? |
| 15:51 | <jgraham> | Ms2ger: Seems like the wrongfix to me |
| 16:06 | <Ms2ger> | jgraham, got a better one? |
| 16:35 | <jgraham> | Ms2ger: I don't know what the bug is. Is it a problem with the tests or with the parser? |
| 16:35 | <jgraham> | (I didn't look) |
| 16:35 | <jgraham> | (and will have to go in a few minutes so don't plan to) |
| 16:35 | <Ms2ger> | The tests all rely on the old parser, not the new one |
| 16:36 | <Ms2ger> | And I'd rather not go and find them all to figure out if they need changes |
| 16:37 | <jgraham> | So I don't understand why the tests depend on a specific parser |
| 16:37 | <Ms2ger> | <script src=/resources/WebIDLParser.js></script> |
| 16:38 | <Ms2ger> | Changing that to refer to the new parser may or may not work |
| 16:38 | <jgraham> | Yeah well we should try that first at least |
| 16:38 | <Ms2ger> | But in either case, the new parser isn't available on http://w3c-test.org/resources/ |
| 16:38 | <jgraham> | Depending on old unsupported software is bad |
| 16:39 | <jgraham> | I guess we need to ci the new parser there |
| 16:39 | <jgraham> | Or make some sort of submodule if that will work |
| 16:39 | <jgraham> | Probably best to ask darobin |
| 16:40 | <Ms2ger> | Anyway, it'd be nice if introducing a new implementation didn't break every consumer |
| 16:41 | <jgraham> | YEs, well |
| 16:41 | <jgraham> | Maybe the new harness should have a more back-compatible API |
| 16:42 | <jgraham> | So we could just create a symlinkor something |
| 16:42 | <jgraham> | (no one runs windows, right? :) |
| 16:43 | <Ms2ger> | I don't :) |
| 16:44 | <jgraham> | But even just updating the filename would be easy if the function names didn't change |