| 05:40 | <gsnedders> | https://www.youtube.com/watch?v=D1S-G8rJrEk — URL parsing differences causing security issues |
| 05:58 | <annevk> | smaug____: nope |
| 15:30 | <nox> | gsnedders: Couldn't resist: https://twitter.com/nokusu/status/930094758483169281 |
| 15:41 | <jgraham> | nox: "But what about the aesthetic issue of allowing many slashes?" |
| 15:42 | <jgraham> | Truely the "but her emails" of URL standardisation |
| 15:42 | <nox> | jgraham: I feel like “but the sla— |
| 15:42 | <nox> | DAMN YOU SAID IT BEFORE I COULD |
| 15:43 | nox | pouts. |
| 15:45 | <annevk> | nox: preach |
| 15:46 | <annevk> | Is there a writeup somewhere of that video? |
| 15:46 | <nox> | Nah but I have the best screenshot. |
| 15:47 | <nox> | https://irccloud.mozilla.com/file/NHgBAPJC/image.png |
| 15:47 | <nox> | Can’t top that. |
| 15:47 | <annevk> | Ah okay, those kind of exploits |
| 15:48 | <annevk> | If after you serialize you might end up parsing something else out of it next time, that's a problem |
| 15:48 | <annevk> | URL Standard should be good there |
| 17:10 | <wanderview> | JakeA: I regret ever looking at monitor refresh rates... |
| 17:11 | <wanderview> | JakeA: my home desktop monitor was set to 59hz refresh rate for some reason.... wtf |
| 17:19 | <Domenic> | wow |
| 17:19 | <Domenic> | I thought that was kind of impossible with LCDs |
| 17:19 | <Domenic> | How can I ensure I'm not suffering from this myself? |
| 17:23 | <wanderview> | I went in to the windows OS display adapters to check and set it back to 60hz |
| 17:23 | <wanderview> | but I wonder how firefox handles two monitors at different vsync rates |
| 17:24 | <JakeA> | wanderview: may have been 59.97? I think that's common |
| 17:24 | <wanderview> | JakeA: maybe... the windows UI only gave whole numbers... who knows how it rounds |
| 17:25 | <nox> | The PHP screenshot is kind of DRY badly applied. |
| 17:25 | <JakeA> | I'm not sure where 59.97 comes from, maybe NTSC |
| 17:25 | <wanderview> | this all just confirms my previous suspicion that I want nothing to do with the graphics code |
| 17:25 | <nox> | Didn't repeat yourself if your second URL parser is not interoperable with your first one! |
| 19:44 | <smaug____> | I'm feeling stupid now |
| 19:45 | <smaug____> | Domenic: annevk: want to explain why we need 7.7.2 https://dom.spec.whatwg.org/#concept-node-insert |
| 19:45 | <smaug____> | er, 7.7.2.2 |
| 19:47 | <smaug____> | oh, perhaps adopting doesn't do what it should do |
| 19:47 | <smaug____> | interesting |
| 19:47 | <smaug____> | I wonder why |
| 19:49 | <Mek> | blah, I really need to rewrite the whole Blob URL Store part of the File API spec... Trying to rewrite chromes implementation of that whole concept is just too painful without having a spec that actually addresses any edge cases... |
| 19:49 | <Mek> | (not that I didn't already know I needed to rewrite that part of the spec, but now I might be extra motivated...) |
| 19:49 | <jsbell> | :) |
| 19:50 | <smaug____> | ++Mek |
| 19:50 | <smaug____> | Mek: if you rewrite that part of the spec, ask @bakulf to give feedback |
| 19:51 | <smaug____> | He is familiar with the gecko impl |
| 19:52 | <Mek> | smaug____: thanks, will make sure to do so. |
| 22:03 | <smaug____> | Domenic: doesn't something in the HTML spec define what kind of document fullpage images or videos or so get |
| 22:10 | <Mek> | smaug____: https://html.spec.whatwg.org/multipage/browsing-the-web.html#read-media ? |
| 22:14 | <smaug____> | that. thanks |
