00:00
<erlehmann>
even IE devs use IE hacks !
00:00
<erlehmann>
what a wonderfu^W awful world :(
00:00
<JonathanNeal>
Well, it may not be a direct translation --- I can't find how they may be triggering it.
00:01
<JonathanNeal>
This is a first draft.
00:01
<JonathanNeal>
A lot of weird detection going on to get these.
00:01
<TabAtkins>
JonathanNeal: What is the script doing to gather this info?
00:02
<JonathanNeal>
One I wrote. See why I don't trust it.
00:02
<TabAtkins>
Care to share?
00:02
<JonathanNeal>
http://msdn.microsoft.com/en-us/library/ms535231(VS.85).aspx --- translated this into a checker.
00:03
<TabAtkins>
How did you extract information out of that? Compare the values with some suitable "default" values?
00:03
<JonathanNeal>
Exactly, if they claim that everything ever should retain these current values, then I don't need to assign them.
00:04
<TabAtkins>
Gotcha.
00:04
<JonathanNeal>
And other browsers follow this convention, for instance webkit or firefox almost never assign display: inline
00:05
<JonathanNeal>
One could assume there is a vendor * {} but when I individually checked all of the default values, they checked out.
00:06
<TabAtkins>
Kk. So you could automate this by just doing some statistical analysis on the properties, and ignoring values that appear too often.
00:06
<erlehmann>
haha
00:06
<JonathanNeal>
By either appearing too often or being universally accepted in multiple browsers as the default.
00:07
<JonathanNeal>
like how all xml elements are generally display: inline.
00:07
<TabAtkins>
Yeah, too often across all elements in a given browser, or across all browsers for a given element.
00:07
<TabAtkins>
We should make a table for this.
00:08
<JonathanNeal>
Sure, I'll brb in about 10 - 15 minutes, cool?
00:10
<TabAtkins>
Yeah.
00:11
TabAtkins
could work on it this weekend.
00:11
TabAtkins
is already tipsy now at the TGIF meeting.
00:56
<TabAtkins>
Hm. What *is* the behavior of a CSS background image with only a defined width, or only a defined height?
00:56
<TabAtkins>
(Such an image could be produced through SVG, frex.)
00:57
TabAtkins
doesn't know enough SVG to actually define such an image and test it.
02:51
<othermaciej>
hola
02:51
<othermaciej>
TabAtkins: I think CSS now defines what the intrinsic size is in "weird" cases like that
03:47
<Traveler1>
hi
03:49
<Traveler1>
anyone around?
03:49
<Traveler1>
hi TabAtkins
03:52
<TabAtkins>
yo
03:52
<TabAtkins>
othermaciej: Any idea where it might do so? I was pretty sure it did too, but I can't find it at the moment.
03:53
<Traveler1>
What are your thoughts on multiple H1 tags on a page?
03:54
<TabAtkins>
Multiple top-level headings, or just using multiple <h1>s and letting them take implicit levels based on sectioning elements?
03:54
<TabAtkins>
(That is, doing <h1>foo</h1><section><h1>bar</h1></section> rather than <h1>foo</h1><h2>bar</h2>.)
03:54
<Traveler1>
Well if you're site calls for it
03:55
<Traveler1>
A lot of people say that one should use only once the h1 tag.
03:55
<Traveler1>
Hm no
03:56
<Traveler1>
For example on the homepage of a blog. You will find a few posts(3,4)
03:56
<TabAtkins>
Most of the time you'll have a single definite "top level" heading, and so a single <h1> is appropriate to mark that up, with <h2> or lower for other stuff.
03:56
<Traveler1>
The titles are h1's.
03:56
<Traveler1>
The subtitles(if any) are h2. and so on so forth.
03:56
<Traveler1>
Would you say that's a bad practice?
03:57
<TabAtkins>
No, I think that's just fine. However, those <h1>s likely aren't actually the top-level heading of the page (probably the blog title is), so make sure that they are wrapped in something that properly scopes them, like <article> or <section>.
03:57
<TabAtkins>
That way they won't be registered as being the same level of heading as the blog title is.
03:58
<Traveler1>
so <article><h1>title</h1></article> ?
03:59
<Traveler1>
The blog title is just the title. I don't get why people wrap it in h1.
03:59
<Traveler1>
It has it's freaggin tag <title>
03:59
<TabAtkins>
Well, like <body><h1>My blog!</h1><article><h1>Post about my cat</h1><p>My cat rocks.</p></article><article><h1>More cat info!</h1><p>Really.</p></article></body>
03:59
<Traveler1>
not like that.
04:00
<Traveler1>
what's that lonely h1 doing after the body tag?
04:00
<TabAtkins>
...? People wrap the title in an <h1> because it's the top-level heading, and because it's difficult to display the <title>.
04:00
<TabAtkins>
That's the blog title.
04:00
<TabAtkins>
(Thus the words inside of it.)
04:02
<Traveler1>
A heading element briefly describes the topic of the section it introduces.
04:02
<Traveler1>
Wouldn't it be logically correct to use it as I described it above?
04:03
<Traveler1>
and just skip the h1 tag for the title
04:04
<TabAtkins>
You could, sure, but then the page as a whole doesn't have a heading.
04:04
<JonathanNeal>
Wow
04:04
<JonathanNeal>
That was a long 15 minutes.
04:04
<TabAtkins>
Because the <h1> is the heading for the article.
04:04
<TabAtkins>
Haha, JonathanNeal.
04:04
<JonathanNeal>
Turns out it was one of my great friends birthdays
04:04
<Traveler1>
The page as a whole doesn't need a heading. It has a title :P
04:04
<Traveler1>
The articles need headings
04:04
<JonathanNeal>
and I couldn't not drop code for my friend.
04:05
<TabAtkins>
Traveler1: Need? No, you're right, it doesn't *need* one. But most people will put one, since they'd like to have a header on their site. ^_^ And that's perfectly normal.
04:05
<JonathanNeal>
TabAtkins, I'm rewriting my tests that generate those ie stylesheets.
04:05
<TabAtkins>
JonathanNeal: Congrats to your friend!
04:06
<Traveler1>
That doesn't bother me at all. I think it bothers me a little when people use the word must.
04:07
<Traveler1>
Wouldn't you be bothered?
04:08
<miketaylr>
Traveler1: i appreciate a h1 in the body since i use chromium which doesn't really show the <title> so well
04:08
<miketaylr>
e.g., http://miketaylr.com/post/806aae69.png
04:09
<Traveler1>
you use chromium as your main os?
04:09
<Traveler1>
(I had to ask)
04:10
<miketaylr>
heh. no. but i use chromium as my main browser.
04:11
<JonathanNeal>
But now I'm rewriting those tests
05:45
<Bolkonskij>
Hm
05:46
<Bolkonskij>
I can't believe this. I have to uninstall SP3 in order to remove IE8.
05:47
<Bolkonskij>
Give me a freakin break.
06:33
<JonathanNeal>
http://sandbox.thewikies.com/html5-browser-stylesheets/ie8.css --- woo woo I think these are the default styles for ie8
06:51
<JonathanNeal>
http://sandbox.thewikies.com/html5-browser-stylesheets/ie7.css --- and ie7
07:05
<othermaciej>
zoinks, Hixie pinged out
07:24
<JonathanNeal>
http://sandbox.thewikies.com/html5-browser-stylesheets/ie6.css --- and ie6
09:02
<JonathanNeal>
heyo
12:23
<annevk>
oh wow
12:23
<annevk>
http://www.amuz.be/noflash.html (via krijnh)
12:24
<annevk>
roughly translated "we also have a site for blind people. click here for the site for blind people" (and then some mumbling for when you do not have Flash)
13:24
<hsivonen>
the rationale for conformance criteria is good to have
13:27
<hsivonen>
I think file size is the weakest of the rationales, because type=text/css is allowed
13:27
<annevk>
via your reply to gruber I found http://twitter.com/gruber/status/11119748935
13:27
<annevk>
funny
13:28
<annevk>
hsivonen, type=text/css is marginal compared to a 80% reduction overall
13:54
<karlcow>
annevk: indeed it is not the right questions, but I'm not sure what was the intent of Sam asking the questions. Both given examples may create accessibility challenge, they are both presentational, the only difference is size.
15:10
<Philip`>
Is it normal to get multiple requests per second, for many minutes, for an .ogg file served by <audio> to a Firefox 3.6 user?
15:46
<JonathanNeal>
Mornin!
15:55
<TabAtkins>
Yo, JonathanNeal.
15:56
<JonathanNeal>
Did you see the 5 css? ie6, ie7, ie8, ie6 (ietester), ie7 (ietester) ?
15:56
<JonathanNeal>
I don't know why, but ietester would produce slightly different results.
15:59
<TabAtkins>
No, I left the room before you posted that, I guess.
16:00
<TabAtkins>
I found that ie emulators do an imperfect job of reproducing ie's quirks.
16:00
<TabAtkins>
I had some real problems when a site that looked fine in some ie emulation was actually still very unusable in the real ie6.
16:02
<JonathanNeal>
They are all @ http://sandbox.thewikies.com/html5-browser-stylesheets/
16:08
<TabAtkins>
Cool.
16:09
TabAtkins
goes to turn this into a huge table.
16:10
<JonathanNeal>
You've mentioned that, how are you planning to display this data in a table?
16:10
<TabAtkins>
Complicatedly.
16:11
<TabAtkins>
It's 3-dimensional, unfortunately, which means some trickery to display it in a <table>.
16:11
<TabAtkins>
I'm going with properties for the rows, with column groups corresponding to each element, and browsers in each column group.
16:15
<Philip`>
If it's 3D, you should use WebGL
16:16
<TabAtkins>
I doubt that would make the table easier to understand.
16:17
<Philip`>
No, but it would look cooler
16:18
<TabAtkins>
But I couldn't program it in ten minutes.
16:21
<JonathanNeal>
TabAtkins, I could always program my test to output the results differently.
16:21
<JonathanNeal>
Give me a structure on pastie or something that you want it to follow.
16:22
<TabAtkins>
Okay. Can you output it for all browsers simultaneously?
16:22
<JonathanNeal>
No, but I can easily concat all 3 or 6 tests.
16:22
<JonathanNeal>
And each test can be written to be a piece of that table.
16:23
<TabAtkins>
Can you gimme a json structure containing nested objects keyed to element name, then property name?
16:24
<TabAtkins>
Ie {"a":{"border-color":"#000",...}...}
16:24
<JonathanNeal>
Sure
16:26
<TabAtkins>
Damn, wrong use of ie. Should have been eg.
16:28
<Bolkonskij>
Do you still support Ie 6?
16:31
<TabAtkins>
I "support" it in the sense that I will make sure most of my site is at least visible in ie6. I don't care beyond that.
16:37
<JonathanNeal>
TabAtkins, http://sandbox.thewikies.com/html5-browser-stylesheets/ie7.json.txt and http://sandbox.thewikies.com/html5-browser-stylesheets/ie8.json.txt ?
16:37
<TabAtkins>
Yes, that is perfect.
16:37
<TabAtkins>
Now I go to eat breakfast, but I'll finish this later today.
16:40
<JonathanNeal>
ie6.json.txt is in there too.
17:24
<Bolkonskij>
http://cnettv.cnet.com/apple-vs-google/9742-1_53-50085458.html
17:38
<lazni>
idea: federated feed syncing: several ppl in different timezones (and online habit) share the workload of subscribing to feeds
17:38
<lazni>
may reach the same sync reliability of an always-on feed reader
17:38
<lazni>
bonus point if implemented as an HTML offline-cached app
18:31
<GPHemsley>
annevk: (Where's Hixie?) "Errors that are intended to save the author time" in Section "1.10.3 Restrictions on the content model and on attribute values" has a typo
18:31
<GPHemsley>
"inlien" should be "inline"
18:33
<Philip`>
GPHemsley: Already in Bugzilla
18:33
<GPHemsley>
ah, OK, good :)
18:34
<GPHemsley>
glad I didn't make it official then :)
19:02
<TabAtkins>
JonathanNeal: http://www.xanthir.com/etc/default-stylesheets.php
19:03
<JonathanNeal>
Interesting
19:03
<JonathanNeal>
It would be neat if you could consolidate ones that repeat
19:04
<JonathanNeal>
so instead of italic, italic, italic, it was italic colspan="3"
19:04
<TabAtkins>
Sure.
19:04
<Bolkonskij>
Heh
19:04
<JonathanNeal>
I like the rollover and stuff too, that's nice.
19:05
<Bolkonskij>
This router is weird. I leave the desk for 2 mins and it disconnects me. It always happens when I'm away.
19:07
Bolkonskij
is sick of the support guys telling him that the problem will be fixed in the next couple of days
19:16
<TabAtkins>
JonathanNeal: Done.
19:16
<JonathanNeal>
Soweet
19:18
<JonathanNeal>
Neat chart
19:18
<JonathanNeal>
How easy is it to update if we improve the json?
19:19
<TabAtkins>
Just hand me new json, I paste it in.
19:24
<TabAtkins>
Adding new browsers is a 1-line change too.
19:24
<JonathanNeal>
cool.
19:26
<lazni>
is there any websocket implementation? (not neccessarily in browsers)
19:26
<TabAtkins>
Doesn't Chrome have some early implementation of it?
19:26
TabAtkins
isn't certain.
19:27
lazni
would like to write apps wholly in web languages, to enforce agpl
19:28
<lazni>
http://blog.chromium.org/2009/12/web-sockets-now-available-in-google.html great
19:28
<TabAtkins>
agpl?
19:28
<TabAtkins>
Oh, wait, nm.
19:29
<lazni>
those languages are inherently distributed with the corresponding source code
19:29
<TabAtkins>
Yeah.
19:29
<TabAtkins>
Though with web sockets, you'll be talking back to a server. That source isn't automatically distributed.
19:30
<TabAtkins>
Ooh, apparently ie8 implements some of the page-break properties?
19:30
<lazni>
can't WS be used to connect to other browsers? oops
19:32
<TabAtkins>
JonathanNeal: ie7 caption padding. Really?
19:38
<lazni>
http://code.google.com/p/mochiweb/issues/detail?id=37 WS in minefield too
19:40
<MikeSmith>
lazni: there's a patch for adding WS support to Gecko, but I don't think the code has landed yet
19:41
<lazni>
you would know better than I do, as the above bug report isn't backed up
19:42
<MikeSmith>
https://bugzilla.mozilla.org/show_bug.cgi?id=472529
19:43
<MikeSmith>
the patch is at https://bug472529.bugzilla.mozilla.org/attachment.cgi?id=429716
19:51
<lazni>
each node sends its host:port to a tracker server, which distributes them to other nodes, and nodes run node.js and WS between themselves
19:52
<lazni>
kinda like bittorrent, which would suggest DHT as the next step
19:52
<lazni>
then the tracker is AGPL, and doesn't log anything
20:16
<Philip`>
lazni: WebSockets can't connect to browsers
20:17
<Philip`>
You'd need some kind of P2P protocol maybe like http://www.whatwg.org/specs/web-apps/current-work/multipage/commands.html#peer-to-peer-connections
20:17
<Philip`>
though you'll probably need to proxy a lot of the traffic through a server just to get around NATs and firewalls
20:20
<daedb>
TabAtkins: That's a pretty cool table :)
20:21
<TabAtkins>
Thank JonathanNeal equally.
20:21
<daedb>
Yes, JonathanNeal too ^^
20:22
<daedb>
I think it would be easier to read if the elements were on the left side instead on top though, so it wouldn't require so much horizontal scrolling.
20:23
<JonathanNeal>
TabAtkins, about 300zzz, you have no idea how many times I reran that trying to figure out what was going wrong.
20:23
<JonathanNeal>
It's honestly what the browser reports.
20:24
<TabAtkins>
JonathanNeal: How crazy.
20:25
<TabAtkins>
daedb: Eh, you either have lots of horizontal or lots of vertical.
20:25
<JonathanNeal>
So if it is a bug, it's with what the browser reports not the script.
20:25
<daedb>
TabAtkins: Horizontal is less annoying imo
20:26
<TabAtkins>
Good!
20:26
<TabAtkins>
(since that's what I'm doing now)
20:27
<daedb>
err... vertical, I mean... typo :p
20:27
<TabAtkins>
^_^
20:27
<TabAtkins>
The table would, in general, be a lot bigger if I swapped the axes, because of the width of various bits of text.
21:16
<jgraham>
Anyone got any ideas what could cause lcov to fail with messages like geninfo: WARNING: gcov did not create any files for /path/to/.gcda/file?
21:16
jgraham
realises there is likely a better channel for this somewhere