| 00:33 | <TabAtkins> | Argh, why is being precise so difficult? >_< |
| 00:34 | <TabAtkins> | s/precise/precise while maintaining clear prose/ |
| 00:43 | <TabAtkins> | Anyone know shepazu's mobile? He sent me a 9-digit telephone number? |
| 00:43 | <TabAtkins> | Ignore that last ?. |
| 00:44 | <MikeSmithX> | TabAtkins: I'll find it for you now |
| 00:45 | <TabAtkins> | Danke. |
| 00:46 | <MikeSmithX> | ->DM |
| 00:51 | <TabAtkins> | Thank, MikeSmithX. He didn't answer, but I left a message. |
| 01:01 | <MikeSmithX> | hai |
| 01:05 | <karlcow> | just realized that http://www.w3.org/TR/XMLHttpRequest/ was still in WD |
| 01:05 | <karlcow> | W3C Working Draft 19 November 2009 |
| 01:45 | <bl4ckcomb> | hi, can someone clarify whether <command ... /> (validated by w3's validator) is valid or if it should be <command ...></command> (parsed correctly in chrome and mozilla) ? |
| 01:46 | <Hixie> | it's neither actually |
| 01:46 | <Hixie> | supposed to be just <command> |
| 01:47 | <Hixie> | like <img> |
| 01:50 | <bl4ckcomb> | Hixie, it seems to validate (w3's validator) as <command>, but then again the browsers don't parse it correctly (they add a closing tag and nest sibling <command> elements) :( |
| 03:22 | <wirepair> | does any browser besides chrome/chromium implement the sandbox attribute for iframes? |
| 03:41 | <othermaciej> | wirepair: it's in WebKit trunk but not yet in a shipping version of Safari |
| 03:42 | <wirepair> | cool thanks |
| 05:13 | <wirepair> | there's nothing like IE8's toStaticHtml defined in html5 correct? |
| 08:39 | <MikeSmith> | roc: can you think of any Mozilla developers who might take an interest in picking up work on implementing support for the progress element? |
| 08:39 | <MikeSmith> | https://bugzilla.mozilla.org/show_bug.cgi?id=514437 |
| 08:40 | <hsivonen> | MikeSmith: have you pinged volkmar about it? |
| 08:41 | <MikeSmith> | hsivonen: nope |
| 08:41 | <MikeSmith> | but I will |
| 08:42 | MikeSmith | wonders what timezone volkmar is in |
| 08:42 | <MikeSmith> | CET I guess |
| 08:49 | <MikeSmith> | othermaciej: we seem to have a product for the alt-techniques doc already |
| 08:49 | <MikeSmith> | http://www.w3.org/html/wg/tracker/products/9 |
| 08:50 | <othermaciej> | MikeSmith: cool! |
| 08:51 | <MikeSmith> | and I just now added one for HTML+RDFa |
| 08:51 | <MikeSmith> | http://www.w3.org/html/wg/tracker/products/10 |
| 08:51 | <othermaciej> | sweet! |
| 08:52 | <MikeSmith> | othermaciej: do you know if Yael Aharon frequents IRC? |
| 08:52 | <othermaciej> | maybe I'll convert over the 4 TrackerRequest bugs |
| 08:52 | <othermaciej> | MikeSmith: I don't know |
| 08:52 | <MikeSmith> | k |
| 08:52 | <othermaciej> | there is a "yael" on #webkit but I dunno if she pays attention |
| 08:54 | <MikeSmith> | ah, OK |
| 09:05 | <hsivonen> | since we don't have a proper URL parsing spec yet: What's the path in this url? href=" ftp://foo/a " |
| 09:06 | <hsivonen> | what about href=" ftp://foo/a%20 " |
| 09:07 | <hsivonen> | Where can I find the last URL parsing spec rev before IETF buried it? |
| 09:08 | hsivonen | is getting annoyed at politics getting in the way of implementation work |
| 09:09 | <hsivonen> | $ hg clone http://bitbucket.org/DanC/urlp urlp |
| 09:10 | <hsivonen> | well, there it is |
| 09:10 | <hsivonen> | Strip leading and trailing space characters from w. |
| 09:11 | <hsivonen> | now if we could agree on what the space characters are... |
| 09:11 | <annevk> | hsivonen, /a /a%20 |
| 09:12 | <hsivonen> | annevk: thanks |
| 09:13 | <hsivonen> | for now, I'm going to pretend that space characters are ' ', '\r', '\n' and '\t', since that's what most of the above-DOM layers of Gecko think |
| 09:13 | hsivonen | is quite unhappy that HTML5 doesn't agree |
| 09:13 | <annevk> | http://www.w3.org/html/wg/href/draft is what you are looking for I suppose but it's not entirely up to date with all latest findings (but then nothing is) |
| 09:14 | <hsivonen> | annevk: thanks. I found the most up-to-date version of that doc from DanC's bitbucket |
| 09:20 | <MikeSmith> | http://twitter.com/Rich_Clark/status/14282319673 |
| 09:21 | <MikeSmith> | http://twitter.com/gtrufitt/statuses/14219697892 |
| 09:21 | <MikeSmith> | "Why is there no input type=year in HTML5 forms?" |
| 09:21 | <MikeSmith> | I don't know the answer to that |
| 09:21 | <MikeSmith> | I do know it wasn't in Web Forms 2.0 |
| 09:21 | <MikeSmith> | or I don't think it was at least |
| 09:21 | MikeSmith | checks |
| 09:22 | <MikeSmith> | but also don't know that the use cases would be |
| 09:24 | <hsivonen> | MikeSmith: http://twitter.com/hsivonen/status/14282994498 |
| 09:24 | <MikeSmith> | thanks |
| 09:25 | <annevk> | be interesting to know the use case |
| 09:26 | <annevk> | localized version of type=year could be way more rich than you can get with type=number |
| 09:28 | <hsivonen> | annevk: what would a localized version do? |
| 09:29 | <annevk> | for certain locales it could offer different calendars as input |
| 09:29 | <annevk> | but then it depends on the use case whether that would actually work, of course |
| 09:29 | <hsivonen> | annevk: I think the start and end of years in different calendars don't match Gregorian years |
| 09:30 | <annevk> | yeah... |
| 09:45 | <othermaciej> | I hate waiting for builds |
| 09:45 | othermaciej | whines to no one in particular |
| 09:45 | <gsnedders> | Get a faster computer? |
| 09:51 | hsivonen | whines about Apple's faster computers being unnecessarily huge in size |
| 09:52 | <hsivonen> | I like the build times on my i7 box that's smaller than a Mac Pro and that Apple wouldn't sell me |
| 09:55 | <hsivonen> | of course, things could always be faster |
| 09:55 | hsivonen | blames C++ for having an archaic file dependency model |
| 10:21 | <roc> | MikeSmith: why should the progress element be a priority? |
| 10:22 | <MikeSmith> | roc: because there's now another actual implementation of it, with some refinements still being made |
| 10:23 | <MikeSmith> | and it might be good to have at least another implementation in the works at the same time |
| 10:24 | <MikeSmith> | and because it's one of the few remaining new elements that hasn't been implemented yet |
| 10:24 | <roc> | I think there are heaps of <input> element types that aren't implemented yet |
| 10:26 | <MikeSmith> | true |
| 10:26 | <MikeSmith> | but I don't think it's necessarily an either-or |
| 10:41 | <volkmar> | oups, i miss him |
| 10:42 | <annevk> | he prolly reads the logs |
| 10:45 | <volkmar> | ok, then he will read I've planned to work on <progress> this week ;) |
| 10:53 | <annevk> | volkmar, mwaha |
| 10:53 | <annevk> | (cool though) |
| 11:56 | <annevk> | oh great - we're gonna discuss whether PHP is HTML again? |
| 12:04 | <Philip`> | Does anyone actually edit PHP files in supposedly-HTML editors, or is it all hypothetical? |
| 12:05 | Philip` | doesn't remember having seen any concrete examples of people successfully doing that |
| 12:06 | <Philip`> | (which makes the discussion seem a bit pointless) |
| 12:08 | <annevk> | I think Dreamweaver has support; prolly others too |
| 12:08 | <annevk> | I've seen plenty of editors that support mixed syntax-highlighting too |
| 12:14 | <hsivonen> | I would have thought it was clear that polyglot was about an intersection--not about a union of features. sigh. |
| 13:15 | <karlcow> | Philip`: yes dreamweaver, textmate, handles the fact to have php. For example, authoring tool parsers must be aware of php(|something else) language for syntax coloring. |
| 13:15 | <karlcow> | but as hsivonen is saying. The way to address the comment is about the intersection of features and I would go a bit further by saying in the realm of http. |
| 13:17 | <karlcow> | The question of glazou is interesting, but in the realm of authoring tool, which as usual is not really addressed in html5. |
| 13:18 | <annevk> | it is addressed karlcow |
| 13:19 | <annevk> | but PHP+HTML is not defined |
| 13:19 | <annevk> | that should not be up to us, but to the PHP guys |
| 13:19 | <karlcow> | annevk: s/PHP/templating and programming languages/ |
| 13:20 | <karlcow> | maybe it should be up to authoring tools developers but that would require a precise list of requirements/issues. |
| 13:20 | <karlcow> | Maybe it's a set of constraints which could live in a separate document |
| 13:21 | karlcow | is thinking and doesn't have a solution |
| 13:22 | <annevk> | it seems something to compete over really |
| 13:22 | <jgraham> | I don't see why PHP is special |
| 13:22 | <jgraham> | RoR or Django are just as popular today |
| 13:22 | <annevk> | it's not |
| 13:22 | <annevk> | not sure that's true |
| 13:23 | <jgraham> | I think Glazou thinks its special |
| 13:25 | karlcow | would avoid to think about what Glazou thinks. Let him express his own thoughts. |
| 13:25 | <jgraham> | Well I mean he did express his thoughts. They were about PHP, not templating languages in general |
| 13:30 | <hsivonen> | jgraham: the only reason why PHP is more special than other conceptually similar templating languages in that PHP chooses to use a syntaxt that deliberately looks like a PI |
| 13:31 | <workmad3> | PHP certainly is special... goes to special school and everything :) |
| 15:38 | <zcorpan_> | why does 'google chrome renderer' sometimes eat my cpu? |
| 15:39 | <nessy> | so does gecko ;) |
| 15:45 | <zcorpan_> | http://www.w3.org/Bugs/Public/show_bug.cgi?id=9766 - should it be called websocket.protocol or websocket.subprotocol? |
| 15:46 | <zcorpan_> | location.protocol returns 'http:' so maybe subprotocol is a better name |
| 15:59 | <zcorpan_> | http://forums.whatwg.org/viewtopic.php?t=4302 - what's *your* html5 story? |
| 16:00 | <gsnedders> | annevk dragged me here. |
| 16:01 | <jgraham> | A long time ago in a galaxy far far away... |
| 16:01 | <jgraham> | No wait that's Star Wars isn't it |
| 16:02 | <jgraham> | I always get those two confused |
| 16:02 | <zcorpan_> | html5 and star wars? |
| 16:02 | <jgraham> | Yeah, sure |
| 16:03 | <jgraham> | We are currently going through the "Empire Strikes Back" phase |
| 16:03 | <gsnedders> | zcorpan_: How long did you work in the same room as jgraham? Didn't you realize this? |
| 16:03 | <jgraham> | eventually the whole project will be saved by a planet full of tiny furry creates |
| 16:03 | <jgraham> | *creatures |
| 16:04 | <Philip`> | jgraham: Have we already gone through the Phantom Menace phase, or is that still to come? |
| 16:05 | <zcorpan_> | gsnedders: i don't know anything about star wars myself to pick up on star wars wibes |
| 16:05 | <TabAtkins> | Argh so many emails |
| 16:05 | TabAtkins | drowns |
| 16:05 | <TabAtkins> | Crap, and I need to write some proposals today too. |
| 16:05 | gsnedders | is kinda hungry, already… gah. |
| 16:05 | <TabAtkins> | Or tomorrow, but I'd rather give myself a day. |
| 16:06 | <TabAtkins> | gsnedders: Come over here, we'll get breakfast. |
| 16:06 | <gsnedders> | That means waiting at least ten hours. |
| 16:06 | <TabAtkins> | ...and? |
| 16:06 | <gsnedders> | I want food now, kthxbai. |
| 16:06 | <TabAtkins> | You can eat on the plane |
| 16:06 | <gsnedders> | Doesn't that somewhat circumvent the point of going to you for food? |
| 16:06 | <TabAtkins> | You get more food when you get here. |
| 16:07 | <TabAtkins> | We'll cook for you. |
| 16:07 | <TabAtkins> | We already got sheppers trapped in the house. |
| 16:07 | <jgraham> | Philip`: Attack of the clones was HTML3.2 |
| 17:11 | <TabAtkins> | http://www.webmproject.org |
| 17:12 | <TabAtkins> | So it looks like we did indeed release vp8 freely. |
| 17:12 | <Dashiva> | I can't find the specification anywhere... |
| 17:12 | <Dashiva> | It just says "based on matroska" |
| 17:13 | <TabAtkins> | ?_? |
| 17:13 | <Dashiva> | Is it a delta spec? |
| 17:13 | <TabAtkins> | I don't understand what you're asking. |
| 17:14 | <TabAtkins> | Oh, got it. |
| 17:14 | <TabAtkins> | Um, I dunno. I suggest checking the Code page. |
| 17:17 | <Dashiva> | I guess this is all there is for now: http://www.webmproject.org/code/specs/container/ |
| 17:24 | <Dashiva> | Arghl |
| 17:25 | <Dashiva> | Why do people insist on mixing in non-HTML document formats in the polyglot discussion? |
| 17:25 | <Lachy> | haha. Håkon just said, re the Norwegian 17th of May celebration video he showed at google I/O: "We do this every year to celebrate the video element" :-D |
| 17:25 | <Dashiva> | Unprocessed PHP code isn't HTML |
| 17:25 | <Lachy> | he's demoing WebM support in Opera |
| 17:25 | <TabAtkins> | ARGH I'M MISSING THE KEYNOTE AND HAKON |
| 17:25 | <Philip`> | Is WebM currently / going to be supported more widely than Theora? |
| 17:26 | <TabAtkins> | Well, it's in FF and Webkit nightlies now. |
| 17:26 | <Philip`> | Is it likely to be in Safari? |
| 17:27 | <Dashiva> | Philip`: Flash is on the supporter list |
| 17:27 | <TabAtkins> | I suspect so. |
| 17:27 | <TabAtkins> | And Opera is going with a beta soon. |
| 17:28 | <TabAtkins> | I wonder if we pulled MS into this? |
| 17:29 | <Dashiva> | From my reading of the container spec, a regular matroska splitter should be able to handle webm, so support could get in via regular codec packs too |
| 17:29 | <Dashiva> | Needs VP8 added, of course :) |
| 17:29 | <Lachy> | Dashiva, existing tools just need to add support for the "webm" doctype. But otherwise, yes, WebM is a strict subset of MKV |
| 17:30 | <Lachy> | oh, and they need the VP8 codec to play videos |
| 17:30 | <Lachy> | support in mkvmerge is coming soon. mkvaldiator and mkclean are already out for working with webm |
| 17:30 | <Philip`> | Dashiva: If the Flash player will support it then that sounds good, since you only need to encode your video once and you can have decent fallback in all browsers |
| 17:31 | <TabAtkins> | Yup, Adobe CTO is up on stage talking about it right now. |
| 17:31 | <Dashiva> | Is the blog really supposed to be private? |
| 17:31 | <TabAtkins> | I suspect that's a mistake. |
| 17:34 | <Rik`> | What about WebM and live streaming ? |
| 17:35 | <Lachy> | Rik`, live streaming could theoretically be done with VP8. But the video element isn't really optimised for live streaming in HTML yet |
| 17:35 | <Lachy> | Skype, for example, is adopting VP8 for video conferencing |
| 17:35 | <Rik`> | great |
| 17:35 | <Lachy> | I don't think they'll be using the webm container though |
| 17:35 | <Dashiva> | Someone started looking at the markup |
| 17:36 | <Dashiva> | <a href="http://www.android.com"><img src="/media/images/logos/android.jpg" title="Android" alt=""></a> |
| 17:36 | <jwalden> | nice alt-attributing there |
| 17:36 | <Lachy> | all this webm stuff is really old news to me though now. I've known for a month. I'm just waiting for a response from Apple and Microsoft |
| 17:37 | <TabAtkins> | We're horrible with accessibility. ;_; |
| 17:37 | <TabAtkins> | Lachy: Hey, let the rest of us be excited that we finally got confirmation. |
| 17:37 | Philip` | wonders what company will be the first to sue over patents in VP8 |
| 17:37 | <Lachy> | Yay, he just announced VP8 in Flash :-) |
| 17:38 | <Lachy> | TabAtkins, don't you work for Google now? Didn't you know? |
| 17:38 | <TabAtkins> | No! They were very secretive. |
| 17:38 | <Lachy> | wow |
| 17:38 | <Dashiva> | http://x264dev.multimedia.cx/?p=377 |
| 17:38 | <Rik`> | Lachy: I bet the answer will be "hardware support?" |
| 17:39 | <gsnedders> | Lachy: You do realize most large tech companies are like that? |
| 17:39 | <TabAtkins> | Nobody cares about leaks from Opera, since no one can understand norwegian anyway. |
| 17:39 | <Lachy> | haha |
| 17:41 | <Lachy> | Rik`, the answer to what? |
| 17:41 | <Lachy> | oh, you mean from Microsoft and Apple? |
| 17:41 | <Rik`> | yep |
| 17:41 | <Lachy> | yeah, my guess is that Apple and Microsoft will come back with 2 responses: 1. Patent trolls. 2. Hardware support not yet available. |
| 17:42 | <Lachy> | But it's coming soon, see the hardware vendors listed on webmproject.org |
| 17:42 | <Dashiva> | The x264 article claims part of vp8 is extremely similar to h264 |
| 17:42 | <Dashiva> | Intra Prediction section |
| 17:43 | <Rik`> | Lachy: I'd like to, but the blog is closed right now |
| 17:43 | <TabAtkins> | We're obviously willing to swallow the patent risk. |
| 17:44 | <jcranmer> | if hardware vendors are implementing it, they're willing to do patent risk |
| 17:44 | <jcranmer> | at which point the target audience is very broad |
| 17:45 | <jcranmer> | it's harder to argue patent risk |
| 17:49 | <Rik`> | what about subtitles and multiple audio tracks in WebM ? |
| 17:50 | <Philip`> | Dashiva: Not just part of it |
| 17:50 | <Philip`> | "VP8 is simply way too similar to H.264: a pithy, if slightly inaccurate, description of VP8 would be “H.264 Baseline Profile with a better entropy coder”. Though I am not a lawyer, I simply cannot believe that they will be able to get away with this, especially in today’s overly litigious day and age. Even VC-1 differed more from H.264 than VP8 does, and even VC-1 didn’t manage to escape the clutches of software patents." |
| 17:50 | <TabAtkins> | Well, subtitles are being handles in <video> now. |
| 17:50 | <erlehmann> | TabAtkins, i must have missed that. link ? |
| 17:52 | <TabAtkins> | erlehmann: http://www.whatwg.org/specs/web-apps/current-work/multipage/video.html#the-track-element |
| 18:23 | <Dashiva> | "But, by many accounts, Firefox is no longer considered to be the light, open alternative it once was." |
| 18:24 | <Dashiva> | When was the last time anyone called firefox light in a non-sarcastic way? :) |
| 18:42 | <miketaylr> | " In its HTML5 support, IE9 will support playback of H.264 video as well as VP8 video when the user has installed a VP8 codec on Windows." |
| 18:42 | <miketaylr> | http://windowsteamblog.com/windows/b/bloggingwindows/archive/2010/05/19/another-follow-up-on-html5-video-in-ie9.aspx |
| 18:43 | <Rik`> | Lachy: In its HTML5 support, IE9 will support playback of H.264 video as well as VP8 video when the user has installed a VP8 codec on Windows. |
| 18:43 | <Rik`> | http://blogs.msdn.com/ie/ |
| 18:43 | <Rik`> | oops |
| 18:43 | <Rik`> | http://windowsteamblog.com/windows/b/bloggingwindows/archive/2010/05/19/another-follow-up-on-html5-video-in-ie9.aspx |
| 18:43 | <miketaylr> | :D |
| 18:51 | <virtuelv> | oh, the x264 guy is ripping into vp8 again |
| 18:51 | <virtuelv> | http://x264dev.multimedia.cx/?p=377 |
| 18:55 | <TabAtkins> | Hm. Given that webm uses a subset of the matroska format, does that mean that any player that understands matroska and has a vp8 codec will play webm? |
| 18:55 | TabAtkins | doesn't know enough about video technical details. |
| 18:55 | <Dashiva> | Except the doctype name, apparently yes |
| 18:56 | <Dashiva> | Not sure how much the doctype actually means in mkv files |
| 18:59 | <Lachy> | TabAtkins, players need to add support for the webm doctype. In EBML, you need to understand the doctype in order to parse the file properly |
| 19:00 | <Lachy> | at least, if your implementation is following EBML, and isn't just assuming that any EBML file is a Matroska file. |
| 19:00 | <Lachy> | mkvinfo, however, already does ignore the doctype, and parses any file like matroska |
| 19:00 | <TabAtkins> | So is it accurate or not for Microsoft to say that as long as someone has a vp8 codec on their system, IE9 will automatically play webm? |
| 19:01 | <Dashiva> | You need support for both the container and the video codec |
| 19:01 | <Dashiva> | (and the audio, does windows 7 come with vorbis?) |
| 19:02 | <daedb> | Vorbis is not included in any version of Windows |
| 19:02 | <Lachy> | yes. The DirectShow filters should add support |
| 19:03 | <Philip`> | I can't figure out from the set of IEBlog posts whether IE9 will support any video formats that are supported by DirectShow |
| 19:03 | daedb | just tested a 720p WebM vid from Youtube i WMP after installing the Directshow filters, and it works great |
| 19:03 | <Philip`> | or whether they're specifically filtering it to only allow H.264/VP8 |
| 19:03 | <TabAtkins> | Philip`: Sounds like the former. |
| 19:04 | <daedb> | Didn't they say earlier that they weren't going to allow any random DS codec in IE9? |
| 19:04 | <Dashiva> | Is there a lenna.webm? :) |
| 19:05 | <Philip`> | Dashiva: Let me know if you find any clear quotes saying that :-) |
| 19:05 | <Philip`> | Um |
| 19:05 | <Philip`> | daedb: ^ |
| 19:05 | <Lachy> | daedb, if you have 5.1 channel audio support, try it with this video http://lachy.id.au/lib/media/elephantsdream/Elephants_Dream-720p-5.1.webm |
| 19:06 | <Lachy> | there's a stereo version of that available there too |
| 19:07 | <Dashiva> | How long is that video? |
| 19:08 | <Lachy> | about 10 minutes |
| 19:08 | <Lachy> | if you want to watch something longer, try http://lachy.id.au/lib/media/sitasingstheblues/Sita_Sings_the_Blues-360p-Stereo.webm |
| 19:08 | <Lachy> | I don't have that in 720p yet |
| 19:09 | <Lachy> | and my experience with 1080p WebM wasn't great. The software decoding is too slow, at least for the encoding parameters I used at the time. |
| 19:09 | <Lachy> | There may be a way to make it more efficient, but I'm still trying to understand all the different parameters |
| 19:11 | <Rik`> | Lachy: the Opera Labs Mac version asks me to download your first video |
| 19:13 | <Dashiva> | Hum, 10 minutes at 720p for 150 MB |
| 19:14 | <Dashiva> | Guess that's not so bad |
| 19:14 | <daedb> | Philip`: "In its HTML5 support, IE9 will support playback of H.264 video only." and "To be clear, users can install other codecs for use in Windows Media Player and Windows Media Center. For web browsers, developers can continue to offer plug-ins (using NPAPI or ActiveX; they are effectively equivalent in this scenario) so that webpages can play video using these codecs on Windows." are about the most clear statements I've seen. Both are |
| 19:14 | <daedb> | from the IE blog. |
| 19:15 | <Philip`> | Dashiva: How can you deduce that it is not bad from the file size? |
| 19:16 | <Philip`> | You could probably get that size with MJPEG with quality=5, but it wouldn't be not so bad |
| 19:17 | <virtuelv> | http://windowsteamblog.com/windows/b/bloggingwindows/archive/2010/05/19/another-follow-up-on-html5-video-in-ie9.aspx |
| 19:17 | <virtuelv> | In its HTML5 support, IE9 will support playback of H.264 video as well as VP8 video when the user has installed a VP8 codec on Windows. |
| 19:19 | <Dashiva> | Philip`: I can deduce that it's not so bad from the fact that it doesn't have a much larger file size than similar h264 files I have |
| 19:22 | <virtuelv> | hm |
| 19:22 | <virtuelv> | that elephant's dream was choppy for me |
| 19:22 | <virtuelv> | then again, I have no hw acceleration |
| 19:22 | <virtuelv> | but what bothered me was that the video seemed to need deblocking |
| 19:23 | <virtuelv> | it appeared to have what I can best describe as low-quuality jpeg artifacts in some frames |
| 19:23 | <virtuelv> | (this doesn't reflect my experience with the videos on youtube |
| 19:51 | <erlehmann> | virtuelv, well, it will probably play theora with xiph components, won't it ? |
| 20:04 | <svl> | Lachy: your Mozilla Firefox link in http://lachy.id.au/log/2010/05/webm points to chromium |
| 20:05 | <TabAtkins> | svl: Surprise! |
| 23:30 | <roc> | I have a question about sandboxed iframes again |
| 23:31 | <roc> | if a sandboxed iframe has scripts disabled, any child non-sandboxed iframes would still have scripts enabled, right? |
| 23:31 | <roc> | as far as I can tell from the spec, that's true |
| 23:31 | <roc> | hmm, but that can't be right |
| 23:32 | <roc> | oh here we go |
| 23:32 | <roc> | "In addition, any browsing contexts nested within an iframe, either directly or indirectly, must have all the flags set on them as were set on the iframe's Document's browsing context when the iframe's Document was created." |