| 02:04 | <MikeSmith> | does anybody know what the proper mechanism is for reporting bugs in https://developers.google.com content |
| 02:05 | <MikeSmith> | https://developers.google.com/structured-data/site-name has an example that suggests using <link rel="canonical" href="https://example.com/"; itemprop="url"> which violates the "A link element must have either a rel attribute or an itemprop attribute, but not both." requirement in the HTML spec https://html.spec.whatwg.org/multipage/semantics.html#the-link-element |
| 02:37 | <JonathanNeal> | Is this on track for spec? https://lists.w3.org/Archives/Public/www-style/2014Jul/0315.html |
| 02:37 | <JonathanNeal> | translate, rotate, and scale properties. |
| 02:46 | <astearns> | JonathanNeal: yes, we're planning on adding that to the next level of CSS Transforms |
| 02:47 | <astearns> | http://drafts.csswg.org/css-transforms-2/ |
| 02:48 | <JonathanNeal> | astearns: That’s what I wanted. I’m working on a PostCSS plugin for it. |
| 02:49 | <JonathanNeal> | Here is the work I have started https://github.com/jonathantneal/postcss-transform-shortcut |
| 03:01 | <JonathanNeal> | astearns: so `translate: 10px 10px;` is the same as `transform: translate3d(10px, 10px, 0px)` ? |
| 03:02 | <JonathanNeal> | I’m basing this off “The translate property accepts 1-3 values, each specifying a translation against one axis, in the order X, Y, then Z. Unspecified translations default to 0px.” I presume this means all three axis are automatically declared, defaulting to `0px`. |
| 03:15 | <astearns> | JonathanNeal: that sounds correct to me, but I'd defer to more transform-oriented people |
| 08:01 | <therophyte> | VER |
| 09:03 | <annevk> | philipj: so basically, define "unloading document cleanup steps" to run https://fullscreen.spec.whatwg.org/#unfullscreen-a-document right? |
| 09:08 | annevk | proceeds with that assumption |
| 09:09 | <annevk> | philipj: if you find new issues, could you please file new GitHub issues? |
| 09:09 | <annevk> | philipj: having to deal with Bugzilla less is starting to feel like a plus |
| 13:47 | <mikec> | What functionality is replacing DocumentType.entities these days? i.e. where is the list of entities recognized by a parser "stored"? Is it just the fixed list at http://dev.w3.org/html5/html-author/charref ? |
| 14:03 | <gsnedders> | mikec: in HTML, there's been a fixed list for years (okay, it occasionally get ammended, but there's no point in exposing the list anyway) |
| 14:04 | <gsnedders> | mikec: in XML, no UA to my knowledge loads external entities, so there's no that much use to the API either |
| 14:05 | <MikeSmith> | mikec: yeah the list of character references that HTML parsers must support is in the HTML spec |
| 14:08 | <mikec> | MikeSmith: thanks |
| 14:10 | <MikeSmith> | gsnedders: did you see https://github.com/w3c/web-platform-tests/issues/1999 |
| 14:12 | <MikeSmith> | apparently the use of data: URIs in wpt tests is blocking somewhat the Blink team's efforts to integrate the wpt test suite into their CI |
| 14:13 | <MikeSmith> | and the html5lib tests are one place where they're used a lot |
| 14:13 | <gsnedders> | MikeSmith: that's jgraham's doing |
| 14:13 | <MikeSmith> | ok |
| 14:14 | <gsnedders> | MikeSmith: pretty sure I did the internal review of tham when he wrote them, but that was Opera 11 days. |
| 14:14 | <MikeSmith> | well I been wondering if the data URI instances in the wpt html5lib tests could be replaced with <img srcdoc> |
| 14:14 | <MikeSmith> | yeah I guess it's been a while |
| 14:14 | <gsnedders> | from memory there were data URI versions and document.open/write/close versions? |
| 14:14 | <MikeSmith> | oh |
| 14:14 | <gsnedders> | the latter should work at least |
| 14:15 | <gsnedders> | also I should find out what gate I'm meant to be going to |
| 14:15 | <MikeSmith> | well jgraham says at https://github.com/w3c/web-platform-tests/issues/1999#issuecomment-121080384 "I welcome PRs to change these tests to not use data: URIs (but in at least some cases I expect that to be difficult e.g. the html5lib tests are based around loading a document generated in content using the regular HTML parser; I'm not sure how else to do that)" |
| 14:15 | <gsnedders> | idk! |
| 14:15 | <gsnedders> | I certainly remember seeing some conversion of them to use document.open/write/close |
| 14:16 | <gsnedders> | But yeah, I only maintain the actual tests in our weird test format. I've not handled any browser runner in years. |
| 14:16 | <gsnedders> | Anyhow, yes, gate hunting. |
| 14:16 | <gsnedders> | Things to do, places to fly, etc. |
| 14:18 | <MikeSmith> | hai |
| 14:18 | <MikeSmith> | have fun |
| 14:22 | <gsnedders> | "Please wait", apparently. Oh well. |
| 14:23 | <gsnedders> | (Gate due to be announced in -7 minutes.) |
| 14:30 | <MikeSmith> | if you're at Heathrow the thing they do there of not announcing gates ahead of time and making you wait in the human-corral area is real innovation in making the most hostile user experience possible |
| 14:31 | <MikeSmith> | "Just when you thought the airport experience couldn't be anyway worse, we're still busy figuring out new ways!" |
| 14:31 | <gsnedders> | This is T3. So this is even worse. |
| 14:32 | <gsnedders> | For some reason I doubt we're leaving in 13 minutes. |
| 14:32 | <MikeSmith> | it's like a microcosm of all the worst aspects of British culture |
| 14:33 | <MikeSmith> | enjoy the ambience in the mean time |
| 14:33 | <MikeSmith> | soak in the full experience |
| 14:33 | <gsnedders> | yay, a gate! |
| 14:34 | gsnedders | scurries off |
| 14:40 | <gsnedders> | still another twenty minutes… |
| 16:22 | <jgraham> | MikeSmith, gsnedders: Yes, there are document.write versions, but that's an entirely different codepath, so I wouldn't run *only* those version |
| 16:22 | <jgraham> | s |
| 16:22 | <jgraham> | <iframe srcdoc> might be acceptable if that's same origin |
| 18:32 | <wanderview> | Ms2ger: if you have time, could you make me an account on wiki.whatwg.org with the username wanderview? I want to collaborate on the SW related pages... thanks! |
| 18:40 | <gsnedders> | jgraham: it should be the same codepath in the parser, no? or is it that different because of the re-entrant stuff? |
| 19:53 | <jgraham> | gsnedders: Certainly I have managed to find bugs using document.write that the other approach didn't. That's why they're seperate tests. |
| 19:58 | <smaug____> | writing tests for document.write? including also document.open()/close() behavior? |
| 19:59 | smaug____ | assumes tons of differences between browser engines |
| 20:01 | <gsnedders> | smaug____: I'm talking about just using open/write/close triplets to test the parser, really without any of the re-entrant fun |
| 20:15 | <smaug____> | oh, I wasn't even thinking re-entrancy |
| 20:15 | <smaug____> | but all the handling with session history and global scope and what not, when document.open/write is used after load event dispatch |
| 20:42 | <jgraham> | Yeah, that stuff is an interop wasteland |
| 21:04 | <gsnedders> | oh, that sort of stuff |
| 21:04 | <gsnedders> | well yeah, the html5lib test conversions only really test what the parser does, not that nightmare |