| 06:45 | <zcorpan> | does ie support <mark>? |
| 07:23 | <annevk> | Hixie, "<td> Whether the element is an editable" seems wrong |
| 07:31 | <annevk> | anything happened btw? |
| 07:32 | <annevk> | hmm, the new blog styling has a lot of whitespace |
| 07:36 | <zcorpan> | whatwg blog? |
| 07:36 | <annevk> | yeah |
| 07:49 | <zcorpan> | i don't see it being different from a few months ago? |
| 07:52 | <annevk> | well nimbu changed it with help from jgraham so you must be missing something or have something cached |
| 07:56 | <woef> | As far as analogies go, would you think it's fair to say <article> broadly matches back-end content types? |
| 07:58 | <annevk> | depends on what back-end content types are |
| 07:58 | <zcorpan> | i reloaded http://blog.whatwg.org/wp-content/themes/org.whatwg.awesome/style.css but still looks the same. i guess i'm missing something, then |
| 08:05 | <annevk> | compare with http://web.archive.org/web/20100823233819/http://blog.whatwg.org/ |
| 08:08 | <zcorpan> | ah. ok |
| 08:10 | <woef> | annevk: well, typically article, product, blogpost, event ... structured content. |
| 08:10 | <woef> | Usually appears in a list-detail structure. |
| 08:16 | <annevk> | sounds about right |
| 08:17 | <woef> | Cool, a bit easier to understand than the usual "syndication" stuff imo :) |
| 08:29 | <annevk> | oh yes |
| 08:29 | <annevk> | http://trac.webkit.org/changeset/93951 |
| 08:29 | <annevk> | weinig+++ |
| 08:29 | <asmodai> | wow |
| 08:29 | <asmodai> | lovely diginotar fuckup |
| 08:31 | <annevk> | ? |
| 08:31 | <asmodai> | Dutch certificate provider gave a wildcard certificate for *.google.com |
| 08:31 | <asmodai> | to some Iranian requester or something along those lines |
| 08:31 | <asmodai> | annevk: http://tweakers.net/nieuws/76444/iran-gebruikt-nederlands-certificaat-om-gmail-te-onderscheppen.html |
| 08:32 | <asmodai> | http://tweakers.net/nieuws/76445/browsermakers-geven-nieuwe-versies-uit-na-diginotar-blunder.html |
| 08:45 | <jgraham> | annevk: I don't think it has anything like excessive whitespace. Indeed ideally I would like it to look more like e.g. diveintomark with no sidebar |
| 08:48 | <annevk> | jgraham, feel free to modify the templates |
| 08:48 | <annevk> | archives and categories are pretty useless imo |
| 08:48 | <annevk> | so we would just need those sidebar links presented differently |
| 08:50 | <jgraham> | Yeah, it's a bit non-trivial to modify the actual templates without being able to download them |
| 08:51 | <annevk> | I can prolly get you ssh access if I remember all the details |
| 09:03 | <annevk> | zcorpan, did you introduce the prefix match for "xmlns" in setAttribute()? |
| 09:03 | <annevk> | zcorpan, see thread on www-dom |
| 09:06 | <zcorpan> | annevk: don't remember |
| 09:06 | <zcorpan> | annevk: seems bogus |
| 09:07 | <zcorpan> | annevk: so it must have been you :P |
| 09:13 | <annevk> | heh, will take the blame :) |
| 09:14 | <annevk> | even though I have no recollection of specifying these methods |
| 09:14 | <annevk> | maybe I should blame gsnedders, I hear he is away |
| 09:14 | <annevk> | http://www.mnot.net/blog/2011/08/24/distributed_hungarian_notation_doesnt_work didn't we ask mnot for an alternative to Sec-? |
| 09:16 | <annevk> | indeed |
| 09:16 | <annevk> | http://lists.w3.org/Archives/Public/public-webapps/2011JanMar/0623.html |
| 09:16 | <annevk> | lovely complaining on your blog while not providing solutions |
| 09:16 | <jgraham> | Or blame Ms2ger |
| 09:16 | <jgraham> | But do it on Google+ so he can't see |
| 09:16 | <Ms2ger> | jgraham, isn't that your job? |
| 09:17 | <Ms2ger> | Oh, and that prefix match was you |
| 09:18 | <annevk> | me? |
| 09:18 | <Ms2ger> | Yep |
| 09:19 | <annevk> | i still blame gsnedders |
| 09:19 | <annevk> | added a comment to mnot's post |
| 09:24 | <zcorpan> | this is why we shouldn't have multiple editors. makes it harder to place blame. |
| 09:27 | <Ms2ger> | zcorpan, that's what hg is for :) |
| 09:29 | <zcorpan> | what you mean 'the tools will save us'? silly |
| 10:32 | <jgraham> | annevk: Isn't document.contains(node) different to node.inDocument in the case of multiple documents? |
| 10:33 | <annevk> | yes |
| 10:34 | <annevk> | I wonder when you want to know the latter but not the former |
| 10:35 | <jgraham> | Well that seems like an important criterion in determining the right API to add |
| 10:35 | <gsnedders> | annevk: IT WASN'T ME. |
| 10:35 | gsnedders | looks innocent |
| 10:36 | <annevk> | jgraham, yes |
| 10:37 | <Ms2ger> | node.ownerDocument.contains(node), then? |
| 10:38 | <annevk> | time to get some food |
| 10:41 | <zcorpan> | maybe we want node.topMostAncestor instead |
| 10:42 | <annevk> | Ms2ger, btw, the DocumentType.ownerDocument change breaks Acid3 |
| 10:42 | <Ms2ger> | Time to fix Acid3, then |
| 10:42 | <roc> | acid3-- |
| 10:42 | <annevk> | agreed |
| 10:42 | <annevk> | changing Acid3 does not seem very simple however :( |
| 10:43 | <Ms2ger> | roc, acid2? |
| 10:43 | <annevk> | but ignoring it for now probably works and at some point it will have to adapt or die |
| 10:43 | <Ms2ger> | Hixie, please fix acid3, thanks |
| 10:54 | <annevk> | renameNode semantics sound more like mv in shell |
| 10:54 | <annevk> | moveNode |
| 10:54 | <annevk> | well, moveElement |
| 10:55 | <annevk> | actually, nm |
| 11:01 | <asmodai> | annevk: gets better, looks like that root authority has now been hacked by Iranians |
| 11:01 | <asmodai> | annevk: http://www.f-secure.com/weblog/archives/00002228.html |
| 11:22 | <smaug____> | Ms2ger: what is "node document" |
| 11:23 | <smaug____> | strangely named |
| 11:23 | Ms2ger | blames annevk |
| 11:23 | <Ms2ger> | It's just ownerDocument |
| 11:23 | <smaug____> | Ms2ger: and, createDocument doesn't work atm |
| 11:23 | <smaug____> | "If the doctype's node document is not null, throw a WRONG_DOCUMENT_ERR exception and terminate the overall set of steps." |
| 11:24 | <Ms2ger> | Didn't I change that? |
| 11:24 | Ms2ger | checks |
| 11:25 | <Ms2ger> | Er, I didn't |
| 11:27 | <smaug____> | Ms2ger: so what is your plan? just remove steps 1 and 2 |
| 11:47 | <annevk> | node document is named after XMLHttpRequest document |
| 11:52 | <smaug____> | Ms2ger: so, what is the plan? Allow using dtd nodes even if they are already bound to some other document? |
| 11:52 | <Ms2ger> | Auto-adopt, like we do for all nodes |
| 11:53 | <smaug____> | k |
| 11:53 | <zcorpan> | but doctypes have special powers!! |
| 12:02 | <annevk> | and soon they have none |
| 12:03 | <annevk> | it's a shame browsers support document.doctype at all |
| 12:06 | <Ms2ger> | Acid3? |
| 12:06 | <annevk> | I think for Opera it was Acid3 yes |
| 12:07 | <smaug____> | yeah, I'm just trying to load acid3 to test whether these changes break it |
| 12:07 | <smaug____> | but the site seems to be down |
| 12:07 | <annevk> | Acid3 has a check for ownerDocument being null after createDocumentType() |
| 12:08 | <smaug____> | interesting |
| 12:08 | <smaug____> | someone is going to blame me for breaking it in FF |
| 12:08 | <smaug____> | I do remember that acid3 has seemingly random tests about dtd and createDocument |
| 12:08 | <annevk> | I am planning on writing a blog post at some point about the wrongs of Acid3 |
| 12:09 | <smaug____> | we need to change acid3 |
| 12:09 | <annevk> | might salute you for not caring (and IE for not caring about SMIL) |
| 12:09 | <smaug____> | http://acid3.acidtests.org/ is very very slow |
| 12:10 | <jgraham> | smaug____: Hixie's server is having issues |
| 12:10 | <smaug____> | again :( |
| 12:13 | <smaug____> | would be interesting if acid3 was changed so that all the current browsers start to fail in a test |
| 12:14 | <jgraham> | Would be nice if ACID3 was retired as a failed experiment (maybe) |
| 12:15 | <smaug____> | yes, that would be good |
| 12:15 | <hsivonen> | wiki.whatwg.org is apparently on the same server that's having issues :-( |
| 12:15 | <annevk> | Hixie uses one server |
| 12:45 | <gsnedders> | How frickin' hard can it be to return a broken laptop: obviously very. |
| 12:47 | <hsivonen> | Are Apple and Opera zapping the DigiNotar root? |
| 13:05 | <smaug____> | Hixie: could you remove assertEquals(doctype.ownerDocument, null, "doctype's ownerDocument was wrong after creation"); from acid3. Per DOM Core dtd nodes have ownerDocument |
| 13:10 | <Kellen`> | hsivonen: is there any progress towards a validator.nu library which can be used by external projects? |
| 13:25 | <hsivonen> | Kellen`: no real progress. it's part of the long-term plan, but there's other stuff ahead of it in my work queue |
| 13:26 | <hsivonen> | Kellen`: if you need it now, I suggest writing a mock servlet request/response objects for running VerifierServletTransaction in a holder that makes it think it lives in a servlet container |
| 13:26 | <hsivonen> | s/objects/object pair/ |
| 13:27 | <Kellen`> | hsivonen: that's one possibility. i need to validate a few gigs of data so it seemed like it could be a bottleneck to send HTTP requests everywhere |
| 13:32 | <annevk> | Ms2ger, using concept-node-pre-insert is probably wrong for a bunch of cases |
| 13:32 | <Ms2ger> | Tell me about it |
| 13:32 | <annevk> | Ms2ger, my idea was that pre-insert would also do modification listener stuff |
| 13:32 | <Kellen`> | hsivonen: are you open to contributions towards making the validator library or would that cause extra problems for you? |
| 13:33 | <annevk> | I guess we can cross that bridge later... when it is more clear how modifications listeners are going to work |
| 13:33 | <Ms2ger> | Which is fine, because you can't add listeners to a document before it's created, no? |
| 13:34 | <annevk> | hmm |
| 13:34 | <hsivonen> | Kellen`: I'm open to contributions (under the MIT license) but preferably with design discussion beforehand and not out of the blue |
| 13:38 | <hsivonen> | oh well. WebVTT didn't evolve the way I wanted, but at least there's forward motion: https://bugs.webkit.org/show_bug.cgi?id=64132 |
| 13:39 | <Kellen`> | hsivonen: okay thanks. I'll take a look at the servlet code and see how I feel about it. I'll get back to you before/if I do any serious development work on it. |
| 13:47 | <hsivonen> | Kellen`: ok. thanks |
| 14:56 | <annevk> | Ms2ger, how is the Attr migration going? |
| 14:57 | <Ms2ger> | Nothing much happening |
| 15:15 | <annevk> | http://www.w3.org/wiki/TPAC2011 |
| 15:17 | <jgraham> | Wow |
| 15:17 | <jgraham> | That's quite some progress |
| 15:21 | <jgraham> | Maybe should propose something testing related if I get to attend. |
| 15:25 | <jgraham> | (not sure xactly what has the right level of appeal and isn't covered by the testing IG meeting or so) |
| 15:25 | <jgraham> | +e |
| 15:33 | <karlcow> | even far to be a niche problem… it's one of the first questions I get when talking about mediaqueries for background images. "OH cool!!! How can I use it for img too?" |
| 15:36 | <zewt> | different images for different screen resolutions? uh, no... |
| 15:37 | <zewt> | for different screen sizes vs. dpi, perhaps |
| 15:37 | <Ms2ger> | <img lowsrc=foo> |
| 15:39 | <zewt> | (yuck) |
| 15:39 | <karlcow> | lowsrc is not enough |
| 15:40 | <karlcow> | you need to be able to select the screen size. |
| 15:40 | <zewt> | screen size is meaningless without dpi as well |
| 15:41 | <zewt> | (and even then is only meaningful on mobile browsers, not on anything where the window size is variable) |
| 15:41 | <zewt> | (technically the window size is variable on android's browser, but) |
| 15:42 | karlcow | has a tendency to resize his windows on desktop to get the mediaqueries for small screens. Better sites usually. |
| 15:43 | <zewt> | i always use maximized browsers, myself |
| 15:44 | <karlcow> | zewt: never for me. :) |
| 15:46 | <zewt> | heh, this is also one of the rare cases where progressive jpeg could have been useful, if it was possible for browsers to request the number of passes to download |
| 15:47 | <zewt> | so it could download however much is needed for the resolution it's actually displaying at (and then resume the download to get more, if that changes) |
| 15:50 | <annevk> | karlcow, if you are already talking in the context of images it's not surprising the question comes up |
| 15:50 | <karlcow> | annevk: not sure how does it relate to what we are saying. |
| 15:50 | <karlcow> | contextual images is a **need**, not a niche problem, and a growing frustration from designers. |
| 15:50 | <karlcow> | it is already implemented and well used for background-images in CSS |
| 15:50 | <karlcow> | people want it for img element |
| 15:51 | <annevk> | what's wrong with using a high-resolution image? |
| 15:51 | <karlcow> | It has nothing to do with the resolution |
| 15:53 | <karlcow> | for example, contextual images are an image where you would have a "Logo + company name" (let's say a 400 pixels banner) then when you reach a smaller screen, you want to display only the logo without the company name, (like a 100px square logo) |
| 15:53 | <karlcow> | It is just an example. |
| 15:54 | <karlcow> | a thumbnail of an image at a small size is not necessary the full image but a crop of the bigger image. |
| 15:54 | <zewt> | i'd think you'd just have two images in that case, toggled on mutually exclusively with css, not a single image with src magic |
| 15:54 | <karlcow> | like for example a rectangle image and you show a square crop at smaller size |
| 15:54 | <karlcow> | etc etc |
| 15:54 | <karlcow> | zewt: you are not forced to limit yourself to two images |
| 15:55 | <zewt> | yes, you can have three or four images, again with visibility controlled with css :) |
| 15:55 | <karlcow> | because you can precisely target a very large screen, a tablet screen, a giant billboard, a desktop screen, etc. |
| 15:55 | <zewt> | (not ideal, since it won't work well if the stylesheet isn't loaded, but "css is optional" doesn't exactly work in practice very often anyway heh) |
| 15:55 | shetech | thinks this would be great for targeting mobile vs. full screen |
| 15:58 | <zewt> | karlcow: what i'm saying is, why do this with a complex <img> mechanism, instead of implementing it with multiple, distinct <img> nodes, controlling visibility on each (whether with css or otherwise) |
| 15:59 | <annevk> | <img> is already way complex, adding some conditional resource loading on top of it used by a couple of authors is not worth it |
| 16:00 | <jgraham> | I think characterising it as :a couple of authors" is not very fair |
| 16:00 | <karlcow> | yup |
| 16:00 | <shetech> | jgraham+1 |
| 16:00 | <woef> | Is Apple already conforming to the media="handheld" on css files for it's mobile devices? |
| 16:01 | <zewt> | (what use would that be? a "handheld" device might have a display in the same class as a desktop pc) |
| 16:01 | <annevk> | jgraham, maybe not, is <source> a success? |
| 16:01 | <zewt> | (or a laptop, more practically) |
| 16:01 | <woef> | zewt: so it's out of the spec? |
| 16:02 | <zewt> | i don't know anything about it; i'm asking since it sounds useless to me on first impression |
| 16:02 | <annevk> | woef, you should use media queries instead |
| 16:02 | <annevk> | handheld is an old concept, nearly obsolete |
| 16:02 | <zewt> | good :) |
| 16:03 | <woef> | But media queries are based on browser window size right? |
| 16:04 | <woef> | If I reduce the size of my browse I don't necessarily want to end up with some iPad-enhanced css |
| 16:04 | <woef> | *browser |
| 16:04 | <woef> | Probably should say *degraded |
| 16:04 | <annevk> | they select on capabilities |
| 16:04 | <annevk> | viewport size being one of them |
| 16:06 | <karlcow> | zewt see http://dev.opera.com/articles/view/an-introduction-to-meta-viewport-and-viewport/ |
| 16:07 | <woef> | "handheld" just sounded like a good "crap for phones" alternative to me :) |
| 16:07 | <zewt> | (i know about meta viewport, doesn't seem relevant here though) |
| 16:07 | <karlcow> | and http://dev.w3.org/csswg/css-device-adapt/#the-lsquoresolutionrsquo-property |
| 16:08 | <karlcow> | oops I meant for woef |
| 16:09 | <zewt> | heh, meta viewport was pretty nastily inconsistent between iOS and android last i used it (three cheers for vendors making crap up as they go, because it's the 90s, right?) |
| 16:09 | <karlcow> | about mediaqueries and selection on capabilities |
| 16:09 | karlcow | is impatient to see that implemented |
| 16:09 | <karlcow> | @viewport { |
| 16:09 | <karlcow> | width: device-width; |
| 16:09 | <karlcow> | } |
| 16:10 | <karlcow> | instead of having to tweak the HTML code with meta |
| 16:10 | <zewt> | and fun when you need different versions for ios and android |
| 16:11 | <zewt> | ended up having to use document.write to handle that :| |
| 16:11 | <zewt> | (the only time i can ever remember having had to use that) |
| 16:13 | <woef> | Btw, how I came to this question: |
| 16:13 | <woef> | I was asked to remove a bg-image for mobile (because of bandwidth issues) |
| 16:13 | <woef> | So screen-size is really not an interesting capability here. |
| 16:14 | <zewt> | @media 2g? :P |
| 16:16 | <zewt> | that isn't mobile-specific, though--there are painfully slow links that aren't mobile |
| 16:17 | <zewt> | (ever try viewing a site in China during their prime time?) |
| 16:17 | <zewt> | (at least in the US) |
| 16:17 | <woef> | As a broad guess, it's probably not bad though. |
| 16:17 | <zewt> | oh it's much much worse |
| 16:19 | <zewt> | and conversely, many people on mobile have very fast links--it'd be reducing the site unnecessarily for them |
| 16:19 | <jgraham> | annevk: <source> seems to be a success, yes. Although it addresses a quite different problem |
| 16:19 | <zewt> | it's the wrong metric for adjusting for bandwidth capability |
| 16:19 | <woef> | Probably, but it's better than nothing though. |
| 16:20 | <woef> | Which is pretty much the perfect summary of 20 years of webdev :p |
| 16:20 | <annevk> | jgraham, where is it used? |
| 16:20 | <annevk> | jgraham, <source> takes a media query |
| 16:21 | <gsnedders> | zewt: Equally, different resources on the same page could be fetched over different connection types |
| 16:21 | <zewt> | that's much more niche |
| 16:22 | <zewt> | mobile could in theory do some stuff over wifi and some over 3g, but i don't know why they would |
| 16:28 | <gsnedders> | zewt: It's not that niche if you're on, e.g., a bus, or a train, or in a car. |
| 16:28 | <gsnedders> | zewt: Basically any reasonably quick-moving phone can hit that issue. |
| 16:28 | <zewt> | but you're still only using a single connection type at a time |
| 16:30 | <gsnedders> | 3G -> 2G is possible, esp. seeming sites often cause multiple connections to the server to be created |
| 18:03 | <timeless> | zewt: my BlackBerry probably does some stuff over WiFi and some stuff over cellular |
| 18:04 | <timeless> | i think it can choose to send corporate VPN stuff over cellular if it needs to |
| 18:34 | <gsnedders> | hsivonen: No, we're not [revokeing the DigiNotar root yet], just relying on protection against blocked revocation lists. |
| 18:36 | <timeless> | gsnedders: how do you do that? |
| 18:36 | <timeless> | if the ocsp responder is down, what then? |
| 18:36 | <gsnedders> | timeless: I don't know the detail |
| 18:36 | timeless | hasn't checked the crls they issue to see how long they're valid |
| 18:36 | <timeless> | (but generally one can replay an old crl) |
| 18:37 | <hsivonen> | I thought Moxie Marlinspike had shown that CRLs don't work |
| 18:37 | <timeless> | they don't |
| 18:37 | <hsivonen> | or don't work with the defaults of non-Opera browsers? does Opera have different behavior? |
| 18:37 | <timeless> | and yeah |
| 18:37 | <timeless> | oh, i misread |
| 18:38 | <timeless> | gsnedders really did say they were relying on CRLs and not OCSP |
| 18:38 | <gsnedders> | timeless: I did? |
| 18:38 | <timeless> | `blocked revocation lists` implies `revocation lists` implies `crl` |
| 18:38 | gsnedders | notes it's been a long time since he's looked at a lot of this |
| 18:38 | <timeless> | as opposed to OCSP which isn't really a list |
| 18:39 | gsnedders | looks up OCSP, and remembers how that works |
| 18:39 | <gsnedders> | Okay, I was grouping OCSP and CRLs as the same thing. |
| 18:40 | <timeless> | ok, they're idiots |
| 18:40 | <timeless> | the CRL they have right now http://service.diginotar.nl/crl/root/latestCRL.crl next updates 2/3/2012 |
| 18:40 | <timeless> | wtf |
| 18:41 | <timeless> | it also claims it was last updated 2/3/2011 |
| 18:41 | <gsnedders> | timeless: AFAIK if the OCSP responder is down, we treat the the site as untrusted. |
| 18:41 | <gsnedders> | Because we can't guarantee the cert is valid. |
| 18:43 | timeless | kinda wishes this stuff was documented in some easy to review place |
| 18:43 | <timeless> | (one place for all browsers) |
| 18:43 | <timeless> | (security through distributed obscurity) |
| 18:44 | <gsnedders> | timeless: default-secure for OCSP being down seems bad, though |
| 18:45 | <timeless> | oh yeah, i'm not arguing that |
| 18:45 | <timeless> | i just wish i could look at a single web page to get a list of what each browser does for this stuff |
| 18:45 | <timeless> | i shouldn't have to spend 10 minutes reversing how each browser behaves |
| 18:45 | <timeless> | (nor should i have to waste anyone else's time for each browser) |
| 18:45 | <gsnedders> | as since revoked the digital certificate. This is not a Microsoft security vulnerability; however, the certificate potentially affects... |
| 18:45 | <gsnedders> | 21 minutes ago · Share |
| 18:45 | <gsnedders> | Korin Tom Queen Mine's Opera. Dunno how we're affected. |
| 18:45 | <gsnedders> | 19 minutes ago |
| 18:46 | <gsnedders> | Sam Vennall Might wanna double check your security certificates |
| 18:46 | <gsnedders> | 18 minutes ago |
| 18:46 | <gsnedders> | Sam Vennall The one you should be worried about is DigiNotar |
| 18:46 | <gsnedders> | 18 minutes ago |
| 18:46 | <gsnedders> | Korin Tom Queen Nothing seems to be an issue. Geoffrey Sneddon? |
| 18:46 | <gsnedders> | 15 minutes ago |
| 18:46 | <gsnedders> | Axel Theodor Rolandsson Klingberg Umm, Chrome? |
| 18:46 | <timeless> | heh |
| 18:46 | <gsnedders> | 14 minutes ago |
| 18:46 | <gsnedders> | Daniel Callander http://www.reddit.com/r/programming/comments/jya5h/gmailcom_being_mitmd_by_iran_using_this/ |
| 18:46 | <gsnedders> | Google's domain is being man-in-the-middle'd by the Iranian Government. This doesn't affect us, however. Only people connecting from around Iran. |
| 18:46 | <gsnedders> | But if you have a root certifcate for DigiNotar you should probably delete it.Gmail.com being MITM'd by Iran using this certificate : programming |
| 18:46 | <gsnedders> | www.reddit.com |
| 18:46 | <gsnedders> | reddit: the front page of the internet |
| 18:46 | <gsnedders> | 14 minutes ago |
| 18:46 | <gsnedders> | Sam Vennall Fair enough. |
| 18:46 | <gsnedders> | 13 minutes ago |
| 18:46 | <gsnedders> | Sam Vennall You're fine. Google caught it |
| 18:46 | <gsnedders> | 13 minutes ago |
| 18:46 | <gsnedders> | Michael Dyson No problems. I have a certificate pre-screener for FireFox xD. |
| 18:46 | <gsnedders> | 12 minutes ago |
| 18:46 | <gsnedders> | Uh,. shit. |
| 18:46 | <gsnedders> | Totally didn't just paste from the wrong clipboard. |
| 18:46 | <gsnedders> | Sorry. |
| 18:47 | <gsnedders> | http://my.opera.com/securitygroup/blog/2011/08/30/when-certificate-authorities-are-hacked-2 |
| 18:47 | <timeless> | it was amusing |
| 18:47 | <gsnedders> | That's the right clipboard. |
| 18:48 | <timeless> | so.. |
| 18:48 | <timeless> | minor problem |
| 18:48 | <timeless> | revocation url *usually* means CRL |
| 18:48 | <timeless> | and their CRL was last updated in February |
| 18:48 | <timeless> | at best they've updated their OCSP server |
| 18:48 | <gsnedders> | Yeah, it's not the best of posts. |
| 18:48 | <gsnedders> | I'd trust if Sigbjørn claims it's fine that they have updated OCSP. |
| 18:48 | <timeless> | if you guys means OCSP responder |
| 18:49 | <timeless> | .. it'd be good if your post was updated to clarify the text to use "responder" |
| 18:49 | <timeless> | instead of "revocation url" |
| 18:49 | <gsnedders> | timeless: email sigbjorn⊙oc |
| 18:49 | <timeless> | ok |
| 18:49 | timeless | sighs and pulls up blackberry-gmail |
| 18:50 | gsnedders | is about to head off |
| 18:59 | <timeless> | gsnedders: email sent... kinda |
| 18:59 | timeless | waits for gmail.java to finish "Sending message..." |
| 19:00 | <timeless> | and gah, your my site requires me to log in |
| 19:00 | <timeless> | e-way-too-painful |
| 19:01 | <gsnedders> | timeless: Should be possible to post an anon comment on myopera |
| 19:01 | <timeless> | Write a comment You must be logged in to write a comment. If you're not a registered member, please sign up. |
| 19:01 | <timeless> | i could see if bugmenot can help.. |
| 19:01 | <gsnedders> | It used to be possible to post anon comments, at least |
| 19:02 | <zewt> | heh sites that expect you to sign up for an account to leave a comment are sort of, uh, ... no, heh |
| 19:02 | <timeless> | i wouldn't mind so much if i could use google/facebook creds |
| 19:02 | <timeless> | maybe |
| 19:02 | <timeless> | i still wouldn't do it |
| 19:02 | <timeless> | since i don't share those creds w/ work |
| 19:02 | <timeless> | but i wouldn't mind so much! |
| 19:02 | <zewt> | not as bad as sites that try to make you sign up for an account for no reason at all |
| 19:03 | <zewt> | as if people signing up for accounts is an end by itself |
| 19:04 | <gsnedders> | zewt: But it is! |
| 19:04 | <zewt> | even better, when combined with arbitrary blacklists |
| 19:04 | <zewt> | eg. "you can't sign up with a free email" |
| 19:04 | <timeless> | http://tech.slashdot.org/comments.pl?sid=2403472&cid=37247406 |
| 19:06 | <zewt> | win7's file manager is so much worse than xp's, i don't expect it'll recover for many windows generations :| |
| 19:07 | <zewt> | applications seem to reach a peak, at which point engineering knows they don't really need further changing--at which point marketing takes over to force further changes, causing a bottomless downwards spiral |
| 19:09 | <timeless> | darn, i learned about something useful from /. : http://www.officelabs.com/projects/searchcommands/Pages/default.aspx |
| 19:09 | <timeless> | what's the world coming to? |
| 19:10 | <zewt> | heh |
| 19:10 | <zewt> | a ui that needs a search engine to find menu items is ... |
| 19:10 | <timeless> | actually |
| 19:11 | <timeless> | have you used win7's start menu? |
| 19:11 | <zewt> | yeah it's terrible |
| 19:11 | timeless | loves being able to type into the text box that appears at its bottom |
| 19:11 | <timeless> | it's like a command line |
| 19:11 | <timeless> | and you can do something similar in control panel |
| 19:11 | <timeless> | very handy |
| 19:11 | <zewt> | the searching is okay but they threw away a very heavily polished menu ui that we had a decade and a half of experience and muscle memory using |
| 19:12 | timeless | nods |
| 19:12 | <timeless> | i've been using windows since 3.0 |
| 19:12 | <zewt> | shows a serious and complete lack of caring about existing users |
| 19:12 | <timeless> | (i've used older versions, but i wasn't using it) |
| 19:12 | <timeless> | actually |
| 19:12 | <timeless> | they were very careful |
| 19:12 | <timeless> | they studied users and discovered what they could change |
| 19:12 | <timeless> | and what they couldn't |
| 19:12 | <timeless> | they're *incredibly* careful not to change keystrokes |
| 19:12 | <timeless> | because power user muscle memory there is very important |
| 19:12 | <zewt> | ... but they threw away the entire start menu interface, which is fundamental muscle memory |
| 19:13 | <timeless> | e.g. they had yes/no/cancel dialogs when you closed an unsaved document in notepad/paint/etc. |
| 19:13 | <timeless> | the dialog now says save/don't save/cancel |
| 19:13 | <zewt> | they changed the post display-mode-change confirmation from "yes/no" to like "keep/cancel", breaking the &y shortcut |
| 19:13 | <zewt> | pressing backspace in file explorer to go up a level doesn't always work (sometimes it acts like "back") |
| 19:13 | <timeless> | but in the old dialog you could use 'n' to mean "no", and you can still use "n" to mean "don't save" |
| 19:13 | <timeless> | yes, they broke the "yes" case |
| 19:13 | <timeless> | but that's ok, for the yes case, you could have been using <space> |
| 19:14 | <timeless> | (and maybe you were) |
| 19:14 | <zewt> | what you could have been using isn't really relevant |
| 19:14 | <timeless> | worst case there, you hear the beep and press space |
| 19:14 | <zewt> | my muscle memory is what i'm using, not what i might have been :) |
| 19:14 | <zewt> | (that one's not a major case, just a random example) |
| 19:14 | <timeless> | well, they studied large numbers of users to determine which ones people used in high concentrations |
| 19:14 | <timeless> | there are some amusing stories about which ones they could change and which they coudn't |
| 19:14 | <zewt> | i don't care what "lots of people use", i care about what i use, heh |
| 19:15 | <timeless> | you're greedy :) |
| 19:15 | <zewt> | win7's file explroer is also mysteriously missing the window icon (system menu icon), which is annoying since i use that to close windows |
| 19:15 | <zewt> | (it's still there--you can still double-click where the system menu should be to close the window--but it's not visible) |
| 19:15 | <timeless> | yeah |
| 19:15 | <zewt> | strange inconsistency since everything else has it |
| 19:15 | <timeless> | i think that's because they wanted to get rid of the window proxy |
| 19:15 | <timeless> | windows explorer used to have a window proxy there |
| 19:15 | <timeless> | which was "special" |
| 19:16 | <timeless> | and a rarely used feature |
| 19:16 | <zewt> | file explorer has some of the worst breakages, overall |
| 19:16 | <timeless> | anyway, i'll be glad to see w7's explorer replaced by the ribbon ui |
| 19:16 | <zewt> | eg. no keyboard shortcuts at all for copy/save "overwrite file", etc. prompts, short of tediously tabbing around |
| 19:16 | <timeless> | really no shortcuts there? |
| 19:16 | timeless | tries to remember how to get that dialog easily |
| 19:17 | <zewt> | previously it was just &yes or &all |
| 19:18 | <timeless> | there's &Do this for the next 1 conflicts |
| 19:18 | <timeless> | and &Skip |
| 19:18 | <timeless> | note that i find the <for the next N conflicts> incredibly valuable |
| 19:18 | <timeless> | and i was complaining about the lack of that style feature in Nokia's Maemo platform |
| 19:18 | <zewt> | but there's no shortcut for the actual confirmation |
| 19:18 | <timeless> | (backup and restore was terrible there |
| 19:18 | <timeless> | you could have 100-800 conflicts |
| 19:18 | <timeless> | and no indication |
| 19:18 | <timeless> | plus no useful grouping! |
| 19:18 | <timeless> | ) |
| 19:20 | <zewt> | no way to get from the location bar to the file list (pressing tab goes to a bunch of other things before hitting the file list again; it even goes to the column headers first); randomly changing view modes regardless of settings; mouseover highlighting is very confusing (two highlighted rows); keyboard prefix-searching is broken (doesn't reset state properly like it used to); i'll stop here :) |
| 19:20 | <timeless> | for the conflict dialog, i think they made the concious decision that you actually need to read through the dialog and make a real choice |
| 19:20 | <timeless> | which isn't a bad approach |
| 19:21 | <timeless> | yes it hurts power users (who could use copy /y or whatever if they were really power users) |
| 19:21 | <timeless> | but it protects average users (who could really hurt themselves) |
| 19:21 | <zewt> | uh i'm not going to drop to a shell to bypass broken dialogs heh |
| 19:21 | <zewt> | making things deliberately cumbersome is never ever ever an acceptable ui policy |
| 19:21 | timeless | disagrees |
| 19:21 | <timeless> | security behavior is often that way |
| 19:21 | <zewt> | firefox's ssl exemption dialog is one of the worst ui's i've seen in a long time |
| 19:21 | <timeless> | have you seen mozilla's xpinstall dialog? |
| 19:22 | <timeless> | we intentionally force you to wait 3-5s |
| 19:22 | <zewt> | yeah that's horrible and one of the first bits of nonsense i turn off |
| 19:22 | <timeless> | because we have no choice |
| 19:22 | <timeless> | if you're being gamed by being tricked into playing a game |
| 19:22 | <timeless> | you can easily fill those 3s with keystrokes |
| 19:22 | <timeless> | some of which go to us instead of the web page |
| 19:22 | <timeless> | and then you're screwed |
| 19:23 | <timeless> | fwiw, from the address bar, f6 twice is pretty good |
| 19:23 | <timeless> | in explorer |
| 19:23 | <timeless> | instead of using tab |
| 19:24 | <zewt> | the ssl exemption dialog is frustrating since it's training every user in the world not only to click through one-off prompts, but as many prompts as necessary to make it go awayt |
| 19:24 | <zewt> | (okay, every firefox user :) |
| 19:24 | <timeless> | well |
| 19:24 | <timeless> | the hope is that users will instead *maybe* realize there's actually something *wrong* there |
| 19:24 | <zewt> | it's as if someone thinks making the flawed-but-best-we've-got ssl quirks more annoying will improve the system |
| 19:25 | <timeless> | i'm open to other suggestions |
| 19:25 | <zewt> | don't make things willfully annoying :) |
| 19:25 | <timeless> | offhand, i think an alternative is probably sending users to a search page which searches for the hash of the server's cert |
| 19:25 | <AryehGregor> | Which a MITM will also control. |
| 19:25 | <timeless> | and a way for people to add a comment "this bit me, i don't like <write vendor name here>" |
| 19:25 | <zewt> | that won't help users who need help |
| 19:26 | <timeless> | AryehGregor: it'd be pinned SSL |
| 19:26 | <timeless> | zewt: why not? |
| 19:26 | <AryehGregor> | In that case, why force the user to search for it? |
| 19:26 | <AryehGregor> | Just use something like Perspectives. |
| 19:27 | <zewt> | regular users don't know what a hash is, or a certificate, and have no idea what the entire certificate dialog (in any incarnation) means |
| 19:27 | <AryehGregor> | Or, like, fix SSL so we don't have so many sites with broken certs. |
| 19:27 | <timeless> | sorry |
| 19:27 | <timeless> | lemme define "search" |
| 19:27 | <timeless> | to mean "where a server takes your input and provides results based on it" |
| 19:27 | <timeless> | that could very well *be* perspectives |
| 19:27 | <zewt> | aryeh: i really wish we could have "shttp", which is just https without any certificates--just to give people who don't want to pay for a cert the ability to use ssl without causing certificate failures |
| 19:28 | timeless | has yet to see an shttp which wasn't just a simpler way to do MITM |
| 19:28 | <zewt> | simpler? |
| 19:28 | <timeless> | yes? |
| 19:28 | <zewt> | simpler how? heh |
| 19:28 | <timeless> | w/ today's MITM, i have to spend time finding a stupid CA |
| 19:29 | <timeless> | then i have to trick it into giving me a CERT |
| 19:29 | <timeless> | then i have to feed that cert to my server and mitm someone |
| 19:29 | <zewt> | shttp wouldn't allow MITM against https sites--that's the entire reason it'd be a different protocol name |
| 19:29 | <timeless> | wouldn't shttp allow mitm shttp? |
| 19:29 | <zewt> | yes |
| 19:29 | <timeless> | ? |
| 19:30 | <timeless> | and isn't that simpler than mitm https |
| 19:30 | timeless | dismisses a periodic "i don't like your mail server cert" dialog |
| 19:30 | <zewt> | shttp should be compared against http, not https |
| 19:30 | <timeless> | (the dialog pops up from an otherwise invisible service, because the service is stupid) |
| 19:31 | <zewt> | perhaps "shttp" is a bad name, since it should absolutely not be viewed as an alternative to https ("real" security), but as an improvement on http (preventing passive sniffing) |
| 19:31 | <timeless> | (the server seems to be round robin with two distinct certificates, which really annoys the service) |
| 19:31 | <zewt> | i wonder if spdy is going anywhere ... that encrypts everything anyway, so it's equivalently secure |
| 19:32 | <zewt> | havn't heard much about it lately |
| 19:35 | <roc> | we are implementing SPDY |
| 19:36 | <AryehGregor> | And Chrome already has, right? |
| 19:36 | <AryehGregor> | I assume it supports negotiation of some type so you can switch between it and regular HTTP seamlessly. |
| 19:38 | <AryehGregor> | Drat it. I thought of a good reason for why getRangeAt()/addRange() should deal with references (like IE/Gecko) and not copies (like WebKit/Opera), but now I forgot it. |
| 19:38 | <timeless> | heh |
| 19:38 | <timeless> | grr |
| 19:38 | timeless | gets 7 update notifications |
| 19:39 | <timeless> | and i get to enter my password once per notification |
| 19:55 | <zewt> | bluh, ff6 (at least) broke structured clone with File (previously it didn't do anything, now it throws) |
| 19:56 | <Ms2ger> | Blame the spec |
| 19:56 | <zewt> | the spec says it should work |
| 19:56 | <zewt> | (and as I'm only using it with History, it's okay to me if it's silently discarded, but throwing is much worse) |
| 20:00 | <zewt> | (the spec is horribly vague on how structured clone on File is actually supposed to work, but that's a separate problem...) |
| 20:07 | <roc> | what about nightlies? |
| 20:09 | <smaug____> | Hixie: ping |
| 20:16 | <timeless> | grr |
| 20:16 | <timeless> | AryehGregor: so... |
| 20:16 | <timeless> | MikeSmith: or maybe you |
| 20:16 | <timeless> | i want a way to sign up before a community group is approved |
| 20:16 | <timeless> | i.e. i don't want to support a group |
| 20:16 | <timeless> | but if the group is created, i do want its spam |
| 20:16 | <timeless> | and i don't want to be forced to sign up after it is created |
| 20:17 | <timeless> | apparently someone is trying to create a Crypto CG |
| 20:18 | <zewt> | because discussing things on a mailing list we're all already on is far too convenient and open |
| 20:18 | <timeless> | well |
| 20:18 | <timeless> | ignoring that |
| 20:18 | <timeless> | because i don't want to *miss* discussions that someone annoyingly moves to a list i'm *not yet* already on! |
| 20:18 | <timeless> | and i clearly can't prevent that behavior |
| 20:19 | <zewt> | "gotta get away from all these annoying people telling me what i'm doing wrong" |
| 20:19 | <timeless> | but i could at least preempt its damage to me :) |
| 20:19 | <zewt> | was that the one that started out with that bizarre "crypto + address book" nonsense? heh |
| 20:19 | <timeless> | zewt: i didn't look at the guy carefully to figure out if he was one of those |
| 20:19 | <timeless> | did you? |
| 20:19 | <zewt> | i don't remember, it's been a while since that thread |
| 20:20 | <timeless> | from my perspective, reviewing the person takes too much time for me now |
| 20:20 | <timeless> | but asking about a way to avoid missing important mail that is hidden behind some nascent CG |
| 20:20 | <timeless> | seems generically valuable |
| 20:20 | <timeless> | actually, as a gmail user, i'd kinda like a way to tell W3 that i'd like to subscribe to *@cg.w3 |
| 20:20 | <timeless> | give me all your spam, i can take it! |
| 20:20 | <zewt> | if it's the "crypto + address book" one i have little hope of anything useful coming out of it, heh |
| 20:23 | timeless | chuckles |
| 20:23 | <timeless> | <anne> The mobile devices are the ones with the high-resolution displays. |
| 20:23 | <timeless> | <jreschke> Speak for your own device :-) |
| 20:24 | <zewt> | anything modern certainly is higher resolution than any desktop lcd, heh |
| 20:25 | <timeless> | i have 2880x900 |
| 20:25 | <zewt> | on what size display |
| 20:25 | <timeless> | roughly two armspans? (from wrist to elbow x2) |
| 20:25 | <zewt> | err what? heh |
| 20:26 | timeless | looks for a ruler |
| 20:26 | <timeless> | ooh, i have one at my desk! |
| 20:26 | <timeless> | in its original plastic shrink wrap no less! |
| 20:26 | <zewt> | my monitor is 1920x1200, 24", resolution around 80 dpi |
| 20:26 | <zewt> | my phone is something like 200 dpi? |
| 20:27 | <zewt> | much higher resolution |
| 20:27 | <timeless> | well, each screen is 1440x900 and seems to be 17 or 18: |
| 20:27 | <timeless> | s/:/" |
| 20:27 | <timeless> | i think that people have multiple definitions of "resolution" though |
| 20:27 | <timeless> | some are talking about pixel dimensions |
| 20:28 | <timeless> | and others are talking about ppi |
| 20:28 | <zewt> | well anne was obviously talking about dpi |
| 20:28 | <timeless> | a coworker has pointed out that there's another concept to consider |
| 20:28 | <timeless> | which is roughly css's arc concept |
| 20:29 | timeless | doesn't know if there's a good way to describe it in short hand |
| 20:29 | <zewt> | there are many factors that make it tricky: screen size, dpi, and average viewing distance all come into play |
| 20:29 | <timeless> | pixels-per-arc-degree? |
| 20:30 | <zewt> | also the fact that you can zoom the viewport in mobile browsers |
| 20:30 | <zewt> | (can on desktops too with less versitility, though people seem unfortunately content to let anyone using a higher full-page zoom get blurry images) |
| 20:30 | <Philip`> | Don't forget that it depends on the velocity of the observer too |
| 20:31 | <zewt> | what's the resolution of an iphone falling over the event horizon of a black hole |
| 20:31 | <timeless> | Philip`: are you talking about billboards? |
| 20:31 | <timeless> | (times square/tokyo) |
| 20:31 | <Philip`> | timeless: Just any situation in which relativity matters |
| 20:35 | Philip` | thinks authors think "I want to target all things that would be commonly considered to be mobile devices" and it seems silly to force them to say "target all devices with a display resolution >150dpi" (or whatever) as an inaccurate proxy for what they really want |
| 20:35 | <zewt> | i think right now we don't have a solid vocabulary of what's needed, since things have changed so rapidly |
| 20:37 | <zewt> | i don't think the first-gen iPhone was >150dpi |
| 20:37 | <zewt> | (fwiw) |
| 20:41 | <zewt> | ipad is something like 130 |
| 20:49 | <timeless> | Philip`: soudns right |
| 20:49 | <timeless> | s/dn/nd/ |
| 20:49 | timeless | sighs |
| 20:50 | timeless | is relearning to use a keyboard |
| 20:50 | <timeless> | (kinesis arrived yesterday and today is the first day using it) |
| 21:22 | <AryehGregor> | MikeSmith, could you make me the default assignee for DOM Range bugs? |
| 21:24 | Ms2ger | is all for that |
| 21:27 | timeless | suggests not using default assignees this way |
| 21:27 | <timeless> | then you don't have to make such requests regularly :) |
| 21:29 | <AryehGregor> | How do you suggest using them? |
| 22:01 | <timeless> | AryehGregor: have watchable qa contacts per component |
| 22:01 | <timeless> | and default assignees of roughly unassigned⊙wo |
| 22:01 | <AryehGregor> | timeless, I still want to be the default assignee. |
| 22:01 | <AryehGregor> | Not just watch it. |
| 22:01 | <timeless> | whe someone starts working on a bug, they take ownership of the bug |
| 22:01 | <timeless> | why? |
| 22:01 | <timeless> | when you start working on an area, you start watching the qa contact |
| 22:02 | <timeless> | when you stop, you stop watching it |
| 22:02 | <AryehGregor> | I'm the only one working on all these bugs. |
| 22:02 | <timeless> | today |
| 22:02 | <AryehGregor> | Granted. |
| 22:02 | <timeless> | but what happens when that changes? |
| 22:02 | <AryehGregor> | We change all the bugs, obviously. :) |
| 22:02 | <timeless> | you're an average short cited grasshopper |
| 22:02 | AryehGregor | blames Bugzilla for being broken |
| 22:02 | <timeless> | i'm speaking as a long lived ant |
| 22:02 | <Ms2ger> | cited? |
| 22:02 | <timeless> | listen to my words of experience |
| 22:02 | <timeless> | sited :( |
| 22:03 | <timeless> | ? |
| 22:03 | <timeless> | sighted! |
| 22:03 | timeless | sighs |
| 22:03 | timeless | sighed |
| 22:03 | Philip` | prefers "psyted" |
| 22:03 | <timeless> | <cite>AryehGregor</cite>, a short sighted grasshopper |
| 22:04 | <Ms2ger> | Are you calling AryehGregor a piece of work? |
| 22:04 | <Philip`> | (which I suppose could also be a telepathic version of SuperTed) |
| 22:04 | <timeless> | http://www.youtube.com/user/psyted seens potentially NSFW |
| 22:04 | <timeless> | Ms2ger: hey, at least i'm not calling him NSFW :) |
| 22:05 | <timeless> | Ms2ger: can i claim he's self published as a collection of all of his quotations? |
| 22:06 | <Ms2ger> | You could always try |
| 22:06 | timeless | tries |
| 22:16 | <AryehGregor> | Did it work? |
| 22:30 | <timeless> | i'm satisfied with it :) |
| 22:43 | <karlcow> | AryehGregor: before I say more stupid things on the list, let me check here. ;) could the renameElement thing be used to feed the browser with "<foo><bar/></foo>" and then transform it into the DOM as "<p><img/></p>" |
| 23:03 | <TabAtkins> | karlcow: Yes, but it would be a really dumb and fragile thing to do. |
| 23:06 | <TabAtkins> | karlcow: You'd have to iterate through the entire document, transforming every individual element. If JS failed, you'd just have a giant bag of unknown elements that styling wouldn't work on. Even when JS worked, you'd get significant and unavoidable flashes of unstyled content (multiple, because each swap would almost certainly trigger relayout). |
| 23:35 | <karlcow> | TabAtkins: thanks a lot |
| 23:36 | <karlcow> | for the dumbness ;) I'm always surprised by what people try to do online ;) |
| 23:36 | <llrcombs> | does the <video> element have any way to specify or work with 3D? |
| 23:36 | <llrcombs> | afaik it doesn't |
| 23:37 | <TabAtkins> | llrcombs: Not explicitly. If you're doing something like anaglyphic 3d, that's easy to bake into the file. |
| 23:38 | <llrcombs> | does anyone think it should be able to hint to the browser that "this video should be displayed in 3D by combining the side-by-side; use the right-side image if no 3D is available?" |
| 23:38 | <llrcombs> | (e.g. for graphics cards + displays with native 3D, and stuff like the 3DS) |
| 23:38 | <llrcombs> | or a mechanism for providing two separate video files, one for each eye? |
| 23:39 | <llrcombs> | also, can WebGL display in 3D on graphics cards that are capible of it? |
| 23:41 | <llrcombs> | OHSHI- |
| 23:42 | <llrcombs> | which server was that? |
| 23:52 | <roc> | llrcombs: Firefox 4 and later can display WebM videos in 3D |
| 23:52 | <roc> | with Nvidia's 3D hardware at least |
| 23:52 | <llrcombs> | and we're back |
| 23:52 | <llrcombs> | roc: does WebM have an internal hinting system for what type of 3D it is? |
| 23:52 | <roc> | WebM has a standard way to encode stereo, it just packs left and right frames into a single frame and adds a tiny bit of metadata to tell you it's done that |
| 23:52 | <roc> | yes |
| 23:52 | <llrcombs> | yeah, not all formats have that |
| 23:53 | <roc> | right, so it's up to the container format to define that, then browsers can just do it |
| 23:53 | <roc> | no HTML spec changes are required |
| 23:58 | <llrcombs> | well, if the user tells the browser that they own a pair of anglyagraph glasses, and a 3D video online is side-by-side (but encoded in H.264), why not allow the site to hint to the browser that it's side-by-side so the browser can display it anglyagraphic instead? I could see this being doable using <canvas>, but definitely not for hardware 3D like parallax or shutter glasses. |
| 23:59 | <llrcombs> | Preexisting H.264 or other-format 3D videos could be properly displayed on devices that support that codec |
| 23:59 | <llrcombs> | I also like the concept of the browser removing 3D effects if the user says that they don't have any 3D apparatus |