| 05:27 | <Hixie> | can anyone think of a way to have a 2em gap between inline blocks on a line but _not_ at the start or end of lines if they wrap to multiple lines? |
| 05:28 | <Hixie> | can anyone think of a way to have a 2em gap between inline blocks on a line but _not_ at the start or end of lines if they wrap to multiple lines? |
| 05:28 | <Hixie> | the best i've come up with so far is to have 2em right padding and -2em right margin on the container |
| 05:28 | <Hixie> | the best i've come up with so far is to have 2em right padding and -2em right margin on the container |
| 05:28 | <Hixie> | which isn't really very neat |
| 05:29 | <Hixie> | which isn't really very neat |
| 05:42 | <Hixie> | (since it makes the container overflow) |
| 05:43 | <Hixie> | (since it makes the container overflow) |
| 10:54 | <dremy> | hi |
| 10:55 | <dremy> | hi |
| 11:43 | <david_carlisle> | Hixie: I thought you could set word-spacing:2em; on the parent and word-spacing:normal in the inline blocks, but it works in FF but Chrome doesn't seem to think the inline blocks are words... |
| 11:44 | <david_carlisle> | Hixie: I thought you could set word-spacing:2em; on the parent and word-spacing:normal in the inline blocks, but it works in FF but Chrome doesn't seem to think the inline blocks are words... |
| 11:47 | <david_carlisle> | Opera and IE agree with firefox and space the inline blocks |
| 11:48 | <david_carlisle> | Opera and IE agree with firefox and space the inline blocks |
| 14:19 | <zewt> | yuck, is firefox using different rescaling modes for images and canvas now or something |
| 14:19 | <zewt> | yuck, is firefox using different rescaling modes for images and canvas now or something |
| 14:21 | <zewt> | or... for images and images drawn and rescaled into canvas, or something like that |
| 14:21 | <zewt> | or... for images and images drawn and rescaled into canvas, or something like that |
| 15:01 | <annevk> | would be kind of interesting if we could drop floats |
| 15:01 | annevk | likes dropping features |
| 15:01 | <annevk> | would be kind of interesting if we could drop floats |
| 15:01 | annevk | likes dropping features |
| 15:02 | <zewt> | i wonder if anything supports them, given that they don't really exist in JS as far as I know |
| 15:03 | <zewt> | i wonder if anything supports them, given that they don't really exist in JS as far as I know |
| 15:03 | <zewt> | i mean, you have casting rules to make 1.0 == 1.0f in C, but I don't see how you can make that work in JS |
| 15:03 | <zewt> | i mean, you have casting rules to make 1.0 == 1.0f in C, but I don't see how you can make that work in JS |
| 16:15 | <annevk> | :( |
| 16:15 | <annevk> | mapping tables for euc-kr / big5 are all messy |
| 16:15 | <annevk> | :( |
| 16:15 | <annevk> | mapping tables for euc-kr / big5 are all messy |
| 17:33 | <hino> | �� |
| 17:33 | <hino> | ������ ���� |
| 17:34 | <hino> | ¿Í |
| 17:34 | <hino> | »ç¶÷ÀÌ ¸¹³× |
| 17:35 | <zewt> | NO CARRIER |
| 17:35 | <zewt> | NO CARRIER |
| 17:36 | <annevk> | the thing that is worst is when you generate all the valid lead and trail bytes, then decode the bunch |
| 17:36 | <annevk> | and browsers offer different numbers of code points |
| 17:36 | <annevk> | Opera and Chrome: 17724 |
| 17:36 | <annevk> | the thing that is worst is when you generate all the valid lead and trail bytes, then decode the bunch |
| 17:36 | <annevk> | and browsers offer different numbers of code points |
| 17:36 | <annevk> | Opera and Chrome: 17724 |
| 17:36 | <hino> | ok |
| 17:37 | <hino> | ok |
| 17:38 | <hino> | Is the original so quiet here? |
| 17:38 | <annevk> | Gecko: 17758 |
| 17:39 | <hino> | Is the original so quiet here? |
| 17:39 | <annevk> | Gecko: 17758 |
| 17:39 | <annevk> | (for euc-kr) |
| 18:51 | <Ms2ger> | othermaciej, lovely: http://webkitmemes.tumblr.com/post/19508068848/maciej-on-git |
| 18:52 | <Ms2ger> | othermaciej, lovely: http://webkitmemes.tumblr.com/post/19508068848/maciej-on-git |
| 20:21 | <othermaciej> | hehe |
| 20:21 | <othermaciej> | hehe |
| 22:10 | <annevk> | so at least Opera and Chrome are interoperable as far as euc-kr goes |
| 22:10 | <annevk> | except... |
| 22:10 | <annevk> | Chrome uses PUA for undefined areas and Opera uses FFFD |
| 22:10 | <annevk> | so at least Opera and Chrome are interoperable as far as euc-kr goes |
| 22:10 | <annevk> | except... |
| 22:10 | <annevk> | Chrome uses PUA for undefined areas and Opera uses FFFD |
| 22:15 | <annevk> | oh, turns out Chrome does that for only some areas, not all |
| 22:19 | <annevk> | so weird |
| 22:20 | <annevk> | so weird |
| 22:20 | <annevk> | Gecko gets 34 more code points out of the same byte stream |
| 22:20 | <annevk> | but it seems unrelated to the undefined stuff |
| 22:20 | <annevk> | Gecko gets 34 more code points out of the same byte stream |
| 22:20 | <annevk> | but it seems unrelated to the undefined stuff |
| 22:44 | <annevk> | no surrogates |
| 22:44 | <annevk> | no surrogates |
| 23:22 | <annevk> | yay found the problem |
| 23:22 | <annevk> | yay found the problem |
| 23:22 | <annevk> | for lead byte 0xC6 Gecko does not eat some trailing bytes if the resulting code point is undefined, even though the bytes are in the valid range |
| 23:23 | <annevk> | for lead byte 0xC6 Gecko does not eat some trailing bytes if the resulting code point is undefined, even though the bytes are in the valid range |
| 23:23 | <annevk> | with that change, Firefox and Opera are identical |
| 23:23 | <annevk> | booyah |
| 23:24 | <annevk> | with that change, Firefox and Opera are identical |
| 23:24 | <annevk> | booyah |
| 23:29 | <annevk> | now I need to spec it... |
| 23:30 | <annevk> | now I need to spec it... |