| 00:41 | <gsnedders> | is there any real guideline for www-archive anywhere? no? basically, don't be a dick and massively abuse it? |
| 00:41 | <gsnedders> | MikeSmith: ^^ |
| 00:42 | <Domenic> | isn't www-archive specifically where you want to archive precious moments of being a dick? |
| 00:44 | <gsnedders> | :) |
| 00:45 | gsnedders | has generally gone for some viewpoint of things being of interest to W3C members and participants being reasonable there |
| 00:47 | <Domenic> | Hmm yes it appears to be less hilarious than last time I checked it. |
| 01:06 | <MikeSmith> | gsnedders: no rules, it's a free-for-all |
| 01:07 | <gsnedders> | MikeSmith: bah, I know that, I was looking for some sort of guideline :P |
| 01:07 | <gsnedders> | like, at what point would it become abusive? |
| 01:08 | <MikeSmith> | at whatever point that might be, I reckon Bjoern has already crossed it |
| 01:09 | <MikeSmith> | So the point has moved |
| 01:09 | <MikeSmith> | But nobody's going to complain |
| 01:09 | <MikeSmith> | They have only themselves to blame if they're actually subscribed to it |
| 01:10 | <MikeSmith> | also DanC has used it for plenty of odd stuff over the years |
| 01:11 | <MikeSmith> | actually, the guideline is, it's for stuff that there's no other list you can think of where it seems appropriate for |
| 06:06 | <MikeSmith> | does Chrome stop showing all notifications from a particular origin if the origin has created an excessive number of notifications in some particular period of time? |
| 06:40 | <frewsxcv> | annevk: you can respond to me here if that's easier for you |
| 06:40 | <annevk> | frewsxcv: I don't understand why you think it gets set to itself |
| 06:40 | <annevk> | frewsxcv: it gets set to the next sibling of itself |
| 06:41 | <frewsxcv> | my last message was misworded. why does it get set to it's next sibling? |
| 06:43 | <frewsxcv> | or possibly: what does it mean for node.next_sibling == node? |
| 06:43 | <frewsxcv> | why is that ever desired? |
| 06:49 | <frewsxcv> | annevk ^ |
| 06:58 | <annevk> | frewsxcv: because of insertBefore |
| 06:59 | <annevk> | frewsxcv: which is used next |
| 07:03 | <frewsxcv> | hmmm okay. i'm probably overthinking this and need sleep. thanks for the help annevk_, sorry for the confusion |
| 07:03 | <annevk> | frewsxcv: let me know if it still doesn't make sense once you've had some sleep and we'll sort something out |
| 09:46 | <annevk> | Hmm, MikeSmith, not all W3C Staff has a Bugzilla account |
| 09:46 | <annevk> | MikeSmith: tried to add Wendy to https://www.w3.org/Bugs/Public/show_bug.cgi?id=28861 but that didn't work out |
| 14:48 | <wanderview> | MikeSmith: my impression was if a UI change was made in response to the notification, then chrome allowed them all through... so it just can't be a completely silent, behind the scenes operation |
| 15:16 | <wanderview> | annevk: what sets the content frame type defined in fetch? would that be where things integrate with fetch (but isn't spec'd yet)? |
| 15:16 | <annevk> | yup |
| 15:17 | <wanderview> | annevk: I'm trying to interpret this condition from navigation request context: "internal" (as long as context frame type is not "none") |
| 15:17 | <wanderview> | but its unclear to me what would provide a internal+none or internal+nested, etc |
| 15:18 | <annevk> | wanderview: internal+none would be something where the UA uses internal for something other than navigation |
| 15:18 | <annevk> | wanderview: for history or refresh or some such though there'd usually be a frame type |
| 15:19 | <wanderview> | annevk: forward/back/refresh would be "top level"? |
| 15:20 | <annevk> | wanderview: yeah, unless you activate them in an <iframe> |
| 15:21 | <wanderview> | annevk: I guess its safest to treat all "Internal" values as navigations for now |
| 15:41 | <Ms2ger> | "W3C Invites Implementations of XML Inclusions (XInclude) Version 1.1" |
| 16:16 | <mounir> | Ms2ger: does the interface here sounds valid per WebIDL: https://w3c.github.io/permissions/#permissions-interface |
| 16:17 | <Ms2ger> | Ugh, promises |
| 16:17 | <Ms2ger> | --> dinner, but nothing wrong pops out |
| 16:18 | <mounir> | Ms2ger: sequence<T> or T sounds good to you? |
| 16:19 | <MikeSmith> | annevk: I will encourage Wendy to create a bugzilla account |
| 16:21 | <MikeSmith> | wanderview: there is something funky that Chrome on OS X at least does in cases where a document at a particular origin has called a bunch of notifications in a short period of time |
| 16:22 | <MikeSmith> | it quits showing any notifications for that origin after that |
| 16:22 | <MikeSmith> | try http://w3c-test.org/notifications/notification-lang.html in Chrome |
| 16:22 | <MikeSmith> | and then reload it |
| 16:23 | <MikeSmith> | after reloading, the notifications won't appear any longer |
| 16:24 | <MikeSmith> | beverloo: in fact after loading that page once, if you try to navigate to any other documents at that origin which emit notifications, none of the notifications will be shown; e.g., http://w3c-test.org/notifications/notification-body-basic-manual.html |
| 16:25 | <MikeSmith> | But if I restart Chrome, it will then show the notifications as expected |
| 16:30 | <annevk> | mounir: not if T is a dictionary |
| 16:30 | <annevk> | mounir: as I explained to you before... |
| 16:31 | <mounir> | annevk: AFAIK, you said that you didn't know and I should check |
| 16:31 | <annevk> | So instead you put it in the spec? |
| 16:33 | <annevk> | mounir: seems like according to IDL dictionary cannot appear in a union |
| 16:34 | <mounir> | annevk: I prefer to have the spec expressing intent then fix errors |
| 16:35 | <Ms2ger> | mounir, well, there is something obviously wrong: it uses resped |
| 16:35 | <Ms2ger> | c |
| 17:35 | <mounir> | annevk: i'm pretty sure you are still going to be unhappy with it but you can have another look at the spec |
| 17:35 | <mounir> | annevk: I applied some changes you asked |
| 18:06 | <jsbell> | huh... did those new webstorage tests actually get... y'know... tested? |
| 18:08 | <MikeSmith> | jsbell: I think one of the Intel Crosswalk devs reviewed those |
| 18:09 | <MikeSmith> | Zhang |
| 18:09 | <jsbell> | MikeSmith: many of them hang/fail in both FF and Chrome, look like they're trying to do async tests w/ test() |
| 18:09 | <MikeSmith> | Ah geez |
| 18:10 | <MikeSmith> | Is this an open PR? |
| 18:10 | <jsbell> | it was merged |
| 18:10 | <MikeSmith> | Zhang merged it? |
| 18:10 | <jsbell> | jgraham I think? |
| 18:10 | <jsbell> | Just noticed, I was going to import that directory into Blink. |
| 18:11 | <MikeSmith> | ok, I'll check on it |
| 18:11 | <jgraham> | I did what now? |
| 18:11 | <MikeSmith> | oh jgraham still awake |
| 18:12 | <jsbell> | While you two are here... https://critic.hoppipolla.co.uk/r/5424 |
| 18:12 | <jgraham> | It's only 19:10 here, my jetlag isn't that bad :) |
| 18:13 | <jgraham> | jsbell: BTW I landed an import of the blink serviceworker tests in the gecko tree in the hope that people will pay them more attention if they are there and exposing bugs (which they are) than if they are hypothetical |
| 18:13 | <jgraham> | Once people are happy that they're right, I'll move them so they get upstreamed |
| 18:13 | <jsbell> | jgraham: (context for the above^^) several of the new webstorage/ tests (event_basic.html, event_body_attribute.html, event_case_sensitive.html, ...) appear to be buggy. |
| 18:13 | <jsbell> | jgraham: awesome! |
| 18:14 | <jgraham> | I don't recall reviewing those, but I might have |
| 18:14 | <jsbell> | Ah, it was Zhang. |
| 18:15 | <jgraham> | jsbell: re: moving things into resources/ directories, I think it's OK, but not a good idea to require it (I already had this conversation with someone on a different bug) |
| 18:15 | <jgraham> | The canonical source of information for what's a test is the manifest file |
| 18:18 | <jgraham> | (I have to leave in a minute, so I don't think I'll get through that review) |
| 18:18 | <jsbell> | np |
| 18:19 | <jsbell> | jgraham: I'll make a note that we (Blink) should generate/follow MANIFEST.json |
| 18:44 | <wanderview> | jgraham: I liked at a couple of them... the one I remember was a bug in firefox |
| 18:46 | <jgraham> | wanderview: Too much facebook? ("liked" ;) |
| 18:47 | <wanderview> | oh... looked |
| 18:47 | <wanderview> | something, something, jet lag |
| 18:47 | <wanderview> | which is weak since I only have a 3 hour time difference |
| 18:47 | <jgraham> | Heh |
| 18:50 | <jsbell> | Ugh, yeah, those imported webstorage tests are just borked. Need to be one big async_test() not several nested test()s (I mean, w/o rewriting from scratch) |
| 19:26 | <Ms2ger> | jsbell, wow, those are curiously written tests :) |
| 19:28 | <Ms2ger> | storageEventList = new Array(); |
| 19:28 | <Ms2ger> | iframe.contentWindow.onstorage = function (e) { |
| 19:28 | <Ms2ger> | window.parent.storageEventList.push(e); |
| 19:29 | <Ms2ger> | I'm not sure that does what it thinks it does |
| 20:22 | <Ms2ger> | jsbell, r? https://github.com/w3c/web-platform-tests/pull/1954 |
| 21:00 | <jsbell> | Ms2ger: looking |
| 21:06 | <jsbell> | Ms2ger: lgtm, trying to remember how to do that in critic... |
| 21:07 | <jsbell> | Ms2ger: do you have to add me as a reviewer? |
| 21:08 | <TabAtkins> | jsbell: Just click on everything until something happens. |
| 21:09 | <jsbell> | [].slice.call(document.all).forEach(e => e.click()); right? |
| 21:15 | <wanderview> | JakeA: trained-to-thrill installs an impressive number of node modules |
| 21:18 | <jsbell> | Ms2ger: ah, there we go, added myself |
| 21:28 | <jsbell> | Ms2ger: ISTM the storage_*_window_open.html tests that navigate themselves to storage_*_window_open_second.html need to be recast in terms of iframes... ? |
| 21:49 | <JakeA> | wanderview: for the build perhaps. But that's the way of node, lots of one-job micro libraries |
| 21:52 | <wanderview> | yea |
| 22:16 | <caitp> | so does anything actually use [ArrayClass] anymore, or would implementing that be basically dead code |
| 22:25 | <jsbell> | Ms2ger: https://critic.hoppipolla.co.uk/managereviewers?review=5428 |
| 22:31 | <caitp> | I guess gecko uses it for DOMRectList and some other things, so maybe it's not totally useless? |