| 05:08 | <kochi> | MikeSmith: ping? |
| 05:09 | <kochi> | yoichio@ is having trouble getting his first PR merged. https://github.com/w3c/selection-api/pull/81 |
| 05:09 | <kochi> | Does it require "w3c" membership? |
| 06:30 | <annevk> | kochi: seemed rniwa gave some feedback? |
| 06:31 | <rniwa> | kochi, annevk: in fact, we don't want to merge that change until Blink makes the behavioral change |
| 06:31 | <rniwa> | I think I made that clear in the issue tracker? |
| 06:33 | <annevk> | rniwa: yeah, the referenced issue seems pretty clear, but sometimes worth restating the reqs in the PR |
| 06:33 | <annevk> | rniwa: tests would be good too btw |
| 06:34 | <annevk> | hsivonen: seems the Chrome encoding folks would be game to standardize sniffing |
| 06:35 | <annevk> | hsivonen: put it in Encoding? |
| 06:37 | <kochi> | annevk, rniwa: I see, I was just helping to resolve the warning that CI tool was complaining. Yoichi seems aware of it. |
| 06:57 | <yoichio> | Hi |
| 07:55 | <hsivonen> | annevk: I commented on the Chrome bug. I'd like to explore the necessity of sniffing before deciding whether to standardize and in which spec. |
| 08:00 | <annevk> | hsivonen: sg |
| 08:01 | <zcorpan> | https://twitter.com/mozilla/status/831983682256769024 ... is mozilla intentionally using single slash in URLs now? |
| 08:02 | <zcorpan> | uh... nevermind |
| 08:38 | <zcorpan> | Anyone have Edge more recent than 13 to test https://bugs.chromium.org/p/chromium/issues/detail?id=692560#c7 |
| 09:08 | <MikeSmith> | kochi: looking now |
| 09:08 | <kochi> | MikeSmith: thx! |
| 09:12 | <MikeSmith> | kochi: so from what I have seen so far the tool that handles the IPR check is just broken |
| 09:12 | <kochi> | hmm |
| 09:12 | <MikeSmith> | I will ask the team contacts for the WG if they know |
| 09:12 | <kochi> | thanks! |
| 09:14 | <kochi> | it's Friday, and that PR is not in a hurry. thanks in any case. |
| 09:17 | <MikeSmith> | OK |
| 09:17 | <MikeSmith> | will try to get it fixed, anyway |
| 09:20 | <kochi> | MikeSmith: if there is anything yoichio@ has to do, please let him know. |
| 09:22 | <MikeSmith> | ok |
| 09:22 | <MikeSmith> | but I think there here is nothing yoichio can to do resolve it; instead W3C systems team needs to fix the tool I guess |
| 09:25 | <annevk> | zcorpan: I can look in Browserstack |
| 09:25 | <zcorpan> | annevk: i thought BrowserStack had Edge 13 but not newer? |
| 09:26 | <annevk> | zcorpan: mine has 14 |
| 09:26 | <annevk> | zcorpan: object CSSStyleSheet, 1, loaded |
| 09:26 | <zcorpan> | annevk: thanks |
| 10:15 | <annevk> | foolip: the chromium-wpt-export-bot creates a lot of noise on the master commit log |
| 10:16 | <annevk> | foolip: e.g., the "Do not guess UTF8 encoding" commit is repeated eight or so times |
| 10:16 | <Ms2ger> | annevk, yeah, it was turned off |
| 10:16 | <annevk> | foolip: master commit log of web-platform-tests |
| 10:16 | <annevk> | Okay |
| 10:16 | <annevk> | (also, that commit seems wrong, seems better to just remove that test as it's invalid) |
| 10:16 | <Ms2ger> | http://logs.glob.uno/?c=w3%23testing#c12509 |
| 11:03 | <annevk> | mkwst_: I thought I suggested hiding nonces at some point |
| 11:04 | <annevk> | mkwst_: https://github.com/w3c/webappsec-csp/issues/65 |
| 11:36 | <zcorpan> | another anecdote that tests+bugs is working well (also cdumez++) https://bugs.webkit.org/show_bug.cgi?id=168358 |
| 12:38 | <annevk> | Anyone able to make alert(someWindow.location) return a javascript URL? |
| 12:56 | <zcorpan> | annevk: var alert = () => new URL('x:'); |
| 12:56 | <zcorpan> | :-P |
| 12:56 | <zcorpan> | Did not manage to break someWindow.location though |
| 12:57 | <annevk> | hah |
| 13:04 | <zcorpan> | maybe an attack could be to somehow confuse the script about what someWindow is |
| 13:05 | <annevk> | zcorpan: I wasn't really looking for an attack though |
| 13:06 | <annevk> | zcorpan: just a scenario where the Location object represents a javascript URL |
| 13:06 | <zcorpan> | oh a javascript:"something" URL. not an instance of window.URL |
| 13:07 | <annevk> | yeah |
| 13:08 | <annevk> | zcorpan: apologies if I just wasted a bunch of time due to a poor question |
| 13:08 | <Ms2ger> | I understood the question :) |
| 13:19 | <zcorpan> | annevk: this is about the check in .hash getter? |
| 13:20 | <annevk> | zcorpan: yeah |
| 13:27 | <zcorpan> | annevk: http://software.hixie.ch/utilities/js/live-dom-viewer/saved/4896 works in gecko. but seems like a bug per html standard |
| 23:31 | <KiChjang> | when reading the specs, i often come across notes that say something like "these (sub)steps are only done when ..." |
| 23:32 | <KiChjang> | does the note apply to the text above or below the note? |
| 23:52 | <jsbell> | KiChjang: do you have an example? That sounds like a pattern used in older specs, before we started using a more algorithmic style. |
| 23:53 | <KiChjang> | yes, one sec |
| 23:54 | <KiChjang> | jsbell, https://xhr.spec.whatwg.org/#dom-xmlhttprequest-send |
| 23:54 | <KiChjang> | step 10 |
| 23:54 | <KiChjang> | the part where it says "To process request body..." |
| 23:57 | <jsbell> | Ah... well, after staring at that one, that appears to refer to the preceding steps. That's a rather complex algorithm. |
| 23:58 | <jsbell> | We tend to have notes like that annotating what's above it. |
| 23:59 | <jsbell> | (Usually to decipher some complex normative text into something actually comprehensible.) |