| 00:09 | <jamesr> | TabAtkins_: does CSSOM return used values, or actual values? |
| 00:11 | <jamesr> | mdc claims getComputedStyle() always returns used values, but i'm not sure if i trust it |
| 00:15 | <kennyluck> | jamesr, resolved value maybe? http://dev.w3.org/csswg/cssom/#resolved-value |
| 00:15 | <jamesr> | woah |
| 00:16 | <jamesr> | so resolved = computed, except sometimes used |
| 00:16 | <jamesr> | does anything return actual values or is that supposed to be hidden away? |
| 00:25 | <TabAtkins_> | jamesr: It returns computed or used, depending on the property. |
| 00:25 | <TabAtkins_> | actual values are hidden away. |
| 00:25 | <jamesr> | cool |
| 00:26 | <TabAtkins_> | The reason for the "computed or used" is that "computed value" used to mean something different in CSS1 and 2, before 2.1. |
| 00:55 | <MikeSmith> | annevk5: about bugzilla for the Fullscreen and Encoding specs, I created a "Web Platform (other)" product |
| 00:55 | <MikeSmith> | and added those as components |
| 00:55 | <MikeSmith> | about the URL spec, we already have a "URL spec" component under the HTML WG product |
| 01:03 | <smaug____> | "The event must not be retargeted during the default phase of event dispatch." ? |
| 01:04 | <smaug____> | dglazkov: what is that? |
| 01:04 | <smaug____> | "default phase" |
| 01:23 | <roc> | TabAtkins: no browsers have manged to implement skip-free looping yet |
| 01:24 | <roc> | we were waiting to implement "loop" until we could implement it skip-free, then noticed that all other browsers had done the trivial skippy implementation, so why bother waiting |
| 01:24 | <roc> | scripted looping is as simple as <audio onended="event.target.play()"> |
| 01:38 | <zewt> | kennyluck: what's your intlfont.language.group ff pref? curious if that's what's triggering the difference |
| 01:43 | <kennyluck> | zewt, ja for the ja installer, zh-TW for the zh-TW. They are both initial vaue. |
| 01:43 | <zewt> | right. was wondering if that was the setting the installers were changing |
| 01:44 | <zewt> | at least it's easier to test that way than hanging off the system locale (don't have to reboot) |
| 01:46 | <zewt> | (taking what consolations I can get? heh) |
| 01:49 | <zewt> | changing that value from x-western to zh-TW doesn't change the output, though. |
| 01:50 | <kennyluck> | Well, since it depends on OS-locale, which probably isn't in any ff pref. |
| 01:50 | <zewt> | but you had different output with different FF installer languages, regardless of locale |
| 01:51 | <zewt> | (your output from JA and ZH installers wasn't the same as mine with an English installer) |
| 01:51 | <kennyluck> | zewt, than's true. I think that's related to default font setting. |
| 01:51 | <zewt> | the default font is per-language, though |
| 01:52 | <zewt> | mine is SimSun for simplified chinese, ... Taiwan is weird (only Monospace is set to MingLiU, the others are just generic fonts), Japanese is ms mincho/gothic |
| 01:52 | <TabAtkins> | roc: Ah, that's the event. I'd forgotten. |
| 01:53 | <zewt> | (and "allow pages to choose fonts" is turned off) |
| 01:53 | <kennyluck> | zewt, I think zh-TW l10n people do tune, say, the default font for @zh-CN lang. |
| 01:53 | <zewt> | that's pretty evil. |
| 01:54 | <zewt> | this whole thing is evil wrapped in nastiness tied up in horror |
| 01:54 | <kennyluck> | i don't know if that's real evil as OS can always switches their default font. |
| 01:54 | <zewt> | the OS doesn't pick browser fonts |
| 01:56 | <zewt> | well... i sure hope browsers aren't letting OS font renderers get their fingers into that ... |
| 01:56 | <zewt> | heh |
| 01:56 | <zewt> | but font selection is a destroyer of hope :) |
| 01:58 | <kennyluck> | It is. Though I won't consider zh pages with ja glyph as broken, but #whatwg seems to have the culture to want to standardize every single non-UI browser behavior :) |
| 01:59 | <zewt> | but Japanese users do seem to consider Japanese pages with Chinese glyphs as broken |
| 01:59 | <kennyluck> | zewt, any source about that statement? |
| 02:00 | <zewt> | kennyluck: no, just a sentiment I've heard many times--maybe ask rniwa when he's around, i've talked to him about the issue |
| 02:03 | <dglazkov> | smaug____: afk, can you file a bug? |
| 02:03 | <smaug____> | dglazkov: will do |
| 02:21 | <smaug____> | dglazkov: though, the spec seems to lack all the declarative part |
| 02:21 | <smaug____> | no way to use external components |
| 02:21 | <smaug____> | I guess I'll read the document once those are added. hard to judge anything before that |
| 02:22 | <smaug____> | hmm, or is there some other document explaining more... |
| 02:46 | <cartes9> | hello |
| 02:47 | <cartes9> | http://www.w3.org/QA/2008/01/html5-is-html-and-xml.html |
| 02:47 | <cartes9> | http://www.la-grange.net/2009/07/05/html5-xhtml5/ |
| 02:47 | <cartes9> | are these documents still valid? |
| 02:53 | <MikeSmith> | cartes9: yeah |
| 02:53 | <MikeSmith> | in that they are describing what the spec says is valid |
| 02:54 | <cartes9> | i see... that is what i was wondering.. too |
| 02:54 | <cartes9> | i told one member in the group that i'm trying to translate this |
| 02:54 | <cartes9> | document. |
| 02:55 | <cartes9> | and he was pointing out how old these are. |
| 02:56 | <cartes9> | i thought it didn't matter because core parts usually don't change even it's after a couple years |
| 03:00 | <cartes9> | MikeSmith thanks |
| 03:49 | <MikeSmith> | there's no way to link to specific comments in G+, I guess |
| 03:50 | <MikeSmith> | wanted to directly link to a clarifying comment that Joel Webber made to his G+ posting about the Shadow DOM spec |
| 03:54 | <smaug____> | ugh, is there some spec discussion happening in G+ |
| 03:55 | <jamesr> | you can't talk about that there! talk about it over here or shut up! #freespeech |
| 03:59 | <MikeSmith> | heh |
| 04:00 | <MikeSmith> | https://plus.google.com/111111598146968769323/posts/4L2voQVzswx |
| 04:01 | <MikeSmith> | «The way things work right now, there's absolutely no way to create, e.g., a single "LabeledInput" element that's comprised of multiple existing elements, then treat it as a single logical element.» |
| 04:01 | <MikeSmith> | etc. |
| 04:07 | <jamesr> | yeah, replied on that thread |
| 04:07 | <jamesr> | i'm really happy people are talking about this stuff |
| 04:09 | <MikeSmith> | jamesr: good clarification |
| 04:09 | <MikeSmith> | dglazkov should mine those comments for text to put into the intro of the document |
| 07:29 | <annevk> | MikeSmith: ah, didn't know about that component (URL spec)! |
| 07:29 | <annevk> | MikeSmith: moved the bug there |
| 07:29 | <annevk> | guess I'll now add a reference to the bug database from each spec |
| 07:30 | <kennyluck> | that would be nice indeed |
| 07:32 | <annevk> | I like this "participate" box I added to all specs, I wonder if people make use of it or just skip it not knowing it's there |
| 07:35 | <erlehmann> | BE PART OF THE CREW |
| 07:35 | <erlehmann> | LIKE THIS ON GOOGLITTER |
| 07:35 | <erlehmann> | :3 |
| 07:37 | <annevk> | morning erlehmann |
| 07:37 | <erlehmann> | ohai |
| 07:37 | <kennyluck> | People who are here certainly don't need it but it seems useful to newcomers. |
| 07:37 | <erlehmann> | :3 |
| 07:45 | <kennyluck> | annevk, why does public-webapps⊙wo link to a mailto: URI instead of http://lists.w3.org/Archives/Public/public-webbapps/ by the way? I never find mailto: URI useful but I can't speak for others. And ?subject= does serve a use case. |
| 07:49 | <annevk> | you mean in DOM? |
| 07:49 | <annevk> | I can add an archives link there |
| 07:50 | <annevk> | whatwg links to mailing-list because you need to subscribe and such |
| 07:50 | <kennyluck> | I am looking at dvcs.w3.org/hg/xhr/raw-file/tip/Overview.html |
| 07:50 | <annevk> | does it help if I add (archives) after the mailto: links? |
| 07:50 | <annevk> | with "archives" being a link |
| 07:50 | <kennyluck> | annevk, I think so. |
| 07:51 | <annevk> | k will do |
| 07:53 | <kennyluck> | Though before starting to use a offline mail client I used to moan everytime I misclicked a mailto: URI. |
| 07:55 | <annevk> | ah right |
| 07:56 | <annevk> | most browsers implement registerProtocolHandler now |
| 08:02 | <annevk> | whoa, back in the days W3C got a lot of spam: http://lists.w3.org/Archives/Public/ietf-charsets/2004JanMar/ |
| 08:14 | <annevk> | kennyluck: so if I list you in the acknowledgment section, how do I go about that? |
| 08:15 | <kennyluck> | annevk, "Kang-Hao Lu" I guess. Thanks by the way. |
| 08:16 | <annevk> | kennyluck: I can try Unicode if you prefer |
| 08:17 | <kennyluck> | annevk, well, "呂康豪（Kang-Hao Lu）" then. |
| 08:18 | <kennyluck> | Not sure if that's too many characters :p |
| 08:18 | heycam | steals those characters for his spec's acknowledgements section too! :) |
| 08:19 | <annevk> | kennyluck: is that sorted after Z? :) |
| 08:19 | <annevk> | I guess I'll sort you under K to keep it "simple" |
| 08:20 | <kennyluck> | that makes sense. |
| 08:20 | <heycam> | I'm using romanisation of family name as the sorting position |
| 08:20 | <annevk> | heycam: how do you deal with Ms2ger? |
| 08:21 | <heycam> | just sorted under M |
| 08:21 | <kennyluck> | good question. |
| 08:21 | annevk | likes first name |
| 08:21 | <annevk> | well, "name" |
| 08:21 | <annevk> | kennyluck: seems somewhere along the line the characters got converted into character references, but should still be okay |
| 08:22 | <annevk> | http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#acknowledgments |
| 08:40 | <annevk> | kennyluck: maybe I should use non-Kanji (is it Kanji?) parenthesis? |
| 08:42 | <annevk> | thanks zcorpan for writing in the enum bug what I didn't do |
| 08:43 | <kennyluck> | annevk, you could. (My habit is to use ideograph parenthesis as much as possible but I don't particularly care about this). And yeah, it's Kanji or Han character. |
| 08:44 | <annevk> | kennyluck: it looks kind of weird with the comma following it |
| 08:44 | <kennyluck> | ok |
| 08:44 | <annevk> | kennyluck: but if it's semantically more correct, I'm fine with letting it stay and have font designers take care of it some day |
| 08:45 | <annevk> | s/semantically// |
| 08:45 | <kennyluck> | annevk, I know nothing about semantics. |
| 08:45 | <kennyluck> | no it's not. |
| 08:45 | <annevk> | k |
| 08:52 | <erlehmann> | annevk, what about the font designers? |
| 08:52 | <erlehmann> | looks correct to me here |
| 08:52 | <annevk> | I just changed it |
| 08:53 | <annevk> | mostly about "）," vs ")," |
| 08:55 | <erlehmann> | but unicode was developed by 🔰 𝗧𝗬𝗣𝗢𝗚𝗥𝗔𝗣𝗛𝗬 𝗘𝗫𝗣𝗘𝗥𝗧𝗦 |
| 08:58 | <kennyluck> | What is 🔰? lol |
| 08:58 | <erlehmann> | kennyluck, 🔰 U+1F530 JAPANESE SYMBOL FOR BEGINNER |
| 09:00 | <kennyluck> | huh, I do remember this symbol from an episode of Doraemon. I think that was Nobita driving as a beginner. |
| 09:01 | <erlehmann> | i use it to denote that something is sarcastic. when i talk about 🔰 𝗘𝗫𝗣𝗘𝗥𝗧 𝗣𝗥𝗢𝗚𝗥𝗔𝗠𝗠𝗘𝗥𝗦 it is probably useful to have a symbol like that prefix the statement. |
| 09:03 | <woef> | spec developers talking about special font characters in anime. |
| 09:03 | <woef> | There is no known geek scale to measure such activity. |
| 09:04 | <erlehmann> | http://en.wikipedia.org/wiki/Bamboo-copter |
| 09:05 | <annevk> | woef: lol |
| 09:09 | <erlehmann> | woef, slightly related, it is uncanny sometimes how i fit a cliche: i was at a friend's birthday last night. as everyone left or slept, he explained to me the inner workings of his wiki and we proceeded to find out how to best implement focus stealing prevention for the window manager he wrote. turns out chromium does weird stuff with windows. if i had a sense of fashion, i could be a great nerdy hipster! |
| 09:10 | <woef> | I'm never going to invite you to one of my birthdays :p |
| 09:11 | <erlehmann> | woef, but don't you want to know … ABOUT THE XLIB? |
| 09:12 | <woef> | Usually I like things preceded by X- ... geek-territory is an exception I'm afraid. |
| 09:12 | <zcorpan> | X-mas? |
| 09:13 | <erlehmann> | i predict you will never become an 🔰 𝗘𝗫𝗣𝗘𝗥𝗧 𝗣𝗥𝗢𝗚𝗥𝗔𝗠𝗠𝗘𝗥 if you continue on this path! |
| 09:13 | <woef> | Sure, why not. As long as there's presents |
| 09:13 | <woef> | Oh, but I am not a programmer! html is not even a proper language :D |
| 09:13 | <woef> | I'm just a semantics-buff. |
| 09:14 | <zcorpan> | why is it not a language? |
| 09:14 | <woef> | I get angry when people use .news on overview page and .article on the detail page. |
| 09:14 | <woef> | *programming language |
| 09:14 | <zcorpan> | ah |
| 09:14 | <woef> | Or not propper code. |
| 09:14 | <woef> | I dunno, there was a fuss about that 5 or 10 years ago. |
| 09:15 | <woef> | We couldn't call ourselves coders :) |
| 09:15 | <zcorpan> | of course not. it's not a programming language. you're AUTHORS :-) |
| 09:16 | <woef> | I'm a "Front-end Developer" now. |
| 09:16 | <woef> | I'm quite happy with that. |
| 09:17 | <woef> | Front-end author ... sounds quite artistic. |
| 09:17 | <zcorpan> | heh |
| 09:17 | <woef> | It could improve my hipster rating. |
| 09:19 | <erlehmann> | today in tasteless fun: read the breivik manifesto, replace „cultural marxism“ with „hipsterisation“. corollary: search and replace makes even the most despicable reactionaries kind-of-funny at times. |
| 09:32 | <Ms2ger> | annevk, setcapture is an IEism |
| 09:35 | <annevk> | Ms2ger: so proprietary to two browsers |
| 09:35 | <annevk> | ugh :( |
| 09:59 | <annevk> | MikeSmith: updated specs to make use of the new bug components |
| 09:59 | <MikeSmith> | cool |
| 10:23 | <annevk> | zewt: https://www.w3.org/Bugs/Public/show_bug.cgi?id=13408 is about what I meant the other day |
| 10:23 | <annevk> | MikeSmith: I'm going through the LC bugs but I cannot really find anything bad, most bugs seem valid thus far |
| 10:23 | <annevk> | MikeSmith: or have such a long argument that I gave up |
| 10:24 | <MikeSmith> | ok |
| 10:29 | <annevk> | feel free to ping me if the situation changes, but I'll try to monitor it every now and then |
| 10:53 | <annevk> | foolip: when I try to commit a change to the spec-splitter on html5.org I get |
| 10:53 | <annevk> | svn: Server sent unexpected return value (405 Method Not Allowed) in response to MKACTIVITY request for '/svn/!svn/act/cea8c09a-d6dc-4c98-821c-70215e3ba403' |
| 10:53 | <david_carlisle> | annevk: v.nu still unhappy about normal forms |
| 10:53 | <david_carlisle> | http://validator.nu/?doc=http%3A%2F%2Fwww.whatwg.org%2Fspecs%2Fweb-apps%2Fcurrent-work%2Fmultipage%2Fnamed-character-references.html |
| 10:54 | <annevk> | david_carlisle: oh |
| 10:54 | <annevk> | I wonder how this goes wrong then |
| 10:55 | <annevk> | parser maybe :( |
| 10:55 | <david_carlisle> | annevk: I'd look but the office is shutting down around me, closing for some holiday or other |
| 10:56 | <annevk> | heh |
| 10:56 | <annevk> | guess I should study the input |
| 10:59 | <annevk> | so the input to the parser is ⟨ |
| 10:59 | <jgraham> | annevk: I think svn is telling you to use another version control system |
| 11:00 | <annevk> | which yields ⟨ |
| 11:00 | <annevk> | which is correct |
| 11:00 | <annevk> | so somehow that is mangled :( |
| 11:03 | <annevk> | why would those be mangled and nothing else? |
| 11:07 | <annevk> | oh, maybe because in Python they have some kind of meaning http://en.wikipedia.org/wiki/Bracket ? |
| 12:24 | <foolip> | annevk, did you fix it? |
| 12:25 | <annevk> | no |
| 12:25 | <annevk> | bug is here: https://www.w3.org/Bugs/Public/show_bug.cgi?id=12539 |
| 12:30 | <foolip> | annevk, so was the problem that I forgot some file? |
| 12:30 | <foolip> | and now you can't commit it? |
| 12:31 | <annevk> | oh that was a different issue |
| 12:31 | <annevk> | I tried to change spec-splitter.py to fix an issue and I could not commit my change to svn |
| 12:31 | <annevk> | but my fix was not a fix so it doesn't really matter |
| 12:31 | <foolip> | I don't think the SVN problem is my fault, it's Google code's SVN server, right? |
| 12:32 | <annevk> | yeah |
| 12:32 | <annevk> | could be my fault |
| 12:33 | <annevk> | but I think I followed the instructions |
| 12:45 | <annevk> | MikeSmith: can we move http://dev.w3.org/2006/webapi/progress/ to dvcs? |
| 12:45 | <annevk> | MikeSmith: I think that's my last dev.w3.org draft now I quit CSS |
| 12:45 | <annevk> | MikeSmith: saying goodbye to dev.w3.org would be nice |
| 13:08 | <woef> | could itemscope be implied when itemtype is added to an element? |
| 13:09 | <woef> | microdata is quite verbose |
| 13:11 | <jgraham> | I believe that was tried when we did a user study with microdata and people found this design easier to comprehend |
| 13:12 | <jgraham> | Even though it is clearly more verbose |
| 13:27 | <webben> | annevk: Who (if anyone) has taken over CSSOM work? |
| 13:29 | <annevk> | glenn adams / shane stephens |
| 13:29 | <annevk> | jgraham: woef: maybe we should do another study though |
| 13:29 | <annevk> | this is a pretty consistent piece of feedback |
| 13:31 | <woef> | Also (but this might be google's implementation) ... i don't seem to be able to nest itemprops |
| 13:32 | <annevk> | http://blog.whatwg.org/weekly-shadow-encoding-fun |
| 13:32 | <woef> | <div itemprop="name"><span itemprop="givenName">Niels</span> <span itemprop="familyName">Matthijs</span></div> |
| 13:32 | <woef> | This ain't working for Google. |
| 13:35 | <wilhelm> | I like how W3C stores my member password as plain text. |
| 13:42 | <annevk> | "congratulations your paper 8 - What XML can learn from HTML; also known as XML5 was accepted for XML Prague 2012 conference." |
| 13:43 | <jgraham> | You are throwing yourself to the wolves? |
| 13:43 | <annevk> | seems I'm gonna explain XML5 one more time :) |
| 13:45 | <jgraham> | wilhelm: Yeah, I never felt that "we failed web security 101" was a great advert for W3C's credentials to lead the web to it's full potential |
| 13:46 | <annevk> | jgraham: I'm curious, mostly |
| 13:47 | <annevk> | jgraham: they've been quite upset with us, so maybe it helps if they can yell at someone in person |
| 13:47 | <annevk> | preferably over a nice Chech beer |
| 14:03 | <MikeSmith> | annevk: https://dvcs.w3.org/hg/progress |
| 14:03 | <MikeSmith> | didn't copy the spec over but can do that too if you want |
| 14:25 | <Philip`> | annevk: Do you know if the input to spec-splitter script says "⟨" or "⟩"? |
| 14:25 | <Philip`> | (or 27E8 or whatever) |
| 14:26 | <Philip`> | I'd guess it's the former, and lxml is parsing into a U+9001, in which case maybe the most robust solution is for Hixie's scripts to generate the numeric code instead of the name |
| 14:29 | <Philip`> | Ah, single-page version says |
| 14:29 | <Philip`> | <tr id=entity-LeftAngleBracket><td> <code title="">LeftAngleBracket;</code> </td> <td> U+027E8 </td> <td> <span class=glyph title="">⟨</span> </td> |
| 14:30 | <Philip`> | and similar when defining entity-lang |
| 14:31 | <MikeSmith> | Philip`: yeah |
| 14:31 | <Philip`> | The glyphs are explicitly non-normative but it still seems a bit circular to use ⟨ in the spec's definition of ⟨ |
| 14:31 | <MikeSmith> | but I'm not sure using the numeric code will fix it |
| 14:32 | <Philip`> | Why not? |
| 14:32 | <MikeSmith> | I think I might have tried that already |
| 14:32 | <MikeSmith> | dunno |
| 14:32 | <MikeSmith> | hmm |
| 14:32 | <MikeSmith> | that would certainly be the easiest fix though |
| 14:32 | <Philip`> | As far as I'm aware, there's no code that attempts any fancy normalisation or anything - the only way the U+9001 could get introduced is via lxml's entity table, probably |
| 14:32 | <MikeSmith> | OK |
| 14:33 | <Philip`> | (But I could be wrong) |
| 14:33 | <gsnedders> | Philip`: How much does the spec-splitter depend on lxml? |
| 14:33 | <MikeSmith> | well, easy enough to test |
| 14:33 | <gsnedders> | Philip`: If not that much, you can probably get good enough perf with PyPy |
| 14:33 | <Philip`> | annevk: Re 405 Method Not Allowed: Are you behind some kind of HTTP proxy? (They often dislike SVN's special HTTP methods) |
| 14:34 | <Philip`> | gsnedders: It works with the html5lib parser, but I'm not aware of anything that can make html5lib magically go fast |
| 14:35 | <Philip`> | though "good enough" just depends on whether whoever's running the script can spare the CPU time |
| 14:35 | <annevk> | Philip`: it says the latter |
| 14:35 | <annevk> | Philip`: ooh |
| 14:35 | <gsnedders> | Philip`: PyPy is about twice the speed as CPython as parsing the spec, at least |
| 14:35 | <Philip`> | gsnedders: Twice as fast as "extremely slow" is not fast :-( |
| 14:35 | <annevk> | Philip`: http://svn.whatwg.org/webapps/entities-unicode.inc suggests the latter |
| 14:36 | <annevk> | Philip`: but it would make sense if it was ⟨ |
| 14:36 | <annevk> | Philip`: I mean given the historical mappings |
| 14:36 | <Philip`> | Maybe something like Anolis outputs named entities instead? |
| 14:36 | <Philip`> | (given that numeric input) |
| 14:36 | <Ms2ger> | Probably |
| 14:37 | <gsnedders> | Philip`: Dunno, it depends on what serializer you use |
| 14:37 | <gsnedders> | IIRC html5lib does that |
| 14:38 | <annevk> | html5.org does not have html5lib |
| 14:38 | <Philip`> | Maybe the html5lib serializer shouldn't emit ⟨/⟩ since they're not backward compatible |
| 14:38 | <annevk> | html5.org uses the default settings of spec-splitter |
| 14:39 | <Philip`> | Who's running Anolis on the spec (before the spec-splitter sees it)? |
| 14:39 | <annevk> | it uses etree.HTMLParser and etree.tostring |
| 14:39 | <annevk> | good point |
| 14:39 | <annevk> | that's jgraham |
| 14:39 | <annevk> | maybe he's the culprit |
| 14:40 | <annevk> | hadn't thought of that |
| 14:40 | <Philip`> | If he can configure it to output numeric entities, that should minimise problems |
| 14:40 | <Philip`> | (It's a problem for anybody using an old HTML parser on the single-page spec, as well as for the multi-page spec) |
| 14:41 | <gsnedders> | Philip`: It should be exposed as an option, so it's whatever URL Hixie uses |
| 14:43 | <annevk> | Philip`: on the other hand, the main spec does not have this problem? or does it? |
| 14:44 | <Philip`> | annevk: The single-page spec says "⟨" in it, so old parsers will parse into U+9001 or whatever it was |
| 14:44 | <Philip`> | but validator.nu will parse it into the newer U+27E8 so it won't cause validation errors |
| 14:45 | <annevk> | oh I see |
| 14:45 | <annevk> | so jgraham needs to fix it then |
| 14:45 | <Philip`> | Oh, I'm getting confused by decimals |
| 14:45 | <annevk> | thanks Philip` |
| 14:47 | <Philip`> | (U+2329, not U+9001) |
| 14:47 | <Philip`> | (although I'm mixing up lang and rang anyway, but the details don't really matter) |
| 14:47 | <jgraham> | Hmm, should I have been paying attention? |
| 14:48 | <Philip`> | jgraham: Summary: Are you running the spec's Anolis? If so, can you make it emit numeric character references instead of named? |
| 14:50 | <jgraham> | Hmm, html5lib doesn't support that? So yes, but I guess html5lib needs a patch. Or that option needs to be exposed in anolis if it isn't already |
| 14:50 | jgraham | quite likes just using UTF8 really |
| 14:51 | <Philip`> | UTF-8 will probably mess up diffs etc |
| 14:52 | <Philip`> | Can't you use the html5lib serializer with resolve_entities=False ? |
| 14:52 | <jgraham> | Why would it mess up diffs? |
| 14:52 | <Ms2ger> | resolve_entities=True|False? |
| 14:53 | <annevk> | jgraham: ⟨ emits the wrong code point in a number of implementations |
| 14:53 | <Philip`> | Diffs get posted to mailing lists etc, and I wouldn't be surprised if something in the chain wasn't UTF-8-aware and messed it all up, so it's safer if the spec is purely ASCII |
| 14:53 | <annevk> | jgraham: and since the input is not ⟨ but a numeric character reference (which does work) it breaks down the line |
| 14:53 | <annevk> | ooh |
| 14:53 | <annevk> | personally I'm fine with UTF-8 |
| 14:54 | <annevk> | I changed multipage to UTF-8 |
| 14:54 | <jgraham> | Philip`: I'm pretty sure the Hixie approach is to do the right thing and say other people should fix their processors to deal with UTF8 |
| 14:54 | <Philip`> | Also, it's hard to visually read the diff between e.g. "〈 and "⟨", and easier if they're "&#....;" instead |
| 14:56 | <Philip`> | and it's hard to read HTML source that uses U+00A0 instead of " " etc |
| 14:58 | <annevk> | anyone interested in becoming a manager on the +WHATWG page? |
| 15:00 | <annevk> | jgraham: given that Hixie usually writes ASCII-compatible documents, I wouldn't be so sure of that |
| 15:02 | <gsnedders> | Hixie's position has been that ASCII-compatible documents are less hassle. |
| 15:03 | <jgraham> | Well it's not my fault if he has one standard for HTML and another for text |
| 15:04 | <jgraham> | Anyway, resolve_entities might possibly be exposed in the HTTP frontend now |
| 15:05 | <annevk> | jgraham: can you update https://www.w3.org/Bugs/Public/show_bug.cgi?id=12539 with status on this issue? |
| 15:09 | <Philip`> | jgraham: Does that mean Hixie needs to change how he calls it? |
| 15:09 | <annevk> | WHATWG Blog has 6999 subscribers in Google Reader now |
| 15:10 | <Philip`> | This spec-generation process seems to require cooperation between absurdly many people :-/ |
| 15:10 | <Philip`> | (including people like me who are rubbish at responding to bugmail or at getting around to doing anything in general, so it takes forever to fix trivial issues) |
| 15:11 | <annevk> | I think your server is no longer used |
| 15:11 | <Ms2ger> | Philip`, speaking of bugmail... |
| 15:11 | <Ms2ger> | Happen to have time for canvas? |
| 15:11 | <annevk> | but it's still 3 distinct people which is a bit much |
| 15:16 | <zewt> | Philip`: your arguments against UTF-8 feel a bit contrived to me, FWIW |
| 15:17 | <jgraham> | Philip`: Well it isn't very clever and treats missing values as False due to the slightly retarded HTML form submission algorithm |
| 15:18 | <jgraham> | So, I guess he will pick up the change next time he generates the spec |
| 15:18 | <zewt> | sure it's hard to tell similar-looking characters apart, but numeric references are essentially *impossible* to read at all, unless you happen to have a savant-level rote memorization ability |
| 15:18 | jgraham | feels kind of bad about just switching the default like that |
| 15:19 | <Philip`> | Ms2ger: Hmm, I suppose I no longer have the excuse of PhD-related work distracting me, though Christmas might be a sufficiently believable distraction |
| 15:19 | Ms2ger | glares towards Philip` |
| 15:19 | <jgraham> | You could claim to be santa claus |
| 15:19 | <Ms2ger> | And hand out test failures |
| 15:20 | <Philip`> | I suppose it would be technically feasible to spend more time on canvas-related stuff and less time on witchering |
| 15:20 | <jgraham> | "witchering"? |
| 15:22 | <Philip`> | http://www.gog.com/en/gamecard/the_witcher |
| 15:29 | <annevk> | Ms2ger: I don't get https://bitbucket.org/ms2ger/dom-core/changeset/c3ae3775d5d3 |
| 15:30 | <annevk> | oh now I do |
| 15:30 | <Ms2ger> | Yeah, it's awful |
| 15:30 | <annevk> | Ms2ger: how is that first <style> element magically removed? |
| 15:30 | <Ms2ger> | title + style |
| 15:30 | <Ms2ger> | Because style can't have class in HTML4 |
| 15:31 | <annevk> | oh, but now it's HTML |
| 15:31 | <annevk> | so maybe we kill that hack |
| 15:31 | <annevk> | should kill* |
| 15:31 | <Ms2ger> | Can we get away with that already? |
| 15:32 | <annevk> | someone told me that changed, yes |
| 15:32 | <Ms2ger> | That would certainly be nice |
| 15:32 | <annevk> | I think it was shepazu and/or MikeSmith |
| 15:50 | <billyjack> | radio check |
| 15:51 | <Ms2ger> | Can hear you loud and clear |
| 15:51 | <billyjack> | heh |
| 15:51 | <billyjack> | android irc client |
| 16:17 | <dglazkov> | good morning, Whatwg! |
| 16:46 | <JonathanNeal> | hiya |
| 17:25 | <EricInBNE> | when do ppl expect postMessage to be finalised? |
| 17:26 | <EricInBNE> | Hixie, any thoughts? |
| 17:28 | <zewt> | define "finalized" |
| 17:29 | <EricInBNE> | zewt, like how websockets was just blessed. This url http://dev.w3.org/html5/postmsg/ implies it's a draft. |
| 17:30 | <EricInBNE> | before websockets got the tick it seemed like there were quite a few changes |
| 17:30 | <zewt> | i doubt postMessage will see backwards-incompatible changes, since it's deployed and in use, but it could see new features in the future, so it's not "finalized" per se--no web API is |
| 17:31 | <EricInBNE> | ive written some postMessage code and it works in chrome but not firefox. I havent tested it in IE 10. |
| 17:31 | <zewt> | (also, which "postMessage"--there are different related APIs with that method name) |
| 17:31 | <zewt> | window.postMessage? port.postMessage? |
| 17:31 | <EricInBNE> | really? |
| 17:32 | <EricInBNE> | yeah ive been using window.postMessage. what's port.postMessage? |
| 17:32 | <zewt> | http://dev.w3.org/html5/postmsg/#channel-messaging |
| 17:33 | <EricInBNE> | oh awesome. thats what i want |
| 17:33 | <zewt> | (i don't know the status of window.postMessage; i've only used ports, for workers) |
| 17:34 | <Ms2ger> | <doron> html is garbage no matter what! |
| 17:34 | <zewt> | okay? |
| 17:34 | <EricInBNE> | zewt, so if the user opens two browser windows (say example.org and google.com) ports can pass messages even if their is no parent child relationship? |
| 17:34 | <zewt> | you have to have a way to get a port from one to the other |
| 17:35 | <zewt> | for that, you're looking for cross-document messaging, not port messaging |
| 17:35 | <zewt> | which it sounds like you've been using |
| 17:36 | <EricInBNE> | zewt, yeah, ive been using window.open, but the popup blocker somewhat ruins the situation |
| 17:36 | <zewt> | i havn't tried using it, but if you pastebin some code that works in one browser and not another, somebody might tell you why (the answer may simply be "stuff not yet implemented in some browser") |
| 17:36 | <EricInBNE> | i imagine that is the case (not yet implemented) |
| 17:37 | <EricInBNE> | caniuse.com should come with a guide - caniuse caniuse.com? (the answer would be a resounding no) v unreliable. |
| 17:38 | <zewt> | apis generally are going to have subsets of implemented features you can use, and new features you probably can't yet, so it's not a simple API-wide yes or no once you get into the details |
| 17:41 | <zewt> | (for example, iirc FF8 doesn't implement MessageChannel; you get the port messaging that's attached to workers, but you can't yet create new channels) |
| 19:45 | smaug____ | is starting to think that sync APIs should be removed also from workers, just to keep APIs simple and consistent |
| 19:46 | <zewt> | that'd defeat a major purpose of workers |
| 19:46 | <zewt> | being able to write linear code |
| 19:46 | <smaug____> | not sure that is a major purpose of workers |
| 19:47 | <zewt> | i am |
| 19:47 | <smaug____> | the major purpose is to move stuff out from the main thread |
| 19:47 | <zewt> | i did say "a" |
| 19:47 | <zewt> | not "the" |
| 19:47 | ap | thinks that the nice (albeit nearly useless) idea of not adding new functionality to sync requests in document has been blown way, way out of proportion |
| 19:47 | <Ms2ger> | ap, well, we care about a clean web |
| 19:48 | <zewt> | doesn't seem useless to me |
| 19:48 | <ap> | Ms2ger: there is step 2 missing between "disable" and "get a clean web", I'm afraid |
| 19:48 | <zewt> | if it convinces people to not write sync code in the main thread when they otherwise would have |
| 19:49 | <zewt> | i wouldn't call it a *huge* benefit, but it does seem like a win |
| 19:49 | <ap> | people were making sync XHR 5 years ago, before there was CORS or responseType. They won't stop doing that because we remove CORS or responseType from sync requests now |
| 19:50 | <ap> | so yes, not supporting new features is nice, slightly helpful and cheap |
| 19:50 | <zewt> | but if they want to use new features, they'll have to take a step back and notice that what they're doing is wrong |
| 19:50 | <smaug____> | yeah, that is the point |
| 19:50 | <zewt> | if they decide they'd rather make crappy pages, well, not much we can do about that in the end |
| 19:52 | <zewt> | if it was a huge pain to implement then yeah it might not be worth it |
| 19:52 | <ap> | wanting to support new features is more in library author domain. When you've been making your sync XHR request to your SAP server since the last ice age, you're not going to notice CORS |
| 19:52 | <ap> | (and library authors don't appear to be in need of convincing) |
| 19:52 | <zewt> | people who are using old APIs to do old things simply aren't affected either way; nothing we can do about them |
| 19:53 | <zewt> | i just don't know what your objection is |
| 19:53 | <zewt> | do you think it's hard to implement? |
| 19:53 | <zewt> | the cost and the benefits seem about at par |
| 19:53 | <ap> | no, not very hard (although that's also a consideration) |
| 19:54 | <ap> | I just don't want to take any risk of breaking existing content when the benefit is so tiny and unlikely to materialize |
| 19:54 | <zewt> | i wonder if snipy webkit guy is going to clarify what he means by calling me "self-conflicted". heh |
| 19:54 | <ap> | what jQuery already did appears to be an order of magnitude more important than what engines can achieve |
| 19:54 | <ap> | "self-conflicted"? |
| 19:57 | ap | assumes that there is another snipy webkit guy somewhere, and this comment wasn't about himself :) |
| 19:57 | <zewt> | not you :) |
| 19:58 | <zewt> | (sorry, I don't really know who you are :) |
| 19:58 | <smaug____> | ap: benefits of getting rid of sync XHR small? |
| 19:58 | <smaug____> | well, ofc these are the first steps |
| 19:58 | <Ms2ger> | zewt, meet Alexey Proskuryakov, other snipy webkit guy :) |
| 19:58 | <ap> | zewt: I'm the guy who intends to prevent disabling already shipping sync XHR functionality in WebKit |
| 19:59 | <smaug____> | I hope we could start adding warnings about using sync xhr in window context |
| 19:59 | <zewt> | (FYI: i do make the allowance that everyone's allowed to be snipy once in a while, for the selfish reason that it allows me to be from time to time) |
| 19:59 | <Ms2ger> | *Intends to stop any attempts to improve the web |
| 19:59 | <smaug____> | and then finally, maybe in one or two years, get rid of it |
| 19:59 | <Ms2ger> | ftfy |
| 19:59 | <smaug____> | we're trying to get rid of other bad APIs |
| 19:59 | <ap> | smaug____: that's what I allude to by saying that I don't see step 2. Warning for every use seem meaningful, but then I don't see how disabling withCredentials helps |
| 19:59 | <smaug____> | (like Attrs as Nodes) |
| 20:00 | <zewt> | smaug____: it'd be nice, but if there was a betting pool I'd put my money squarely on the other side |
| 20:00 | <zewt> | ("good luck, but I doubt it") |
| 20:00 | <smaug____> | also, we're trying to get rid of Mutation events |
| 20:00 | <smaug____> | they are used surprisingly often |
| 20:01 | <ap> | smaug____: as far as Attrs as nodes are concerned - did someone come up with a plan for XPath? |
| 20:01 | <smaug____> | Ms2ger: ^^ |
| 20:02 | <smaug____> | though, I'm not sure why you'd need Attrs as nodes for XPath |
| 20:02 | <smaug____> | are there some common use cases ? |
| 20:03 | <TabAtkins> | Xpath needs attrs as "nodes" for its selection model. They dont' need to be real Nodes, though, in the DOM sense. |
| 20:03 | <TabAtkins> | They just need to be on equal footing with elements and namespaces in the XPath data model. |
| 20:04 | <ap> | smaug____: XPath can return found attributes as nodes. If the plan is to filter those out from result node set before exposing it to a JavaScript caller, that's a valid plan that can be investigated |
| 20:05 | <ap> | smaug____: as TabAtkins explains, XPath totally needs to treat attributes on equal footing with other nodes internally, but that doesn't really affect whether we can get rid of Attr in DOM |
| 20:06 | <smaug____> | yes, that is what I was saying. I don't know why Attrs would need to be nodes for XPath |
| 20:06 | <smaug____> | need to change some APIs though |
| 20:06 | <smaug____> | to support both Nodes and Attrs |
| 20:06 | <ap> | smaug____: I can easily suggest some use cases, but I don't know if they are actually encountered in real life |
| 20:07 | <ap> | smaug____: e.g. change all "class=foo" attributes in a subtree to "class=bar" |
| 20:07 | <ap> | smaug____: XPath will find them for you, and you'll iterate |
| 20:08 | <ap> | smaug____: in addition to filtering attributes out, another plan is to return non-homogenous node sets, having both node and non-node objects. I don't think that I like this option |
| 20:10 | <TabAtkins> | ap: Of course, you can also use XPath to return the *elements* with those attributes, then iterate and change them. (Or use Selectors to do the same.) |
| 20:12 | <ap> | TabAtkins: that's somewhat less efficient, but probably negligibly so. Arguably more complicated for authors, too |
| 20:13 | <ap> | TabAtkins: it's hard to find _any_ use case for XPath that couldn't be served by Selectors pretty much as well :) |
| 20:13 | <TabAtkins> | Yes, it's slightly more complicated in XPath to write such a query. |
| 20:13 | <annevk> | authors never ever deal with Attr nodes |
| 20:13 | <ap> | TabAtkins: same goes in opposite direction too |
| 20:13 | <annevk> | so I'm not sure if they suddenly have to deal with them it'd be simpler |
| 20:13 | <TabAtkins> | Agreed on Selectors/XPath equivalency. I recall writing a thread to that effect. ^_^ |
| 20:14 | <smaug____> | ap: selectors don't handle textnodes |
| 20:15 | <ap> | smaug____: good point |
| 20:15 | <TabAtkins> | ...yet |
| 20:15 | <TabAtkins> | (Probably never, for CSS's subset of Selectors. But there's no good reason to disallow it from JS's Selectors.) |
| 20:16 | <ap> | Need to run an errand now. Thanks everyone for a useful discussion! |
| 20:17 | <ap> | annevk: (one last notice - may I use your comment that "authors never ever deal with Attr nodes" as an argument against removing them? ;-) ) |
| 20:18 | <Ms2ger> | No |
| 20:18 | <Ms2ger> | Only as one in favour |
| 20:18 | <annevk> | heh, I guess I meant they shouldn't have to deal with them; some probably do anyway because they are there and well, look, features |
| 20:18 | <annevk> | like Facebook was using them, but not because they had a reason |
| 20:19 | <annevk> | Ms2ger: btw, having include support in Anolis |
| 20:20 | <annevk> | Ms2ger: like <!--something.tmpl--> would be sweet |
| 20:20 | <Ms2ger> | It would |
| 20:20 | <Ms2ger> | Does html5lib support fragment parsing? |
| 20:20 | <annevk> | Ms2ger: I generate some stuff for the Encoding Standard and end op copy and pasting things |
| 20:20 | <annevk> | Ms2ger: I'd be happy with a pre-processing step |
| 20:21 | <annevk> | but I think it implements that, yes |
| 20:21 | <Ms2ger> | Then it shouldn't be too hard |
| 20:22 | <annevk> | I'm changing the way I deal with undefined code points |
| 20:22 | <Ms2ger> | I'll get to it at some point, I guess |
| 20:22 | <annevk> | set them to null rather than U+FFFD |
| 20:22 | <annevk> | also makes more sense when you want to encode using a legacy encoding |
| 20:28 | <zewt> | annevk: what happens if a UA wants to suspend scripts when backgrounded (mobile), but keep XHR downloads going? wouldn't that cause tons of onprogress events to back up in the event queue? can't find any sort of "progress events might be delayed arbitrarily by the browser" escape clause that allows not doing that |
| 20:30 | <annevk> | hardware limitation? |
| 20:31 | <zewt> | battery |
| 20:32 | <zewt> | i'd think it would be better to allow this explicitly than force browsers to use that particular clause... |
| 20:32 | <kennyluck> | are browses following per 50ms by the way? |
| 20:33 | <zewt> | for example, perhaps say that when a new progress event task is queued, any progress event tasks still in the queue on the same object are removed |
| 20:33 | <zewt> | that would also have the nice property (i think) that if an onprogress takes too long, they'll never back up more than one deep |
| 20:33 | <zewt> | (well, at least for a single XHR) |
| 20:37 | <jgraham> | That sounds good to me |
| 20:37 | <jgraham> | Aslo, I seem to be writing perl again |
| 20:37 | <jgraham> | Where id my life go wrong :( |
| 20:37 | <jgraham> | *did |
| 20:38 | <Ms2ger> | jgraham, interested in a job at Mozilla? We hate perl as well :) |
| 20:38 | <zewt> | i hate perl, php, java and ruby, do I get to be the boss |
| 20:40 | <jgraham> | Heh |
| 20:40 | jgraham | is just glad it isn't Pike |
| 20:41 | <jgraham> | (although strictly speaking it isn't clear which is worse) |
| 20:42 | <jgraham> | That's http://en.wikipedia.org/wiki/Pike_%28programming_language%29 in case you aren't a scholar of obscure Swedish programming languages |
| 20:43 | <zewt> | there are lots of really bad, really obscure languages; i save my energy for hating the really bad languages that I actually have to deal with now and again :P |
| 20:44 | <jgraham> | So do I :( |
| 20:46 | <jgraham> | Note to future self: if you ever think "hey I could store this structured data as a blob of text and process it in an adhoc way using regexps", don't. |
| 20:47 | <jgraham> | (for posterity, I point out that I didn't do that this time either) |
| 20:57 | <annevk> | zewt: send email I guess |
| 20:58 | <Ms2ger> | jgraham, HTML? |
| 21:08 | <annevk> | Ms2ger: the tables now omit bytes that map to U+FFFD |
| 21:08 | <annevk> | Ms2ger: might be better |
| 21:09 | <jgraham> | Ms2ger: No, key-value pairs, basically. I wouldn't mind if it was parsed with regexp once into a data structure of some sort. But it isn't; the big blob of text is stored and every time some data is needed, it's out with the regexp |
| 21:10 | <Ms2ger> | Nice |
| 21:10 | <gsnedders> | Ms2ger: html5lib has fragment parsing support |
| 21:11 | <gsnedders> | jgraham: Pike isn't bad. It just has horrible debug tools. |
| 21:11 | <annevk> | I guess I should also link to the tables from the spec |
| 21:11 | <annevk> | oh well, later |
| 21:21 | <jgraham> | gsnedders: And three different values of zero |
| 21:22 | <jgraham> | Also, the last person I heard say "Pike isn't so bad" then used it for two *more* weeks and hated it passionately |
| 21:24 | <gsnedders> | jgraham: Gerald always claimed the language wasn't so bad, just the tools. |
| 21:27 | <jgraham> | gsnedders: See if Kevin agrees :) |
| 21:31 | <gsnedders> | Man, I should come to Lkpg sometime and see people again. |
| 21:47 | <TabAtkins> | Hahaha, "Strunk & White? More like Bunk & Trite, amirite?" |
| 21:48 | <Ms2ger> | As long as you don't start about Strunk/White |
| 21:49 | <TabAtkins> | Nothing wrong with literary slash. |
| 22:04 | <TabAtkins> | matijsb: I've totally borked the css-commits RSS feed. I've got all the necessary data to regenerate it properly, but it'll take some time (and testing) to make sure it's all correct. |
| 22:04 | <TabAtkins> | So it may be a good idea to turn off your @csscommits script until you can be sure you're not going to attempt to send a thousand tweets at once. |
| 22:05 | <jgraham> | TabAtkins: Is that "literary slash" as in "Fan fiction in which Strunk/White hook up"? |
| 22:06 | <TabAtkins> | Yes. |
| 22:07 | <TabAtkins> | What else would it be? |
| 22:07 | <jgraham> | Who knows the depths of depravity to which the human mind might sink |
| 22:08 | <Ms2ger> | s/human/TabAtkins/ |
| 22:08 | <jgraham> | Also, that genre of book in general, and Strunk & White in particular, is known to be, to use the technical term, utter bollocks |
| 22:08 | <jamesr_> | oh? how so? |
| 22:10 | <TabAtkins> | jamesr_: Most of it is, to be blunt, made up bullshit based on their own predilections and their hardons for Latin. |
| 22:10 | <jgraham> | The advice generally assumes a prescriptionist model of grammar which doesn't match that of modern linguists. |
| 22:10 | <jgraham> | And S/W has advice that is both contradicatory or, as TabAtkins didn't put it, wrong |
| 22:11 | <jgraham> | s/or/and/ |
| 22:11 | <jgraham> | http://chronicle.com/article/50-Years-of-Stupid-Grammar/25497 for example |
| 22:12 | <zewt> | jgraham: prescriptionist grammar also doesn't match ... common sense |
| 22:13 | <zewt> | if i see one more stupid sentence twisted around like a pretzel because some clueless elementary teacher brainwashed YOU CAN'T PUT PREPOSITIONS AT THE END OF A SENTENCE into someone's head |
| 22:13 | <TabAtkins> | That's the kind of nonsense up with which I'll not put! |
| 22:14 | <jgraham> | (TabAtkins now sounds like Dr Seuss) |
| 22:14 | <TabAtkins> | But I avoid a final preposition! |
| 22:14 | <TabAtkins> | (Or rather, Imaginary Churchill did.) |
| 22:16 | dglazkov | is now convinced that the Big Bang Theory show was conceived as a result of observing #whatwg discussions. |
| 22:17 | <zewt> | (i havn't seen that show, so I can't tell if that's complimentary, backhanded-complimentary or derogatory) |
| 22:17 | <zewt> | (or perhaps it depends on one's opinion of the show) |
| 22:18 | <dglazkov> | does it have to be any of those? Can it be just a musing? |
| 22:18 | <zewt> | prohibited! |
| 22:18 | <Ms2ger> | Objection, your honour! Alleged prohibition! |
| 22:20 | <jgraham> | zewt: Well it would suggest that we were all rather bright, except for the most prominent female. It would also suggest we had surprisingly active social lives given our supposed characters |
| 22:21 | <zewt> | if we're on a tv show, does that mean we're all unusually good looking, too? |
| 22:21 | <jgraham> | OTOH I assume that dglazkov is really refering to the need for a "SARCASM" sign |
| 22:23 | <jgraham> | (I guess in defense of BBT, I should say that many of the other female characters are at least the intellectual equals of the boys) |
| 22:23 | <TabAtkins> | Yes, virtually every major character besides Penny, male or female, is a roughly-equivalent genius. |
| 22:25 | <TabAtkins> | jgraham: Ah, I should have realized that article would be written by one of the Language Log regulars. |
| 22:26 | jgraham | hasn't actually seen season 4 but never understood how one was supposed to understand Bernadette. |
| 22:26 | <zewt> | can we all be on TV-show-actor salaries, too? |
| 22:27 | <dglazkov> | jgraham: don't spoil it! I am on season 2 at the moment. |
| 22:27 | <annevk> | dglazkov: me too! |
| 22:27 | <zewt> | spoiler: the show doesn't end with the big crunch |
| 22:27 | <TabAtkins> | I think me three, too. |
| 22:27 | <TabAtkins> | zewt: Big Rip, or just heat death? |
| 22:28 | <TabAtkins> | Or *gasp* steady-state? |
| 22:28 | <zewt> | make a Choose Your Own Galaxy End-game Adventure out of it |
| 22:28 | <jgraham> | Isn't the steady state ending what The Simpsons has achieved |
| 22:28 | <jgraham> | You just keep churning out mostly indistigguishable episodes for an indefinite amount of time? |
| 22:29 | <zewt> | don't they just have an episode-generating machine by now? |
| 22:29 | <zewt> | with a big red lever, of course |
| 22:32 | <TabAtkins> | I actually wouldn't put it past BBT to go steady-state. Have Sheldon invent a time-machine, and stumble into one of the previous episodes in a believable way. |
| 22:32 | <TabAtkins> | Perhaps the one with a time machine. |
| 22:33 | <zewt> | invent a time machine and travel to another episode that also has a time machine? that seems a recipe for an unpleasant loop |
| 22:33 | <TabAtkins> | Yes, that's the point. |
| 22:33 | <zewt> | mobius tv |
| 22:34 | <TabAtkins> | It turns a series finale into just another episode of the infinite show. |
| 22:47 | <matijsb> | TabAtkins: I'm sure you mean matjas :) |
| 22:47 | matijsb | matjas: what TabAtkins said :) |
| 22:47 | <matijsb> | (fkin cmd-enter) |
| 22:49 | <TabAtkins> | Dammit, people. Get more different names! |
| 22:52 | <roc> | isn't BBT reasonably hard-science? |
| 23:01 | <TabAtkins> | roc: Reasonably so, considering the audience is the general public. |
| 23:02 | <jgraham> | Right, the science is generally accurate; http://thebigblogtheory.wordpress.com/ |
| 23:02 | <roc> | so time travel is right out |
| 23:07 | <jamesr_> | outside of perhaps some neutrinos, yeah |