| 01:27 | <annevk> | Domenic: yup |
| 04:46 | <Domenic> | Oooh, nightly servo builds now available on Windows |
| 04:49 | <Domenic> | Well, all that multithreaded GPU rendering fanciness did jack shit on the singlepage HTML spec ^_^ |
| 04:50 | <MikeSmith> | haha |
| 04:51 | <MikeSmith> | funny benchmark we have |
| 08:16 | <hsivonen> | MikeSmith: yeah, closing it is one of the things I naive thought I had time for this spring |
| 08:16 | <hsivonen> | MikeSmith: would migrating the open bugs to github be useful or spammy? |
| 08:19 | <hsivonen> | MikeSmith: I added a link to GitHub and closed Bugzilla for new bug entry. |
| 08:20 | <hsivonen> | s/naive/naively/ |
| 08:48 | <MikeSmith> | hsivonen: super, thanks |
| 08:49 | <MikeSmith> | Yeah I don't think there's much value in migrating the existing open issues |
| 08:49 | <MikeSmith> | most are basically just stale at this point, I think |
| 10:46 | <hsivonen> | MikeSmith: ok |
| 10:47 | <annevk> | MikeSmith: do you still use WPT for conformance tests? |
| 10:55 | <MikeSmith> | annevk: yes |
| 10:55 | <annevk> | kk |
| 10:56 | <annevk> | (asking cause of some seemingly stale url-labeled issues I found, but I'm not bothered by them or anything) |
| 10:57 | <MikeSmith> | ah OK |
| 17:21 | <MikeSmith> | Domenic: about the deploy.sh find invocation I think we could just add -quit |
| 17:21 | <MikeSmith> | hmm but not sure if that’s a GNU-only thing |
| 17:30 | <MikeSmith> | just tested and it works on BSD too |
| 17:30 | <MikeSmith> | MacOS |
| 17:30 | <MikeSmith> | need to add -print too |
| 17:30 | <MikeSmith> | find . -name "*.bs" -print -quit |
| 17:50 | <Domenic> | MikeSmith: ah cool, makes sense. I get the sense that maybe there's a more targeted tool than find, but find works too |
| 17:50 | <TabAtkins> | What you doing with that? |
| 17:52 | <MikeSmith> | TabAtkins: the context is https://github.com/whatwg/resources.whatwg.org/pull/52#pullrequestreview-32685441 |
| 17:52 | <MikeSmith> | common deploy script for whatwg specs |
| 17:53 | <MikeSmith> | goal is to find the *.bs file regardles of the basename, and get the title from it |
| 19:24 | <Domenic> | zcorpan: smaug: I'm a little confused by https://github.com/whatwg/html/issues/2464. Isn't the question of tab-vs.-window a UI question outside the scope of the spec? |
| 19:25 | <smaug> | I don't think so. blink making 'toolbar' somehow special could break other browsers if pages start to rely on that |
| 19:26 | <smaug> | but yes, in general the window vs tab is probably out of the scope |
| 19:39 | <Domenic> | smaug: how would it break other browsers? what tests could authors write that would succeed in blink and fail elsewhere? |
| 19:44 | <smaug> | Say window.open("about:blank", "", "toolbar,width=400,height=400"); Site could start relying on blink's behavior(, which is rather weird given that size is actually provided). The site would feel broken in other browsers |
| 19:44 | <smaug> | s/about:blank/<some reasonable url>/ |
| 20:05 | <Domenic> | smaug: my question is how sites could rely on Blink's behavior. What's detectable about it? |
| 20:05 | <smaug> | opening a new tab in a "main window" vs. opening a new window with specified size is quite different |
| 20:07 | <smaug> | and detecting that, just check what kind of window was opened |
| 20:07 | <smaug> | like check its size |
| 20:12 | <Domenic> | ok, size, i see. thanks. |
| 20:13 | <Domenic> | although i still am doubtful that web developers could write non-interoperable code based on window sizes being different |
| 20:13 | <Domenic> | given that they have no idea what the size of the browser window is anyway |
| 20:13 | <Domenic> | s/no idea/no control over/ |
| 20:23 | <smaug> | they do have control of the size of the opened window |
| 20:23 | <smaug> | on desktop |
| 20:56 | <Domenic> | But not of any other window |