| 00:00 | <zewt> | well, defining the name by itself is meaningless |
| 00:01 | <zewt> | http://www.w3.org/TR/DOM-Level-3-Events/#event-type-mouseleave but yeah, this needs a redo badly some day |
| 00:01 | <zewt> | the basic indexing of those specs is totally wrong--listing by event names and when they're fired, instead of listing by actions that take place and the events that are fired when they happen |
| 00:01 | <zewt> | the whole thing's inside out |
| 00:01 | <zewt> | (yeah, I know I don't need to convince you of this, heh) |
| 00:03 | <Hixie_> | yeah i was gonna say :-) |
| 00:03 | <GPHemsley> | Hixie_: These DOM 3 events are the ones that need speccing? |
| 00:04 | GPHemsley | wonders why mouseover is supposed to fire before mouseenter |
| 00:05 | <zewt> | does cancelling mouseover prevent mouseenter? |
| 00:06 | <GPHemsley> | no idea |
| 00:06 | <GPHemsley> | I'm just reading the DOM 3 Events list |
| 00:06 | <zewt> | no idea either, just a hypothesis :P |
| 00:06 | <GPHemsley> | 5.2.3.2 Mouse Event Order |
| 00:07 | <zewt> | i like how those lists aren't even normative |
| 00:07 | <zewt> | it's just "eh well it's sorta like this:" |
| 00:08 | <GPHemsley> | mostly because you're supposed to already *know* that (duh) from each event type's definition |
| 00:08 | <Hixie_> | GPHemsley: these events are what need speccing. I wouldn't call them "DOM 3 events", they were invented before the W3C had a DOM WG. (Possibly before the W3C existed.) |
| 00:09 | <zewt> | Hixie_: well, most of them anyway |
| 00:09 | <GPHemsley> | Hixie_: Oh, well, that spec is called "DOM 3 Events" :P |
| 00:09 | <Hixie_> | GPHemsley: as zewt says, though, it's not so much the events that need speccing, as the reaction to mouse movements, clicks, etc. Which happens to involve firing events with these names, but that's the effect, no the cause. |
| 00:09 | <zewt> | GPHemsley: the event descriptions don't say anything about relative order, do they? |
| 00:10 | <GPHemsley> | zewt: I haven't read them, but I think the idea is that you infer the order from the definitions. |
| 00:10 | <zewt> | http://www.w3.org/TR/DOM-Level-3-Events/#event-type-mouseover well, this doesn't seem to say anything about its relative order to mouseenter, or vice versa, at least |
| 00:10 | <GPHemsley> | Hixie_: Ah, so it's not a Mouse Events spec is a Mouse Interaction spec. |
| 00:10 | <GPHemsley> | s/ is/, it's/ |
| 00:11 | <zewt> | UI interaction, mouse events just being an important part |
| 00:12 | <zewt> | (keyboard events are nasty too, of course) |
| 00:12 | <zewt> | are touch events specced anywhere? those are important now, too |
| 00:12 | <GPHemsley> | hmm |
| 00:13 | <zewt> | and they interact with mouse events, they'd want to be in the same spec |
| 00:13 | <gsnedders> | There was a WG, but it went into PAG hell. |
| 00:13 | <GPHemsley> | does UI Events handle keyboard interaction well enough? |
| 00:13 | <zewt> | i doubt it defines any events well enough, heh |
| 00:14 | <zewt> | i don't know what the status of speccing keycodes is (guessing interop is still hopeless) |
| 00:14 | <gsnedders> | "handle keyboard interaction well enough?" hahahahahahaha |
| 00:14 | <gsnedders> | What zewt said, basically |
| 00:14 | <gsnedders> | keycodes? specified? |
| 00:15 | <heycam> | Hixie_, you're right, there's no way to say named properties are not enumerable, currently |
| 00:15 | <zewt> | keycodes are probably one of those really hard to fix things--since it's had zero interop for so long, everyone uses UA sniffing to make sense of it, which probably means that interop can never happen |
| 00:15 | <GPHemsley> | https://dvcs.w3.org/hg/d4e/raw-file/tip/source_respec.htm#key-codes |
| 00:15 | <gsnedders> | zewt: Opera's had issues every time we change to match others better. And then we break a fuckton of stuff that sniffs us. |
| 00:15 | <Hixie_> | man, can you say scope creep :-P |
| 00:16 | <Hixie_> | GPHemsley: i'm just saying mouse interaction, don't go down the road of keyboard interaction events before mouse is done, that's a rat hole and a half |
| 00:16 | <zewt> | i seem to recall some minor effort to add a new keycode-ish property on keyboard events, so interop can be dumped there and leave keycode to the wolves, but i'm not holding my breath on that |
| 00:16 | <Hixie_> | you can't just not support the old key events |
| 00:16 | <Hixie_> | the entire web depends on those |
| 00:16 | <Hixie_> | heycam: k. filed a bug. |
| 00:16 | <Hixie_> | heycam: for now i'm just using handwavy prose. |
| 00:16 | <gsnedders> | GPHemsley: Mostly informative and not matching anyone, no? |
| 00:16 | <GPHemsley> | Hixie_: And what about touch? |
| 00:17 | <GPHemsley> | gsnedders: No idea :) |
| 00:17 | <Hixie_> | GPHemsley: there's a wg on that. i'd stay waaaay clear. |
| 00:17 | <GPHemsley> | k |
| 00:17 | <heycam> | Hixie_, ok cool. if anything, I'll add a term you can link to, not IDL syntax. |
| 00:17 | <Hixie_> | cool |
| 00:17 | <GPHemsley> | so... the WHATWG handles all the stuff that people just assume are already handled |
| 00:17 | <Hixie_> | heycam: i figure the easiest option is probably a [LegacyNonEnumerableNamedProperties] attribute or something |
| 00:17 | <Hixie_> | GPHemsley: more or less |
| 00:18 | <Hixie_> | the nitty gritty isn't sexy |
| 00:18 | <GPHemsley> | we're like the guy with the broom at the end of the parade |
| 00:18 | <zewt> | Hixie_: so, wait until the WG specs touch events badly, then throw it out and spec it too? heh |
| 00:18 | <Hixie_> | (in the w3c's defense, CSS 2.1 was the first effort of its kind) |
| 00:19 | <Hixie_> | zewt: i'd stay away from touch events because it's a patent mine field and we have bigger fish to fry tright now. |
| 00:26 | <Hixie_> | you know it's a bad day when spec something that involves TWELVE separate occurrences of the fingerprint vector warning icon. |
| 00:42 | <TabAtkins> | gsnedders: PAG hell? |
| 00:42 | <gsnedders> | TabAtkins: patent advisory group |
| 00:43 | <gsnedders> | TabAtkins: Just, a wonderful way to stop anything actually moving forward |
| 00:43 | <TabAtkins> | Anyone know if it's possible in git to take a chunk of one file, and move it into a brand new repo with history intact? Maybe just by cloning the old repo into a new one and manually carving away the rest of the file as the first new-repo commit? |
| 00:44 | <gsnedders> | TabAtkins: As Hixie said, it's a patent mind field with people claiming a fuckton of patents covering it |
| 00:44 | <gsnedders> | TabAtkins: You can take the single file and make a new repo of that, but not easily a chunk without manually doing a lot of work, I think |
| 00:44 | <TabAtkins> | Single file works as long as I get to carry history. |
| 00:44 | <TabAtkins> | If not, it's not a huge loss, but I'd like to. |
| 00:45 | <gsnedders> | clone and then use `git-filter-branch` |
| 00:45 | <gsnedders> | To remove everything but that file |
| 00:58 | <TabAtkins> | Excellent, thanks! |
| 01:13 | <TabAtkins> | Do algebraic numbers have a single-letter name, like Z for the integers or Q for the rationals? |
| 01:19 | <Hixie_> | "algebraic numbers"? |
| 01:19 | <TabAtkins> | Solution to polynomials. The reals minus the transendentals. |
| 01:19 | <TabAtkins> | transcendentals |
| 01:20 | <Hixie_> | oh, those. not to my knowledge. |
| 01:21 | <TabAtkins> | Hm, then I don't have a class name for them that matches my pattern. ;_; |
| 01:21 | <TabAtkins> | My bigint class is called Z, my rational class will be called Q. |
| 01:27 | <GPHemsley> | "the algebraic numbers therefore form a field, sometimes denoted by A (which may also denote the adele ring) or Q [overbar]." |
| 01:27 | <TabAtkins> | A works for me! Thanks! |
| 01:27 | <TabAtkins> | I couldn't find anything, but I was probably just skimming too fast. |
| 01:28 | <GPHemsley> | https://en.wikipedia.org/wiki/Algebraic_number#The_field_of_algebraic_numbers |
| 01:29 | <GPHemsley> | "In other words, the intersection of Q and A is exactly Z." |
| 01:29 | <GPHemsley> | In other words, the intersection of Q and A is exactly Z. |
| 01:29 | <GPHemsley> | err |
| 01:29 | <GPHemsley> | https://en.wikipedia.org/wiki/Algebraic_integer#Examples |
| 01:29 | <GPHemsley> | just for reference |
| 01:31 | <GPHemsley> | TabAtkins: ^ |
| 01:32 | <TabAtkins> | Interesting. That's a different reference, using A to refer solely to algebraic integers. |
| 01:32 | <TabAtkins> | I'll just ignore that. |
| 01:49 | GPHemsley | shrugs |
| 02:27 | <cabanier> | TabAtkins: polynomials? what are you doing? :-) |
| 02:28 | <TabAtkins> | Doing Project Euler problems in JS, so I needed a bigint library, and wrote one for myself. |
| 02:28 | <TabAtkins> | Soonish I'll need rationals, so I'll write that. And then I might as well keep going. |
| 13:58 | <annevk> | Changed the spec and patched Firefox... https://bugzilla.mozilla.org/show_bug.cgi?id=891340 |
| 14:02 | <jgraham> | Isn't that cheating? :p |
| 14:02 | <annevk> | The best kind |
| 14:07 | <Hixie_> | hm, i can't find any outstanding feedback on script preloading |
| 14:08 | <Hixie_> | that's amazing, usually there's always something or other pending... |
| 14:11 | <annevk> | Hixie_: are you sure? I'm pretty sure people still want more options for loading scripts |
| 14:11 | <annevk> | Hixie_: talk with JakeA |
| 14:12 | <Hixie_> | can't find any outstanding... |
| 14:12 | <annevk> | Hixie_: e.g. http://www.html5rocks.com/en/tutorials/speed/script-loading/ |
| 14:13 | <JakeA> | I'd love http://www.html5rocks.com/en/tutorials/speed/script-loading/#toc-depressing to be possible |
| 14:13 | <jgraham> | Hixie_: Including email? |
| 14:13 | <Hixie_> | oh i'm sure people want stuff, but either they haven't asked for it, or they didn't reply to my last question on the topic |
| 14:13 | <Hixie_> | jgraham: yeah |
| 14:13 | <Hixie_> | jgraham: (there's very few bugs actually left now) |
| 14:14 | <Hixie_> | (only about 200 including all the deferred ones) |
| 14:14 | <JakeA> | Hixie_: Which question is this? |
| 14:16 | <Hixie_> | JakeA: dunno |
| 14:25 | <Hixie_> | JakeA: i'm just saying i can't find any outstanding feedback on the topic of script preloading |
| 14:25 | <Hixie_> | JakeA: which usually is very rare since there's always someone complaining about it :-) |
| 14:25 | <JakeA> | Kyle isn't happy that IE11 dropped readystate http://blog.getify.com/ie11-please-bring-real-script-preloading-back/ |
| 14:25 | <JakeA> | although that's more an IE complaint than spec |
| 14:25 | <Hixie_> | yeah kyle is usually the one asking for something |
| 14:25 | <Hixie_> | (though i have great trouble understanding what he wants) |
| 14:25 | <JakeA> | :D |
| 14:25 | <annevk> | Hixie_: I think JakeA's article above captures what problems people are running into today with the semantics we offer |
| 14:25 | <JakeA> | I wanted a depends attribute, which took a CSS selector for dependencies, but saw that similar things had been discussed and the circular thing was a blocker. I'm hoping the ES6 module stuff is going to deal with this now |
| 14:25 | <Hixie_> | so there's two things i don't understand |
| 14:25 | <JakeA> | (eg <script src="…" depends=".other-scripts"></script>) |
| 14:25 | <Hixie_> | the first is, why does the platform need to worry about order? it's so trivial to make scripts wait on each other, and javascript is late-binding. the other is, if the slowness is just networking, then why can't you just use XHR and when you're ready, inline the script? |
| 14:25 | <Hixie_> | i'm sure if kyle saw me asking these, he'd bash his head against a wall, since i've asked him the same thing dozens of times and he's tried to answer dozens more |
| 14:25 | <JakeA> | Is it trivial to make scripts wait on each other? If one is a library from a CDN, and the other 3 are scripts of mine that use that library, how do I maintain execution order? |
| 14:25 | <JakeA> | As for XHR, I know Chrome treats XHR as low priority when the page is loading |
| 14:25 | <jgraham> | To be fair xhr+inlining seems rather complicated compared to a declarative solution |
| 14:25 | <JakeA> | & not discoverable by pre-parsers etc |
| 14:26 | <JakeA> | A declarative version of async=false would be most of the way there. But if we're going to see concatenation thrown out of the window with HTTP2, it'd be nice to have feature scripts run as soon as they & their dependencies are ready |
| 14:26 | <Hixie_> | JakeA: put "if (window.postMyLibraryLoad) while (window.postMyLibraryLoad.length) window.postMyLibraryLoad.pop()();" at the end of the library, put "if (!window.myLibrary) { if (!window.postMyLibraryLoad) window.postMyLibraryLoad = []; window.postMyLibraryLoad.push(localInit); } else localInit();" at the end of your dependent scripts |
| 14:26 | <Hixie_> | or some such |
| 14:27 | <Hixie_> | lots of ways to do it |
| 14:27 | <annevk> | Hixie_: you can't change the library script typically |
| 14:27 | <Hixie_> | of course you can change the library script |
| 14:27 | <annevk> | Hixie_: lots of sites load jQuery from Google |
| 14:28 | <Hixie_> | so just have jQuery implement this directly |
| 14:28 | <jgraham> | So, would something like <script src="foo" defer="id1 id2"> work? In down-rev browsers the script would be defered until DOMContentLoaded. In supporting browsers it would execute after scripts with id id1 and id2, with some logic at DOMContentLoaded to ensure that all scripts would load |
| 14:28 | <jgraham> | Hixie_: It isn't really sensible to get all library authors to agree on a common loading pattern |
| 14:29 | <JakeA> | jgraham: Yeah, although you can get into deadlock, which I've head is the reason this has been thrown out in the past |
| 14:29 | <Hixie_> | jgraham: they don't need to. just put whatever pattern you want at the end of the library. |
| 14:29 | <jgraham> | And if they have to it is clear evidence that the platform should be providing one |
| 14:29 | <annevk> | Hixie_: getting each library to work on some kind of standardized solution could maybe work... but putting the solution a level higher would be so much easier |
| 14:29 | <jgraham> | Hixie_: If you don't control the library you can't do that |
| 14:29 | <JakeA> | I guess this common loading pattern is ES6 modules |
| 14:30 | <Hixie_> | anyway, if there's a library that matters so much, why can't you just import it with <script src=""> |
| 14:30 | <JakeA> | but yeah, if it's a hosted library, you lose |
| 14:30 | <jgraham> | JakeA: I'm not sure I see that there has to be a deadlock |
| 14:30 | <Hixie_> | then it'll automatically block anything else |
| 14:30 | <jgraham> | But I am probably missing something |
| 14:30 | <annevk> | Hixie_: you don't want to block page loading |
| 14:30 | <annevk> | Hixie_: and you want <script> loading to start asap |
| 14:30 | <zewt> | (i don't want to modify external libraries if i don't absolutely have to--maintenance headache) |
| 14:31 | <annevk> | Hixie_: this is fairly fundamental stuff in web development... |
| 14:31 | <jgraham> | (if you end up in a situation where B is waiting for A and A for B you can decree that tree order wins or something) |
| 14:31 | <JakeA> | jgraham: <script id="one" defer="two" src="…"> <script id="two" defer="one" src="…"> |
| 14:31 | <JakeA> | yeah, that'd work |
| 14:32 | <Hixie_> | annevk: *shrug* i agree it's fundamental, i just don't see the problem... |
| 14:33 | <jgraham> | I don't know enough about ES6 modules to know if they solve this. Presumably they can only work once the script has downloaded and parsed |
| 14:33 | <annevk> | Hixie_: 1) you don't want to modify libraries and you can't always do that 2) you don't want to block page loading 3) you want to start loading dependencies asap |
| 14:33 | <annevk> | Hixie_: script loading doesn't cater to that at the moment |
| 14:33 | <annevk> | Hixie_: it seems pretty trivial to me |
| 14:36 | <JakeA> | jgraham: I'm *hoping* you can put your imports in an inline script. They'd be declarative so preloaders can do their thing, and I hope you can be complex with the dependencies. However, I have no idea if it'll turn out like this |
| 14:37 | <jgraham> | Ah, I see |
| 14:37 | <jgraham> | It doesn't seem very modular though |
| 14:38 | <JakeA> | I like jgraham's suggestion, although it should use a new attribute rather than defer as IE<10 has poisoned defer |
| 14:39 | <jgraham> | (although I guess one way or another none of this is since it is all about declaring dependencies seperate from the actual code) |
| 14:45 | GPHemsley | clouds up the wiki history |
| 14:45 | <GPHemsley> | moar categories! moar obsolete pages! |
| 14:47 | <annevk> | Not entirely sure http://wiki.whatwg.org/wiki/Character_Encoding_Detection is completely obsolete, but I guess it's fine to mark it as such |
| 15:06 | <Hixie_> | if we do do <script defer="otherscript1 otherscript2">, we could also do <script asneeded> and HTMLScriptElement.needed(), and .needed() would propagate to all the elements that defer="" points to as well |
| 15:06 | <Hixie_> | (i guess asneeded should still download and parse, just not execute) |
| 15:07 | <Hixie_> | (though i'm very not convinced that executing needs to take any time at all, so i don't understand why people are so eager to parse ahead of time but defer execution) |
| 15:08 | <Hixie_> | looks like http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2012-December/038429.html is the last e-mail i can find on the subject |
| 15:14 | <GPHemsley> | annevk: In this case, "obsolete" means "superseded"—the contents of the wiki page are not necessarily wrong; they're just no longer authoritative. |
| 15:15 | <annevk> | GPHemsley: I think for this subject they might be. Though it might turn out we're going to get the entire platform to move away from sniffing. |
| 15:15 | <GPHemsley> | annevk: Well, if you think the wiki page is still relevant, feel free to revert. :) |
| 15:16 | <annevk> | Hixie_: btw, I've also seen requests for <link rel=stylesheet async> |
| 15:16 | <annevk> | Hixie_: to indicate the style sheet is not essential for the purposes of <script>, .offsetWidth, etc. |
| 15:44 | <dglazkov> | good morning, Whatwg! |
| 15:59 | <GPHemsley> | Who broke the whatwg.org domain? |
| 16:01 | <GPHemsley> | ah, it's back |
| 16:27 | <JakeA> | Hixie_: Like asneeded, needed should return a promise |
| 16:28 | <Hixie_> | needed? |
| 16:28 | <Hixie_> | wouldn't this be a content attribute? |
| 16:28 | <JakeA> | HTMLScriptElement.needed().then(...) |
| 16:28 | <Hixie_> | oh, right |
| 16:28 | <Hixie_> | which would execute once the scripts had run? |
| 16:28 | <JakeA> | yeah |
| 16:29 | <Hixie_> | so basically the same as <script onafterscriptexecute> ? |
| 16:29 | <JakeA> | I guess you've been told the gmail js-in-comments story 100 times |
| 16:29 | <Hixie_> | er, <script onload> i mean |
| 16:29 | <Hixie_> | gmail does all kinds of things that i don't understand the motivation for |
| 16:30 | <JakeA> | yeah, it'd be like onload but promisey |
| 16:30 | <JakeA> | Here's David Herman looking at function-futures https://bugzilla.mozilla.org/show_bug.cgi?id=854627 |
| 16:31 | <Hixie_> | i don't understand that bug. why wouldn't all script compilation happen async? |
| 16:31 | <JakeA> | Here's me with a very similar idea to asneeed https://gist.github.com/jakearchibald/5618497 |
| 16:32 | <JakeA> | I think FunctionFuture is an alternative to `new Function`, which is sync |
| 16:33 | <Hixie_> | new Function () doesn't do any compilation, does it? |
| 16:33 | <JakeA> | yeah, var f = new Function("alert('hello')"); f(); |
| 16:34 | <Hixie_> | oh, with arguments |
| 16:34 | <Hixie_> | yeah that's just a fancy eval. just don't do that. |
| 16:35 | <JakeA> | indeed |
| 16:36 | <JakeA> | When I threw that gist around, people much preferred the "depends" attribute to the promise-based model for determining execution order, but yeah, you don't get to defer parsing |
| 16:36 | <Hixie_> | well you could |
| 16:36 | <Hixie_> | is that needed? |
| 16:36 | <Hixie_> | i can't tell what people want |
| 16:36 | <Hixie_> | delaying execution seems pointless since execution can be free |
| 16:36 | <Hixie_> | but that seems to be what people ask for |
| 16:37 | <JakeA> | I'm equally unconvinced |
| 16:37 | <JakeA> | I avoided serving js to older browsers on http://m.lanyrd.com, the old backberry browser took seconds to parse the js |
| 16:38 | <Hixie_> | well old browsers aren't going to support any of this new stuff either way |
| 16:38 | <JakeA> | exactly |
| 16:38 | <JakeA> | maybe the gmail team have data on this for newer devices? |
| 16:43 | <GPHemsley> | Hixie_: Still trying to determine the exact dimensions of the gap in mouse behavior specs: Are you looking for something like "When the mouse moves over an element, fire a 'mousemove' event on that element'? |
| 16:44 | <Hixie_> | yes |
| 16:44 | <Hixie_> | with a "must" in there somewhere |
| 16:44 | <Hixie_> | :-) |
| 16:45 | <Hixie_> | oops, apparently i forgot to tell dreamhost t actually go ahead and update the server OS |
| 16:45 | <Hixie_> | whatwg.org will probably go down for a bit today while the OS is updated |
| 16:45 | <GPHemsley> | yeah, I noticed :P |
| 16:49 | <annevk> | Ms2ger: write a test |
| 16:50 | <Ms2ger> | It's your bug :) |
| 16:51 | <GPHemsley> | Hixie_: Are you picturing this mouse behavior spec to be its own document? |
| 16:53 | <annevk> | GPHemsley: also, note that there's a number of problems with that line |
| 16:53 | <GPHemsley> | annevk: ? |
| 16:53 | <Hixie_> | GPHemsley: only insofar as you'd likely not want it in the mime sniffing document :-) |
| 16:53 | <annevk> | GPHemsley: 1) "moves over an element"; you need to define how to determine this, through defining hit testing |
| 16:54 | <Hixie_> | GPHemsley: my personal ideal would be that all our specs be in one document, but that's too complicated to handle edit-wise, so my realistic ideal is that there be one doc per editor. |
| 16:54 | <annevk> | GPHemsley: 2) "fire a mousemove event"; MouseEvent has a number of members and you'll need to define how each is to be set, given the element determined through hit testing |
| 16:54 | <Hixie_> | GPHemsley: but you do as you wish :-) |
| 16:55 | <GPHemsley> | annevk: Well, that's part of my question... a lot of this is already defined in DOM 3 Events, IIUC |
| 16:55 | <Hixie_> | i need a tool that can periodically sample memory usage on my linux box and show me the data over time |
| 16:55 | <Hixie_> | anyone know of anything like that? |
| 16:55 | <annevk> | GPHemsley: no it's not |
| 16:56 | <GPHemsley> | annevk: Then I guess I don't UC |
| 16:58 | <annevk> | Ms2ger: so if I were to write a test, which test should be updated? |
| 16:58 | <GPHemsley> | annevk: Can you give an example of a MouseEvent member whose behavior is not defined by DOM 3 Events? |
| 16:59 | <Ms2ger> | dom/ranges/Range-collapse.html in https://github.com/w3c/web-platform-tests |
| 16:59 | <annevk> | GPHemsley: clientX |
| 16:59 | <GPHemsley> | Hixie_: I ask because someone would need to set it up :) |
| 16:59 | <Ms2ger> | / http://mxr.mozilla.org/mozilla-central/source/dom/imptests/webapps/DOMCore/tests/approved/test_Range-collapse.html?force=1 |
| 16:59 | <Hixie_> | GPHemsley: oh if you want a subdomain, yeah, let me know |
| 16:59 | <annevk> | Ms2ger: that seems like something you can do much better than I |
| 17:00 | <Ms2ger> | I'm confident you can do it |
| 17:00 | <GPHemsley> | annevk: Oh, so I have to get down to the nitty gritty about the pointer location? ( Hixie_ said this would be easy :( ) |
| 17:00 | <Hixie_> | i didn't say it would be _easy_ |
| 17:00 | <Hixie_> | just that it wouldn't be as bad as html editing :-) |
| 17:01 | <GPHemsley> | oh, sorry, "not too hard" |
| 17:01 | <annevk> | Ms2ger: first getting something through web-platform-tests and then importing that... I think I rather reassign |
| 17:01 | <GPHemsley> | Hixie_: I have to watch your words carefully :P |
| 17:01 | <annevk> | GPHemsley: hah, user interaction is hard |
| 17:02 | <annevk> | GPHemsley: so you know pointer location, that's x,y, the problem is determining what element is at x,y, the scroll positions of the various elements, etc. |
| 17:02 | <GPHemsley> | eesh |
| 17:02 | <annevk> | GPHemsley: and then setting the event attributes correctly, adjusting for pseudo-elements, ... |
| 17:02 | <annevk> | GPHemsley: adjusting for Shadow DOM |
| 17:09 | <Hixie_> | ok looks like update is happening now |
| 17:09 | <Hixie_> | afk |
| 17:10 | <GPHemsley> | "The building might be blowing up right now, so I'm gonna leave." |
| 17:12 | <annevk> | Ms2ger: seems that test has bugs |
| 17:12 | <annevk> | Ms2ger: blargh |
| 17:24 | <GPHemsley> | And the Mozilla WebVTT situation has escalated... |
| 17:25 | <rillian_> | GPHemsley: following the bugs are you? :) |
| 17:26 | <GPHemsley> | just the <track> tracking bug |
| 17:26 | <msaad> | GPHemsley: let the spamming begin! |
| 17:26 | <GPHemsley> | indeed |
| 17:27 | <annevk> | Ms2ger: https://github.com/w3c/web-platform-tests/pull/243 fix it |
| 17:27 | <annevk> | GPHemsley: pointer? |
| 17:27 | <GPHemsley> | https://bugzilla.mozilla.org/show_bug.cgi?id=629350 |
| 17:27 | <GPHemsley> | all the open dependencies are being WONTFIXed |
| 17:28 | <Ms2ger> | Ignore that, please |
| 17:29 | <annevk> | Ms2ger is now a PR-bot? |
| 17:30 | GPHemsley | does wonder why the legal bug never received a response |
| 17:30 | <Ms2ger> | annevk, looks like something weird is up with the indentation in your PR |
| 17:30 | <annevk> | Ms2ger: I tried to preserve the tabs, if that failed, fuck tabs |
| 17:30 | <Ms2ger> | I don't disagree there... |
| 17:31 | <GPHemsley> | <3 tabs |
| 17:39 | <annevk> | Ms2ger: anyway, someone can fix that when merging right? |
| 17:39 | <Ms2ger> | I guess |
| 17:39 | <Ms2ger> | jgraham, ^ |
| 17:43 | <Hixie_> | ok, system's been upgraded |
| 17:43 | <Hixie_> | i've already found two problems... my mail client and my text editor |
| 17:43 | <Hixie_> | nothing i use regularly or anything... |
| 17:46 | <Hixie_> | ok pine is now alpine, that's easy enough and seems backwards compatible, excellent. |
| 17:46 | <Hixie_> | now why is emacs not able to create directories in /tmp |
| 17:50 | <Hixie_> | ok, setting TMPDIR to something local seems to have fixed that |
| 20:13 | <Hixie_> | oh blimey, my entire build system is full of bugs now |
| 20:13 | Hixie_ | grabs some duct tape and goes on a fixing rampage |
| 20:13 | <Ms2ger> | It wasn't before? :) |
| 20:16 | <Hixie_> | Ms2ger: i just updated the os |
| 20:16 | <Hixie_> | well, i didn't |
| 20:16 | <Hixie_> | dreamhost did |
| 20:16 | <Hixie_> | so all the command line tools subtly changed behaviour |
| 20:19 | <Hixie_> | i just went up like two whole emacs versions |
| 20:19 | <Hixie_> | i'm all the way up to date with 2010 emacs now! -_- |
| 20:21 | <annevk> | Hixie_: the broadcasting to same-origin global API, was that part of a bug already? |
| 20:21 | <annevk> | globals* |
| 20:23 | <Hixie_> | come again? |
| 20:24 | <Hixie_> | oh, like postMessage for broadcasts? |
| 20:24 | <Hixie_> | i'm not aware of a bug or e-mail on that off-hand |
| 20:30 | <annevk> | Should I file one? |
| 20:34 | <Hixie_> | if you must |
| 20:34 | <Hixie_> | /usr/bin/perl: symbol lookup error: /home/ianh/bin/perl/lib/x86_64-linux-gnu-thread-multi/auto/Compress/Raw/Zlib/Zlib.so: undefined symbol: Perl_Tstack_sp_ptr |
| 20:34 | <Hixie_> | that seems... bad |
| 20:34 | <Hixie_> | oh i guess it means by zlib library is out of date |
| 20:34 | <Hixie_> | lets see if i even need that now... |
| 20:39 | <annevk> | I guess I must, and given you define Window/Workers... |
| 20:46 | <annevk> | https://www.w3.org/Bugs/Public/show_bug.cgi?id=22628 |
| 20:47 | <smaug____> | rafaelw: hmm, let me think of Bug 22296 |
| 20:52 | <annevk> | Hmm, sees like the diff cache is full again |
| 20:57 | <annevk> | I wonder if my DreamHost instance got updated as well... Something is wrong with html5.org's diff tool. |
| 21:01 | <Hixie_> | unlikely |
| 21:06 | <annevk> | Maybe the output of svn changed... |
| 21:06 | <annevk> | Distributed software is great |
| 21:08 | <annevk> | Hixie_: so, "svn: Can't find a temporary directory: Internal error", wasn't that what you got? |
| 21:13 | <Hixie_> | huh |
| 21:13 | <Hixie_> | how'd you get that? |
| 21:14 | <Hixie_> | haven't had any trouble with svn, but there's every chance that there's lurking trouble there |
| 21:14 | <annevk> | When I run "svn diff -r 8040:8041 http://svn.whatwg.org/webapps/source"; |
| 21:14 | <annevk> | When I run "svn log" things are fine |
| 21:15 | <Hixie_> | i can repro |
| 21:15 | <Hixie_> | looking now |
| 21:15 | <Hixie_> | sounds like a system-level config problem. will report to dreamhost. |
| 21:17 | <Hixie_> | sent |
| 21:17 | <Hixie_> | i'm guessing it's an issue with /tmp permissions |
| 21:18 | <annevk> | tweeted |
| 21:44 | <rafaelw> | smaug____: cool. |
| 21:45 | <rafaelw> | FWIW, I plan to prepair a patch for blink which causes showModalDialog to throw if called within a mutationobserver callback. |
| 21:45 | <rafaelw> | (soon). |
| 21:45 | <rafaelw> | smaug___: ^^^ |
| 21:46 | <Hixie_> | rafaelw: speak to jamesr__, someone the other day was talking abotu making showModalDialog() throw when called from anything that's not a user gesture, which would subsume that |
| 21:46 | <rafaelw> | ok. will do. |
| 21:46 | <rafaelw> | thanks. |
| 21:46 | <Hixie_> | (btw i think the spec says to make it do nothing, not throw) |
| 21:46 | <rafaelw> | ok. |
| 21:47 | <rafaelw> | jamesr__: you got your ears on? |
| 21:58 | <Hixie_> | yay for including ip addresses in bugs from the quick form |
| 22:03 | <annevk> | rafaelw: didn't smaug____ point out elsewhere that it wasn't just showModalDialog but also other things? |
| 22:03 | <rafaelw> | i'm hoping he'll point it out again =-) |
| 22:03 | <rafaelw> | (sync xhr?) |
| 22:03 | <annevk> | I should take some time to read up on all this since event loops currently make me run |
| 22:03 | <rafaelw> | (workers) |
| 22:03 | annevk | looks |
| 22:03 | <smaug____> | sync XHR is gecko only thing |
| 22:03 | <annevk> | sync XHR is not it, although it is in Gecko at the moment |
| 22:04 | <smaug____> | parser spins |
| 22:04 | <smaug____> | IIRC |
| 22:04 | <smaug____> | and there might be some 3rd case too |
| 22:05 | <annevk> | Oh, it was sicking, see https://www.w3.org/Bugs/Public/show_bug.cgi?id=20821#c3 rafaelw |
| 22:06 | <annevk> | "It's definitely the case that spinning the event loop does raise a lot of complex issues with regards to things that need to happen at end-of-microtask. However many of these issues arise no matter what." |
| 22:06 | <rafaelw> | that's the part that i don't understand. |
| 22:06 | <rafaelw> | otherwise it sounds like we're in agreement. |
| 22:06 | <rafaelw> | IOW: Don't do that. |
| 22:06 | <rafaelw> | (and try to make progress towards removing that surface area) |
| 22:07 | <annevk> | I think I'm in your camp, but for now I'm just trying to get you guys to sort it out :-) |
| 22:09 | <jamesr__> | document.write() doesn't spin the message loop |
| 22:09 | <jamesr__> | although it can run lots of fun things |
| 22:09 | <jamesr__> | ditto with innerHTML |
| 22:09 | <jamesr__> | for my money, showModalDialog() should just throw (or silently do nothing) in all cases. web compat impact TBD :) |
| 22:11 | <annevk> | uhuh |
| 22:15 | <Hixie_> | hear hear |
| 22:15 | <Hixie_> | though i did just finish fixing its spec :-) |
| 22:16 | <Hixie_> | if anyone objects to my renaming the term "allowed to navigate", please speak up now |
| 22:18 | <Hixie_> | (specifically, my plan is s/allowed to navigate/friendly with/) |
| 22:18 | <Hixie_> | or "friends with" |
| 22:30 | <annevk> | Hixie_: "Stop one" |
| 22:33 | <Hixie_> | where? |
| 22:39 | <annevk> | Hixie_: commit message ;) |
| 22:40 | <Hixie_> | oh, no chance of changing those |
| 22:47 | <Hixie_> | "If I do not know how to use what can be helped by itself, so that the maximum my site as desired?" |
| 23:16 | <divya> | wheres simon when you need him |
| 23:26 | <GPHemsley> | Hixie_: Next step is to upgrade PHP? |
| 23:26 | <Hixie_> | oh right |
| 23:26 | <Hixie_> | wiki.whatwg.org right? |
| 23:26 | <Hixie_> | 5.3 or 5.4? 5.4? |
| 23:26 | <GPHemsley> | what's the highest |
| 23:27 | <Hixie_> | 5.4 |
| 23:27 | <Hixie_> | FastCGI? |
| 23:27 | <GPHemsley> | yeah |
| 23:27 | <Hixie_> | XCache? it wasn't checked before |
| 23:27 | <GPHemsley> | hmm |
| 23:27 | <GPHemsley> | nah |
| 23:27 | <Hixie_> | done |
| 23:27 | <GPHemsley> | thanks |
| 23:27 | GPHemsley | checks for bustage |
| 23:28 | <GPHemsley> | hmm... not instantaneous? |
| 23:28 | <GPHemsley> | oh, you know something |
| 23:28 | <GPHemsley> | I think the OS upgrade earlier broke the wiki widgets |
| 23:29 | <GPHemsley> | err, gadgets |
| 23:30 | <GPHemsley> | Hixie_: Did it say how long it would take to go into effect? |
| 23:30 | <Hixie_> | prolly take 10 or so minutes |
| 23:31 | <GPHemsley> | alright, I'll check back later |
| 23:31 | <Hixie_> | they have a system that does deployments in a queue or something |
| 23:37 | <Hixie_> | i've gotten to a low enough number of bugs that i've actually responded to all 10 within the last 12 horus |
| 23:37 | <Hixie_> | (all 10 that aren't blocked or intentionally deferred) |
| 23:38 | <Hixie_> | (there's 110 of those) |