| 00:17 | <gsnedders> | Anyone know of an HTML parser in Erlang? |
| 02:55 | <zewt> | a little silly that to do window.location.href = url with rel=noreferrer, apparently you have to create a dummy A and call .click(), heh ... wonder if there's any less silly way, though I guess that works |
| 02:55 | <Hixie> | use an <a href=""> link? :-) |
| 03:03 | <Hixie> | TabAtkins: yeah. i was trying to make it work like a presentational attributes, basically. |
| 03:17 | <zewt> | it's programmatic, not a link, heh |
| 03:55 | <zewt> | heh, 3d transitions are nice on mobile safari for smoothness, but ... buggy as hell |
| 04:00 | <zewt> | transitions of 3d transforms, that is |
| 04:01 | <zewt> | heh, like opacity: 0 layers on top being visible as if they're opacity: 0.01 |
| 04:18 | <zewt> | maybe it's just chrome, it seems to work fine in mobile safari; guess i'll dig into it more tomorrow |
| 05:00 | <zewt> | borderline shocked that people can seriously, with a straight face, argue that black backgrounds behind subtitles is even conceivably a better default than a stroked font |
| 05:13 | <zewt> | sometimes i feel like if I suggest going out for steak, i'll have to fight tooth and nail with people who insist that the pile of nails and broken glass is a perfectly decent meal |
| 05:40 | <Hixie> | zewt: it's happening after the user clicks something right? |
| 05:52 | <zewt> | Hixie: yes, but as a result of JS logic a couple layers deep |
| 08:00 | Ms2ger | pokes Velmont |
| 09:17 | <Stevef_> | zewt: re "black backgrounds behind subtitles" recommendations from NAD (US) is "Characters must be sans serif, have a drop or rim shadow, and be proportionally spaced. " a translucent box is preferred so that the text will be clearer, especially on light backgrounds." http://www.dcmp.org/captioningkey/text.html |
| 14:56 | <karlcow> | "If you analyze XML sent as text/html on the web, something like 95% of it is invalid XML, for lots of different reasons." — http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2012-August/036873.html not sure I understand this by tabatkins |
| 14:57 | <karlcow> | or does he mean documents written with XML syntax rules, sent as text/html and being not well-formed. |
| 15:07 | <Ms2ger> | Breaking news, HTML is not XML? |
| 15:17 | <karlcow> | ☺ heh |
| 16:33 | <Hixie> | zewt: do the logic early, and just have a link :-) |
| 16:37 | <zewt> | Hixie: always keeping a DOM node in sync with script state changes is much more brittle |
| 16:37 | <zewt> | less hacky to just do the createElement/click workaround :) |
| 16:44 | <Hixie> | zewt: why is it brittle? |
| 16:44 | <Hixie> | zewt: how else would you make it possible for the user to copy link location, open link in new tab, drag the link, bookmark the link, etc? |
| 16:48 | <zewt> | it's a link to an oauth login flow (or not, depending on the situation) that responds back to a script on the calling site; not even sure what would happen if it was launched in some other way |
| 16:53 | <Hixie> | heh |
| 16:53 | <Hixie> | why noreferrer? |
| 16:57 | <zewt> | paranoia :) it's a site used soley for user authentication, and while there should never be anything sensitive to leak in the URL, this is the only place the site loads anything external |
| 22:48 | <zewt> | cool, havn't seen the "people don't abuse this in native apps so what's the problem" argument in a while |