| 01:01 | gsnedders | wonders how useful MSR's tooling around contracts is, is the static checker sound? |
| 01:01 | <gsnedders> | If it is, it could well be interesting to reimplement the parser. |
| 01:09 | <gsnedders> | Can someone hel with <https://github.com/html5lib/html5lib-tests/issues/78>;? I don't have the AAA paged in and have come to a completely nonsense conclusion |
| 06:29 | <annevk> | http://the-orbit.net/almostdiamonds/2012/02/28/dont-feed-the-trolls-is-bad-science/ interesting |
| 09:44 | <zcorpan> | MikeSmith: do you think html-markup/ could get a position:fixed warning? |
| 09:58 | <zcorpan> | MikeSmith: seems like checker.html5.org doesn't give an error for <p title="&=">, so no change needed for https://github.com/whatwg/html/pull/1220 |
| 10:22 | <zcorpan> | MikeSmith: found a bug though; &a{491}; |
| 10:22 | <zcorpan> | er |
| 10:22 | <zcorpan> | MikeSmith: found a bug though; &a{941}; is not a parse error |
| 10:22 | <zcorpan> | i.e. a very long entity |
| 10:54 | jgraham | wonders if anyone with a b.m.o account fancies doing a quick review of some test changes? |
| 11:12 | <nox> | annevk: Were some comments deleted from the URL issue? oO |
| 11:13 | <annevk> | nox: not by me |
| 11:14 | <nox> | annevk: Oh don't worry, wasn't implying this. :) |
| 11:14 | <nox> | annevk: I was trying to show the semantic web thing to a friend but it disappeared. :) |
| 11:15 | <annevk> | nox: https://github.com/mark-otaris seems to have disappeared from GitHub |
| 11:15 | <nox> | annevk: Hah. |
| 11:16 | <nox> | annevk: The weird thing is that usually comments are preserved and appeared as being written by 'ghost'. |
| 11:16 | <nox> | appear* |
| 11:18 | <annevk> | nox: according to the audit log this person did mutate their comments |
| 11:18 | <nox> | annevk: There is such a thing on GH? :O |
| 11:18 | <nox> | TIL. |
| 11:19 | <annevk> | nox: it's recent, for WHATWG we don't record the details of the events though, think you'd have to manually add something for that |
| 11:19 | <nox> | annevk: Oh like, through the webhooks or something like that? |
| 11:19 | <annevk> | nox: yeah, but we do have a log that says something happened |
| 11:19 | <nox> | Nice. |
| 11:23 | <annevk> | tyoshino: when do you think you'll have time to review the CORS change to allow * in more places? |
| 14:45 | <wanderview> | annevk: we does the fetch spec seem to say to add the Origin header all the time and not just for cross-origin CORS? that seems like a change |
| 14:47 | <annevk> | wanderview: Origin header is a mess :-/ |
| 14:47 | <annevk> | wanderview: there's various issues on figuring out when exactly it should be included |
| 14:47 | <annevk> | wanderview: sorry |
| 14:47 | <wanderview> | annevk: gecko only sets Origin header if CORS is in use and the request goes cross-origin |
| 14:47 | <wanderview> | annevk: is there an open spec issue? |
| 14:47 | <annevk> | wanderview: the specification attempted to match an additional case where Chrome would transmit the header for XSRF preventive purposes |
| 14:48 | <annevk> | but I failed capturing the semantics accurately |
| 14:48 | <wanderview> | I see this issue: https://github.com/whatwg/fetch/issues/225 |
| 14:48 | <annevk> | wanderview: see https://github.com/whatwg/xhr/issues/31 and various Fetch issues linked from there |
| 14:49 | <annevk> | wanderview: that works as an entry point too |
| 14:50 | <wanderview> | annevk: fwiw, this is the gecko bug I was trying to answer that led me to this stuff: https://bugzilla.mozilla.org/show_bug.cgi?id=1272302 |
| 14:50 | annevk | has been postponing opening that |
| 17:13 | <Domenic> | Looks like MS implemented a different notifications spec than Chrome and Firefox: https://blogs.windows.com/msedgedev/2016/05/16/web-notifications-microsoft-edge/ |
| 17:13 | <Domenic> | I guess Safari also implemented the W3C one? |
| 18:15 | <smaug____> | rbyers: do you happen to know why chrome is so inconsistent in what kind of mouse events are being dispatched to <select size=1> when opening and selecting some value from the popup? |
| 18:15 | <smaug____> | or just some random historical reasons |
| 18:33 | <rbyers> | smaug: I didn't know there was an issue but <select> is weird because it creates it's own OS-native window (to support overhanging the contents bounds) so it's probably just bugs as a result of implementation complexity. |
| 18:34 | <smaug____> | right. yeah, the dispatched events just depend on the OS |
| 18:34 | <smaug____> | Windows vs. Linux vs OSX being all different |
| 18:34 | <smaug____> | regarding mousedown/up/click events |
| 18:35 | <rbyers> | Yeah. There's related issues we're looking at for mouse event behavior across browser windows in different OSes - trying to get most consistency between platforms and browsers there. |
| 18:36 | <rbyers> | But I haven't personally looked at the <select> case in particular - feel free to file a bug and we can look into details |