| 03:18 | <Hixie> | annevk: how do i fullscreen with keyboard enabled?? |
| 03:55 | <Hixie> | firefox doesn't support vh yet? |
| 03:55 | <Hixie> | :-( |
| 03:59 | <Hixie> | and wtf are event.x and event.y in MouseEvent in chrome |
| 03:59 | <zewt> | everyone knows what the world needs most is: more coordinate systems in pointer events |
| 04:10 | <Hixie> | also why is chrome sending me a bogus 'mouseover' event on load |
| 04:25 | <Hixie> | oh man i wish .style was string settable |
| 04:26 | <Hixie> | every |
| 04:26 | <Hixie> | time |
| 04:32 | <Hixie> | man, how is linear-gradient still only prefixed |
| 05:22 | <jwalden> | Hixie: vh/vw/vmin/vmax they're supported in nightlies |
| 05:22 | <Hixie> | ah, excellent |
| 05:22 | <jwalden> | a recent landing |
| 05:23 | <Hixie> | the only other problem i had with firefox was that position:absolute-ing a <textarea> wouldn't affect its size |
| 05:23 | <Hixie> | can't work out why |
| 05:23 | <Hixie> | (same problem in opera; works in webkit) |
| 05:24 | <jwalden> | zewt: of coarse! |
| 05:24 | <jwalden> | a little late to respond, but a late pun is better than no pun |
| 07:11 | <MikeSmith> | Hixie: thinking about outlines . did anybody ever propose the idea of providing a way for a document to display its own outline? |
| 07:12 | <MikeSmith> | essentialy, having the browser be able to natively render and insert the outline at some point in the document |
| 07:13 | <MikeSmith> | in the way that anolis or whatever generate a ToC and add it, during postprocessing |
| 07:13 | <MikeSmith> | but instead not as postprocessing |
| 07:14 | <MikeSmith> | and not relying on custom script or a script library to add it |
| 07:14 | <MikeSmith> | I'm not saying I think it would be a good idea necessarily to have such a feature |
| 07:15 | <MikeSmith> | just wondering if there was ever any serious discussion about it |
| 07:15 | <MikeSmith> | because for one thing if browser were to ever implement support for the outline algorithm, that case would seem to be the main case for it |
| 07:37 | <SimonSapin> | MikeSmith: not quite "the web", but WeasyPrint makes PDF from web pages and adds an "outline" which is metadata that PDF viewers often show in a sidebar |
| 07:38 | <MikeSmith> | SimonSapin: thanks |
| 07:38 | <SimonSapin> | there is also some demand to have a TOC automatically generated in the document |
| 07:39 | <MikeSmith> | yeah I was thinking about it in the context of people saying that no browsers have implemented the outline algorithm |
| 07:40 | <MikeSmith> | which yeah none of them have, but then there's no feature in the spec yet that actually exposes the outline to Web content or to Web authors |
| 07:40 | <MikeSmith> | so browsers don't really have anything to implement |
| 07:40 | <SimonSapin> | In WeasyPrint this is not based on the outline algorithm but on CSS bookmark-level http://dev.w3.org/csswg/css3-gcpm/#bookmarks which by default is <h1> ... <h6> |
| 07:41 | <MikeSmith> | yeah of course that works fine if you document doesn't use nested sections |
| 07:41 | <SimonSapin> | and some fixups to get a proper tree out of a sequence of level that can be non-sense |
| 07:41 | <MikeSmith> | section elements |
| 07:41 | <MikeSmith> | ok |
| 07:42 | <MikeSmith> | so anyway I can imagine that authors might like to have a way to automatically include a generated outline in a document |
| 07:42 | <MikeSmith> | including a ToC being the most common case |
| 07:42 | <SimonSapin> | yes, for printed stuff this is a big demand |
| 07:43 | <MikeSmith> | but I can't remember actually ever hearing many authors asking for it on the whatwg list or elsewhere |
| 07:45 | <SimonSapin> | for the web not as much I guess. But WeasyPrint/PrinceXML/Antenna House are tools for printing that happen to take HTML/CSS as input more than web browsers |
| 07:47 | <SimonSapin> | (although … http://weasyprint.org/docs/tutorial/#weasyprint-navigator :) |
| 07:58 | <SimonSapin> | MikeSmith: maybe an automated toc/outline could be a WebComponent, though I have to read up on what that is |
| 07:59 | <MikeSmith> | SimonSapin: I think for the non-Web case we don't need that feature as port of the browser engine |
| 08:00 | <MikeSmith> | because those are sorta really all post-processing tools |
| 08:12 | <SimonSapin> | MikeSmith: eventually (ie. given infinite time to work on it) I’d want to have that in WeasyPrint’s engine, not in a separate processing step. Maybe something you can trigger with CSS |
| 08:13 | <SimonSapin> | but yeah, the use cases are very different from browsers |
| 08:13 | <MikeSmith> | yeah |
| 10:20 | <annevk> | Hixie: you simply fullscreen |
| 10:53 | <Ms2ger> | I guess we should define that a Document has an origin |
| 11:12 | <annevk> | Ms2ger: the main problem is that you need some "HTML knowledge" to figure out which origin to copy |
| 11:13 | <annevk> | Ms2ger: "HTML knowledge" being that the global object has an associated Document object |
| 11:13 | <Ms2ger> | It's all quite tangled, isn't it? |
| 11:13 | <annevk> | This web we weave? Indeed sir, it is tangled. |
| 11:47 | <annevk> | Did I mention I dislike percent encoding? |
| 11:48 | <Ms2ger> | You might have |
| 12:22 | <annevk> | SimonSapin: percent decode will be defined to be what you wanted it to mean |
| 12:23 | <annevk> | So the only difference between urlencoded and query is that the former does magic with U+0020 |
| 14:00 | <annevk> | fixing that was no fun |
| 21:54 | <yroc> | Hi all, I'm trying to write up some rationale in the wiki WRT content models |
| 21:55 | <yroc> | For one thing, I notice that flow content and palpable content are defined only by extension (listing of members). |
| 21:56 | <yroc> | No intensional definitions for these categories |
| 21:56 | <yroc> | Trying to understand meaning/motivation for these categories... |
| 21:56 | <yroc> | any pointers? |
| 22:43 | <Hixie> | poor yroc |
| 22:43 | <Hixie> | we keep missing each other |