| 02:53 | <domfarolino> | annevk: did there used to be a concept-request-context? |
| 03:18 | <domfarolino> | Ah, seems that it was the old request-destination |
| 15:47 | <nox> | Would you people be against patching tests which use named properties on Window (e.g. the getter that relies on id and name content attributes) so they explicitly call getElementById etc? |
| 15:47 | <nox> | We have various tests failing in Servo because of that, the tests ultimately time out and that takes time. |
| 15:53 | <annevk> | nox: yeah, I’d rather not have that effect blame and potential coverage |
| 15:54 | <nox> | annevk: I'm not sure if that's a yes or a no, and even if you reply with yes or no my question was formulated in such a convoluted way I'm not sure you are against me making the changes or not. :P |
| 15:56 | <annevk> | nox: against change |
| 15:56 | <nox> | annevk: Ok fair enough. |
| 15:57 | <nox> | annevk: Unrelated, can I mark http://w3c-test.org/css/css-transitions/transitions-animatable-properties-01.html as timeout=long? |
| 15:57 | <nox> | It times out in Servo, which is no good reason to do it, but it seems to time out elsewhere too (just tried on Safari and Firefox). |
| 15:58 | <nox> | (The indentation is so wild in that file hah.) |
| 16:03 | <nox> | annevk: https://github.com/servo/servo/blob/master/tests/wpt/web-platform-tests/css/css-values/support/vh_not_refreshing_on_chrome_iframe.html#L81-L89 What about this kind of test, where it uses both the named getter *and* getElementById for the same element? |
| 16:06 | <annevk> | I’d rather not have unneeded changes; the timeout one sounds reasonable though |
| 16:06 | <nox> | annevk: Ack. |