| 00:17 | <L04f3r> | I found this quite amusing. Ars writes that IE6 market share "has grown, from 7.5 percent to 8.33" during november 2011, from here: http://arstechnica.com/business/news/2011/12/internet-explorer-stops-its-slide-as-chrome-nears-firefox.ars |
| 00:17 | <L04f3r> | Could it be that we have just got another Asian country connected to the internet |
| 01:48 | <TabAtkins> | L04f3r: It seems more likely that whatever detection their stats come from is broken, and some Asian browser suddenly started detecting as IE6. |
| 01:50 | <L04f3r> | Well, IE6 countdown (http://www.ie6countdown.com/#chart) also reflects an increase of users worldwide, |
| 02:15 | <erlehmann> | more like IE6 countup |
| 02:15 | <erlehmann> | hhehe |
| 06:18 | <dbaron> | Hixie, did you mean https://www.w3.org/Bugs/Public/show_bug.cgi?id=15048 to be RESOLVED **LATER** ? |
| 06:18 | <Hixie> | oops, no. sorry about that. fixed. or wontfixed, i guess. :-) |
| 06:33 | <dbaron> | (Hooray for not disabling silly resolutions that come in the default install, or something.) |
| 06:39 | <Hixie> | actually i use LATER and REMIND quite a bit |
| 06:39 | <Hixie> | but that's another story :-) |
| 06:44 | <dbaron> | you were probably the only user in bugzilla.mozilla.org too |
| 09:49 | <annevk> | I sort of wonder if we should make "text" UTF-8-only too in XMLHttpRequest |
| 09:49 | <annevk> | send(string) is limited to UTF-8 |
| 09:49 | <annevk> | receiving should be too |
| 11:07 | <Ms2ger> | Someone backup cssom/cssomview at whatwg, please? |
| 19:52 | Philip` | wonders what the UA "Mozilla/5.0 (X11; Linux i686) AppleWebKit/534.34 (KHTML, like Gecko) Qt/4.7.4 Safari/534.34" is |
| 19:52 | <Philip`> | It seems to be very common in some access logs I'm looking at, but surely it's not really Safari on Linux |
| 19:52 | <Ms2ger> | Konqi? |
| 19:53 | <Philip`> | (It's like 30% of all visitors to the site) |
| 19:55 | <espadrine> | or rekonq |
| 19:58 | <Philip`> | I thought they both added their names into the UA string |
| 19:58 | <erlehmann> | it really is just lying |
| 19:59 | <erlehmann> | say, what happens when someone uses a sane UA string? |
| 19:59 | <Philip`> | The web breaks |
| 20:00 | <erlehmann> | like Vendor/Version (Windowing Environment, Kernel) |
| 20:00 | <erlehmann> | what happens then? |
| 20:00 | <erlehmann> | yeah, but where? |
| 20:01 | <erlehmann> | i have experienced more breakage with assuming HTTP HEAD works than with weird UA strings. |
| 20:02 | <Philip`> | You get sent content that's designed for the wrong browser, as far as I'm aware |
| 20:02 | <Philip`> | (You'd only notice when running scripts) |
| 20:02 | <erlehmann> | can you show me specific sites that do that? |
| 20:02 | <Ms2ger> | Google search didn't like "Gecko/2.0" as a UA string last time I tried |
| 20:03 | <erlehmann> | wat |
| 20:11 | <gsnedders> | Ms2ger: For Google Instant, or more generlaly? |
| 20:11 | <Ms2ger> | Instant, probably? I don't remember |
| 20:11 | <Ms2ger> | Maybe we got Opera's version :) |
| 20:26 | <gsnedders> | Ms2ger: We get Instant, now. |
| 20:37 | <erlehmann> | so, Ms2ger, why do even people at google do browser detection if they can do feature detection? |
| 20:38 | <Ms2ger> | Because those people are not as smart as you seem to think they are? :) |
| 20:56 | <zewt> | Ms2ger: it's become pretty clear that google is a big company, and has its ... variety of employees, like any big company :) |
| 20:56 | <Ms2ger> | Yeah |
| 20:58 | <zewt> | (of course, there could be reasons for it, too--despite a lot of, uh, really questionable changes to google search lately, i still assume they're smart enough to put competent developers on *that* product) |
| 20:58 | <zewt> | (they're completely removed literal phrase searches, which is just unbelievable) |
| 20:59 | <Hixie> | there's also the matter that a developer who might be an expert at, say, UI design, might not be an expert at writing browser-agnostic JS |
| 21:00 | <zewt> | well, i'd hope that google, at least, would know the difference between a UI developer and a JS developer, and put the right people to the right tasks (at least for their more important products, like search) |
| 21:01 | <zewt> | the mysterious and utterly out of place "Change background image" on google's main front page makes me unsure, though. heh |
| 21:03 | Philip` | thought double-quotes still worked fine for literal searches |
| 21:03 | <zewt> | double-quotes are still fuzzed |
| 21:03 | <zewt> | you used to be able to say +"phrase" but they removed + |
| 21:03 | <zewt> | (another unbelievable change) |
| 21:03 | <zewt> | (they changed +foo to "foo", which means there's no equivalent to +"foo") |
| 21:04 | <Hixie> | there's a "verbatim" mode now actually |
| 21:04 | <zewt> | i +do +a +lot +of +searches +like +this so "having" "to" "type" "like" "this" really sucks |
| 21:05 | <zewt> | Hixie: is there another way to do a literal +"phrase" search now? |
| 21:05 | Hixie | points to what he just said |
| 21:06 | <zewt> | i have no idea what "verbatim" mode is, heh |
| 21:06 | <Hixie> | google it :-P |
| 21:06 | <zewt> | if i have to google google features to figure out what they are, that points to a problem in and of itself :P |
| 21:07 | <zewt> | eh that affects the whole search |
| 21:08 | <zewt> | anyway, food |
| 21:24 | <erlehmann> | google is becoming a worse filter. |