Options:
- # Session Start: Wed May 11 00:00:00 2011
- # Session Ident: #css
- # [01:10] * Joins: homata (homata@113.34.70.146)
- # [01:10] * Joins: sylvaing (sylvaing@131.107.0.101)
- # [01:14] * Joins: homata_ (homata@58.158.182.50)
- # [01:15] * Quits: homata (homata@113.34.70.146) (Ping timeout)
- # [01:38] <fantasai> TabAtkins: :link vs. :visited can't be captured with a[href]
- # [01:42] <TabAtkins> a[href]:not(:visited) ^_^
- # [01:46] * Quits: sylvaing (sylvaing@131.107.0.101) (Connection reset by peer)
- # [01:50] * Quits: plinss (plinss@192.6.114.30) (Quit: plinss)
- # [02:17] * Joins: jdaggett (jdaggett@202.221.217.73)
- # [02:59] * Joins: homata__ (homata_@58.158.182.50)
- # [03:12] * Quits: homata__ (homata_@58.158.182.50) (Client exited)
- # [03:18] * Joins: plinss (plinss@68.107.116.23)
- # [03:30] * Joins: sylvaing (sylvaing@131.107.0.101)
- # [03:31] * Joins: sgalineau (sylvaing@184.214.80.237)
- # [03:31] * Quits: homata_ (homata@58.158.182.50) (Ping timeout)
- # [03:31] * Quits: sylvaing (sylvaing@131.107.0.101) (Connection reset by peer)
- # [03:39] * Joins: homata_ (homata_@58.158.182.50)
- # [03:46] * Quits: shepazu (schepers@128.30.52.169) (Quit: Core Breach)
- # [03:59] * Quits: sgalineau (sylvaing@184.214.80.237) (Ping timeout)
- # [04:03] * Joins: sylvaing (sylvaing@98.232.9.174)
- # [04:06] * Quits: sylvaing (sylvaing@98.232.9.174) (Ping timeout)
- # [05:31] * Quits: karl (karlcow@128.30.54.58) (Client exited)
- # [05:32] * Joins: karl (karlcow@128.30.54.58)
- # [06:25] * Joins: shan (qw3birc@128.30.52.28)
- # [06:26] * Quits: shan (qw3birc@128.30.52.28) (Quit: Page closed)
- # [06:32] * Joins: shepazu (schepers@128.30.52.169)
- # [06:55] * Joins: nimbupani (Adium@24.18.47.160)
- # [06:56] * Parts: nimbupani (Adium@24.18.47.160)
- # [07:25] * Joins: homata (homata@58.158.182.50)
- # [08:27] * Joins: nimbupani (Adium@24.18.47.160)
- # [08:27] * Quits: nimbupani (Adium@24.18.47.160) (Quit: Leaving.)
- # [09:16] * Quits: jdaggett (jdaggett@202.221.217.73) (Quit: jdaggett)
- # [10:59] * Quits: lhnz (lhnz@188.223.83.48) (Connection reset by peer)
- # [11:00] * Joins: lhnz (lhnz@188.223.83.48)
- # [11:17] * Quits: plinss (plinss@68.107.116.23) (Ping timeout)
- # [11:34] * Joins: plinss (plinss@68.107.116.23)
- # [12:34] * Quits: lhnz (lhnz@188.223.83.48) (Connection reset by peer)
- # [12:34] * Joins: lhnz (lhnz@188.223.83.48)
- # [12:35] * Quits: homata_ (homata_@58.158.182.50) (Client exited)
- # [14:04] * Quits: homata (homata@58.158.182.50) (Quit: Leaving...)
- # [14:25] * Joins: jdaggett (jdaggett@118.243.227.145)
- # [14:58] * Quits: lhnz (lhnz@188.223.83.48) (Connection reset by peer)
- # [14:59] * Joins: lhnz (lhnz@188.223.83.48)
- # [15:42] * Joins: nimbupani (Adium@24.18.47.160)
- # [15:43] * Parts: nimbupani (Adium@24.18.47.160)
- # [16:31] * Joins: nimbupani (Adium@24.18.47.160)
- # [16:31] * Quits: nimbupani (Adium@24.18.47.160) (Quit: Leaving.)
- # [16:41] * Joins: nimbupani (Adium@71.32.89.167)
- # [16:42] * Parts: nimbupani (Adium@71.32.89.167)
- # [16:47] * Quits: jdaggett (jdaggett@118.243.227.145) (Quit: jdaggett)
- # [17:13] * Joins: Martijnc (Martijnc@84.192.44.100)
- # [17:14] * Joins: Martijnc_ (Martijnc@84.192.44.100)
- # [17:14] * Quits: Martijnc (Martijnc@84.192.44.100) (Connection reset by peer)
- # [17:14] * Martijnc_ is now known as Martijnc
- # [17:14] * Joins: murakami (murakami@118.154.209.3)
- # [17:27] * Joins: sylvaing (sylvaing@98.232.9.174)
- # [17:27] * Quits: Martijnc (Martijnc@84.192.44.100) (Ping timeout)
- # [17:27] * Joins: kojiishi (kojiishi@222.158.227.129)
- # [17:38] * Joins: Martijnc (Martijnc@84.192.44.100)
- # [17:49] * Joins: myakura (myakura@61.203.115.160)
- # [17:52] * Quits: murakami (murakami@118.154.209.3) (Quit: Leaving...)
- # [17:55] * Joins: TabAtkins_ (tabatkins@216.239.45.4)
- # [17:55] * Joins: bradk (bradk@99.7.175.117)
- # [17:58] * Joins: Zakim (rrs-bridgg@128.30.52.169)
- # [17:58] * Joins: RRSAgent (rrs-loggee@128.30.52.169)
- # [17:58] <RRSAgent> logging to http://www.w3.org/2011/05/11-css-irc
- # [17:59] <plinss> zakim, this will be style
- # [17:59] <Zakim> ok, plinss; I see Style_CSS FP()12:00PM scheduled to start in 5 minutes
- # [17:59] <Zakim> Style_CSS FP()12:00PM has now started
- # [17:59] <Zakim> +plinss
- # [18:01] <Zakim> + +1.650.214.aaaa
- # [18:01] <TabAtkins_> Zakim, aaaa is TabAtkins
- # [18:01] <Zakim> +TabAtkins; got it
- # [18:02] * Joins: danielweck (dweck2@86.171.48.72)
- # [18:02] * Joins: oyvind (oyvinds@213.236.208.22)
- # [18:02] <Zakim> +??P32
- # [18:03] <Zakim> +[Microsoft]
- # [18:03] <arronei> zakim, microsoft has me
- # [18:03] <Zakim> +arronei; got it
- # [18:03] <danielweck> Zakim, ??P32is me
- # [18:03] <Zakim> I don't understand '??P32is me', danielweck
- # [18:03] <danielweck> zakim, ??P32 is me
- # [18:03] <Zakim> +danielweck; got it
- # [18:03] <Zakim> + +1.206.324.aabb
- # [18:03] * Joins: smfr (smfr@17.203.14.12)
- # [18:04] <Zakim> +??P37
- # [18:04] * Joins: arno (arno@192.150.10.201)
- # [18:04] * hober will be late calling in; still on the bus and forgot my iPhone
- # [18:04] <Zakim> + +1.408.536.aacc
- # [18:04] <arno> zakim, aacc is arno
- # [18:04] <Zakim> +arno; got it
- # [18:04] <Zakim> -??P37
- # [18:05] <Zakim> +smfr
- # [18:05] <Zakim> +??P37
- # [18:05] <Zakim> +[Microsoft.a]
- # [18:05] <kojiishi> zakim, ??p37 is me
- # [18:05] <Zakim> +kojiishi; got it
- # [18:05] * sylvaing hober, can you even get on an apple shuttle without an iphone ?
- # [18:05] * Joins: johnjan (qw3birc@128.30.52.28)
- # [18:05] <johnjan> zakim, microsoft has johnjan
- # [18:05] <Zakim> +johnjan; got it
- # [18:05] * Joins: cesar (acebal@85.152.178.140)
- # [18:05] * hober sylvaing: surprisingly enough, you can. :)
- # [18:06] <sylvaing> Zakim, aabb is sylvaing
- # [18:06] <Zakim> +sylvaing; got it
- # [18:06] <Zakim> +bradk
- # [18:07] <Zakim> + +050134aadd
- # [18:07] <danielweck> zakim, who am I ?
- # [18:07] <Zakim> I don't understand your question, danielweck.
- # [18:07] <danielweck> zakim, never mind.
- # [18:07] <Zakim> I don't understand 'never mind', danielweck
- # [18:07] <Zakim> + +1.415.920.aaee
- # [18:08] * Joins: szilles (chatzilla@192.150.10.200)
- # [18:08] * Joins: cathy (qw3birc@128.30.52.28)
- # [18:09] <Zakim> +Cathy_Chan
- # [18:09] <fantasai> ScribeNick: fantasai
- # [18:10] <Zakim> + +1.408.536.aaff
- # [18:10] <fantasai> plinss: Any other items for the agenda?
- # [18:10] * Joins: murakami (murakami@118.154.209.3)
- # [18:10] <fantasai> szilles: WD status for regions?
- # [18:10] * Joins: alexmog (qw3birc@128.30.52.28)
- # [18:11] <fantasai> plinss: Kyoto F2F, need agenda items
- # [18:11] <fantasai> plinss: Add them earlier so people have time to review and prepare
- # [18:11] <fantasai> http://wiki.csswg.org/planning/japan-2011
- # [18:12] <fantasai> plinss: Bert sent a message that we're missing reviews for CSS2.1
- # [18:12] <fantasai> TabAtkins_: Is there a way to see who has sent in a review?
- # [18:12] <plinss> https://www.w3.org/2002/09/wbs/33280/css21pr/results
- # [18:12] <fantasai> plinss: MS, Mozilla, Opera, and Apple have responded
- # [18:12] <fantasai> ?: Adobe?
- # [18:13] <fantasai> (Nokia and Opera are the others who have responded so far)
- # [18:13] <fantasai> plinss: Chris is missing, can't talk about charter
- # [18:13] <fantasai> plinss: Is Bert here to talk about website?
- # [18:13] <fantasai> plinss: Nope.
- # [18:13] <fantasai> plinss: Next is spec annotation system
- # [18:14] <fantasai> plinss: Just wanted to get some quick input, discussed on email
- # [18:14] * Bert is late, will join in 2 mins.
- # [18:14] <fantasai> plinss: Do we want to add this to CSS2.1? Do we want to use moving forward?
- # [18:14] <fantasai> TabAtkins_: Would def like to use for specs I edit
- # [18:14] <fantasai> szilles: +1
- # [18:14] <sylvaing> +1 as well
- # [18:14] <fantasai> arronei: Would like for 2.1 and any in the future if possible
- # [18:14] <fantasai> plinss: Any objection to adding to CSs2.1?
- # [18:15] <fantasai> RESOLVED: Use spec annotation system for CSS2.1 and future specs
- # [18:15] <Zakim> + +34.92.38.aagg
- # [18:15] <fantasai> topic: CJK longhand styles
- # [18:15] <plinss> http://lists.w3.org/Archives/Public/www-style/2011Apr/0764.html
- # [18:15] * Bert zakim, aagg is me
- # [18:15] * Zakim +Bert; got it
- # [18:15] <fantasai> TabAtkins_: Some ppl objected to complexity in lists
- # [18:15] <fantasai> TabAtkins_: The only complex parts I could potentially remove are the special styles like CJK ones
- # [18:16] <fantasai> TabAtkins_: They were defined up to 10^16, which is way more than any impl can do
- # [18:16] <fantasai> TabAtkins_: If I limit range to 10^4 I can represent Japanese and Korean styles as additive style
- # [18:16] <fantasai> TabAtkins_: And Chinese becomes much simpler
- # [18:16] <fantasai> TabAtkins_: I think 10,000 is a reasonable limit here.
- # [18:16] <fantasai> TabAtkins_: I wanted to know if anyone wants CJK longhand styles to go beyond
- # [18:17] <fantasai> arronei: I think your limit is reasonable, but I don't think it should be a hard limit.
- # [18:17] <fantasai> arronei: If a UA wants to go beyond then it should be able to do that.
- # [18:17] * Joins: glazou (glazou@82.247.96.19)
- # [18:17] * glazou is late, internet and phone were down , calling in now
- # [18:17] <fantasai> TabAtkins_: When you exceed the range, you drop to a fallback style
- # [18:17] <fantasai> TabAtkins_: In this case, drops to cjk-decimal
- # [18:17] <Zakim> +??P0
- # [18:18] <glazou> Zakim, ??P0 is me
- # [18:18] <Zakim> +glazou; got it
- # [18:18] <fantasai> bradk: Can't we say that if the UA supports the larger numbers, then they should do it in the more sophisticated way?
- # [18:18] <fantasai> TabAtkins_: If I'm not specifying it
- # [18:18] <fantasai> TabAtkins_: I either specify a larger range or a shorter range
- # [18:18] <fantasai> sylvaing: So once the fallback comes, can you get the proper numbers by more rules?
- # [18:18] <fantasai> sylvaing: by specifying ... [????]
- # [18:19] <fantasai> TabAtkins_: theoretically
- # [18:19] <fantasai> TabAtkins_: Officially, I could go up to 10^5 and still have all the same benefits, it's just 10^6 Japanese and Korean can't be additive, and Chinese gets more complex
- # [18:19] <fantasai> sylvaing: I would rather have the spec be clear
- # [18:19] <fantasai> TabAtkins_: There are other number systems already in the spec that have similar problems.
- # [18:20] <fantasai> TabAtkins_: Hebrew, ex, has ways of expressing numbers beyond the range in the spec right now.
- # [18:20] <fantasai> sylvaing: The use case isn't representing all numbers
- # [18:20] <fantasai> TabAtkins_: I could potentially go through and identify all the types of lists that have longer representations than I've defined
- # [18:20] <fantasai> TabAtkins_: Like circled decimal type, only has 50 Unicode chars. You could always synthesize more
- # [18:21] <fantasai> TabAtkins_: But I don't want to make things vague.
- # [18:21] <fantasai> TabAtkins_: Going through and explaining how to extend them would be more complexity than people want
- # [18:21] <fantasai> bradk: You were talking about putting those in an appendix
- # [18:21] <fantasai> TabAtkins_: The definitions are part of the spec in an appendix for ua stylesheet
- # [18:22] <fantasai> bradk: If you wanted to go beyond 10,000 you could still recommend what the UA puts in its style sheet
- # [18:22] <fantasai> TabAtkins_: If I carve out an exception for CJK longhand
- # [18:22] * Zakim fantasai, you typed too many words without commas; I suspect you forgot to start with 'to ...'
- # [18:22] <fantasai> TabAtkins_: That's inconsistent
- # [18:22] <cesar> zakim, aadd is me
- # [18:22] <Zakim> +cesar; got it
- # [18:23] <fantasai> TabAtkins_: We do know how to do it correctly, but nobody wanted to do that.
- # [18:23] <fantasai> fantasai: Not true. Webkit implements it in full (though buggy) and Mozilla implements it correctly up to its internal counter limit
- # [18:23] <fantasai> s/in full//
- # [18:23] <fantasai> bradk: Even if there were some exceptions for e.g. cjk-longhand, I think there'd be some value to have an exception for UAs that want beyond 10,000
- # [18:24] <fantasai> bradk: Some UAs in todays world have a problem going beyond such large numbers, but at some point other UAs won't mind
- # [18:24] <fantasai> TabAtkins_: So at that point we'll require larger limits
- # [18:24] <fantasai> ?: ... that don't want those limits
- # [18:24] <fantasai> TabAtkins_: Hardware limits always override anything the spec says
- # [18:25] <fantasai> 1) Define cjk counter styles up to 10^16 (full definition)
- # [18:25] <fantasai> 2) Define them up to 10,000 (artificially limited to simplify)
- # [18:25] <fantasai> 3) Allow both behaviors
- # [18:26] <fantasai> TabAtkins_: Note, the full definition is up to 10^68, but usually beyond that you switch to scientific notation
- # [18:27] <fantasai> fantasai: But we have a definition for up to 10^16 that we're pretty sure is correct
- # [18:27] <fantasai> TabAtkins_: Everybody does counters up to 2^30, some go up to 2^31
- # [18:27] <fantasai> TabAtkins_: That's like 10^12
- # [18:27] * sylvaing we could allow the e notation for Opera...
- # [18:27] <Zakim> +[Apple]
- # [18:28] <hober> Zakim, Apple has me
- # [18:28] <Zakim> +hober; got it
- # [18:28] <fantasai> TabAtkins_: There are only two complex styles left. Ethiopic-numeric and cjk longhand
- # [18:28] * Zakim fantasai, you typed too many words without commas; I suspect you forgot to start with 'to ...'
- # [18:29] <fantasai> sylvaing: It's complex for no use case, why would you have such a long list?
- # [18:29] <fantasai> TabAtkins_: Most styles defined to infinity, note
- # [18:29] <fantasai> bradk: Web is a big place. I'm not sure there aren't lists that go beyond 10,000 or that start at 10,000 and go to 20,000
- # [18:29] <fantasai> TabAtkins_: There are other types defined up to infinity
- # [18:29] * Joins: dsinger (dsinger@17.197.32.11)
- # [18:30] <fantasai> TabAtkins_: If I define the CJK styles out more fully, I'll want to define the other styles more fully
- # [18:30] <fantasai> TabAtkins_: to be more consistent
- # [18:30] <fantasai> ?: 10,000 seems like a reasonable artificial limit especially if we define the fallback for what happens if we go beyond that
- # [18:31] <fantasai> s/?/Arno
- # [18:31] <fantasai> plinss: I do think 10,000 items in the list is a reasonable limit, but I'm concerned about lists that don't counting at 1
- # [18:31] <fantasai> sylvaing: Maybe the use case is someone who has a paged view of a database
- # [18:32] <fantasai> sylvaing: You start at 12,000 one a particular page
- # [18:32] <fantasai> TabAtkins_: Printouts like that are the only really strong use case for lists that start at large numbers, and you won't use cjk longhand for that
- # [18:32] <fantasai> glazou: Use case is email. You can have thousands of email in a list
- # [18:33] <fantasai> TabAtkins_: are you going to use CJK numbers for that?
- # [18:33] <fantasai> glazou: why not
- # [18:34] <fantasai> TabAtkins_: Note that 10,000 and beyond will have a lot of characters, you have around two chars per digit
- # [18:34] * hober thinks the Romans got away with a 10K limit :)
- # [18:34] <fantasai> glazou: 10,000 is fairly common. 100,000 is more reasonable.
- # [18:34] <fantasai> TabAtkins_: I can go to 100,000 and keep things simple as they are
- # [18:35] <fantasai> glazou: I think that drastically reduces the risk of problems in the future
- # [18:36] <fantasai> sylvaing: ... the use case for high numbers is when you start at a very high number
- # [18:36] <fantasai> sylvaing: e.g. a paginated view of database results
- # [18:36] <fantasai> TabAtkins_: Is it use case enough that we define how to work those things?
- # [18:38] <dsinger> as I said before, we can define conformance out to some reasonable finite limit. well, we have to.
- # [18:38] <dsinger> and then if the definition of how to go higher is referenced or provided, UAs are welcome to knock themselves out
- # [18:39] <fantasai> fantasai: So we could spend the rest of the call talking about databases, or we could resolve on what to do
- # [18:40] <fantasai> 1) Define cjk counter up to 10^16 (full definition that we have ready to go, more than counter hardware limits in place now)
- # [18:40] <fantasai> 2) Definte them up to 10,000
- # [18:40] <fantasai> 3) Definte them up to 100,000
- # [18:40] <fantasai> 4) Put both definitions in the spec, allow UA to implement either, and mark full definition at-risk to see what ppl implement in CR
- # [18:41] <fantasai> arronei: I still think that UAs /may/ support up to 100,000 but may support numbers higher and leave it undefined
- # [18:42] <fantasai> TabAtkins_: You do have to define it because it's complex and ppl /will/ get it wrong
- # [18:42] <fantasai> fantasai: And we have the correct definitions already
- # [18:42] <Zakim> -Cathy_Chan
- # [18:42] <fantasai> TabAtkins_: I don't want ppl to get fallback in one UA, correct result in another UA, and wrong result in another UA because they got it wrong
- # [18:42] <Zakim> -bradk
- # [18:43] <dsinger> UAs are always at liberty to exceed requirements. you don't even have to say it
- # [18:43] <fantasai> glazou: You can always add a note that CSSWG might define beyond the limit later
- # [18:43] <Zakim> +bradk
- # [18:44] <fantasai> glazou: Put the definition to 100,000, allow UAs to go beyond, and add the note
- # [18:44] <dsinger> I just think it might be safer to define what they should do beyond the conformance limit, if they want to. it can be purely informative text
- # [18:44] <fantasai> fantasai: We have tnhe definition, if we're allowing UAs to go beyond the limit, I don't see any reason not to put the definition in the spec
- # [18:44] <fantasai> TabAtkins_: I prefer 3, can live with 1
- # [18:44] <dsinger> as I say, you can't prohibit people from doing more than is required
- # [18:44] <fantasai> 5) Define up to 100,000, allow UA to go beyond it, but DONT put a definition in for beyond 100,000
- # [18:45] <fantasai> 6) Definte up 100,000 allow UA to go beyond it, put an informative definition in for byeond 100,000
- # [18:45] <fantasai> We'll put a note for all of them
- # [18:46] <fantasai> dweck: My knowldge is limited. Abstain
- # [18:47] <fantasai> sylvaing: I think 6 works for me
- # [18:47] <dsinger> (1) is a testing nightmare, isn't it?
- # [18:47] <fantasai> arno: Go with 3, but live with 6
- # [18:47] <fantasai> smfr: 6
- # [18:47] <Zakim> -danielweck
- # [18:47] <smfr> let's give Tab more work :)
- # [18:47] <fantasai> koji: I prefer 6
- # [18:47] <Zakim> +??P10
- # [18:48] <danielweck> zakim, ??P10 is me
- # [18:48] <Zakim> +danielweck; got it
- # [18:48] <fantasai> arronei: 6
- # [18:48] <fantasai> césar: not sure
- # [18:48] <fantasai> Bert: no opinion
- # [18:48] <fantasai> glazou: 6
- # [18:48] <fantasai> bradk: 6
- # [18:49] <fantasai> plinss: I prefer 4, could live with 6
- # [18:49] <dsinger> dave defers to smfr (he's always right): 6
- # [18:49] * Joins: fantasai_ (fantasai@76.14.69.234)
- # [18:49] <fantasai_> hober: I prefer 6, but happy for tab to do less work as 3
- # [18:49] <fantasai_> szilles: prefer 3, live with 6
- # [18:50] <fantasai_> johnjan: prefers 6, very against 2
- # [18:50] <fantasai_> fantasai: same as plinss
- # [18:51] <fantasai_> RESOLVED: Define up to 100,000 with fallback to cjk-decimal beyond, allow UAs to implement longhand beyond that limit, put definition in informative appendix
- # [18:52] <fantasai> RESOLVED http://lists.w3.org/Archives/Member/w3c-css-wg/2011AprJun/0245.html
- # [18:52] <fantasai> not, noresolved
- # [18:53] * Joins: nimbupani (Adium@24.18.47.160)
- # [18:54] * Parts: nimbupani (Adium@24.18.47.160)
- # [18:54] <Zakim> -bradk
- # [18:54] <fantasai_> fantasai summarizes email
- # [18:54] <fantasai_> TabAtkins_: I'm going to want them defined because I need them in FlexBox for similar reasons
- # [18:54] <fantasai> fantasai summarizes issues
- # [18:54] <Zakim> +bradk
- # [18:54] <fantasai_> plinss: I'd like to see these width values advance as quickly as possible
- # [18:54] * bradk growls at the darn phone.
- # [18:55] * Quits: fantasai (fantasai@69.162.163.148) (Client exited)
- # [18:55] * gsnedders oh, so that's what the noise was. :P
- # [18:55] * gsnedders isn't actually dialed in
- # [18:55] <fantasai_> plinss: My concern is that UAs that don't want to support vertical mode
- # [18:56] <Zakim> -bradk
- # [18:56] <fantasai_> fantasai_: We can make it explicit that you can implement the module in parts, maybe make profiles
- # [18:56] * Joins: fantasai (fantasai@69.162.163.148)
- # [18:56] <Zakim> +bradk
- # [18:56] <fantasai_> plinss: Is that the best place to put it?
- # [18:56] <fantasai_> fantasai: I think so
- # [18:57] <fantasai_> [...] Bert: torn between elika and peter, would be hard to split it out
- # [18:58] <fantasai_> szilles: We should get it in and get it reviewed
- # [18:58] <fantasai_> arronei: put it in values and units?
- # [18:58] <fantasai_> fantasai: no, it's very tied to layout
- # [18:59] <fantasai_> fantasai: I have to define the concepts in writing modes anyway, I can just say 'btw, here are keywords for this'
- # [18:59] <fantasai_> fantasai: Can make a new section for it
- # [18:59] <fantasai_> fantasai: right now it's an appendix, could even leave it in the appendix
- # [18:59] <fantasai_> szilles: normative appendix sounds good to me
- # [18:59] <fantasai_> plinss: and all parts Tab would refer to are in that appendix?
- # [18:59] <fantasai_> fantasai: yeah
- # [19:00] <fantasai_> fantasai: if you really want to split it out later, let's do it as an editorial change in CR
- # [19:00] <szilles> +1 for a normative appendix in Writing Modes
- # [19:01] <fantasai_> arronei: make sure it's normative
- # [19:01] <fantasai_> arron: I would prefer a separate spec, but not against making it a normative appendix
- # [19:01] <fantasai_> szilles: I agree that it really belongs in the Box Module, but it needs to be in something that's progressing faster than the box module.
- # [19:02] <fantasai_> szilles: By making it an appendix, it makes it clearer that this is a separable piece that can/might be used elsewhere
- # [19:02] <fantasai_> arronei: Maybe add a note that this might be moved to e.g. future version of box module
- # [19:02] <fantasai_> RESOLVED: Add these keywords as an appendix, add note that they might be moved
- # [19:03] <fantasai_> szilles: Would like to give 1-week notice of request to publish WD of Regions.
- # [19:03] <fantasai_> szilles: Exclusions still needs more work.
- # [19:03] <fantasai_> szilles: hyatt posted some issues to www-style
- # [19:03] <fantasai_> plinss: OK
- # [19:03] <fantasai_> Meeting closed.
- # [19:03] <Zakim> -danielweck
- # [19:03] <Zakim> -[Microsoft]
- # [19:03] <Zakim> -smfr
- # [19:03] <Zakim> -arno
- # [19:03] <Zakim> -glazou
- # [19:03] <Zakim> -[Apple]
- # [19:03] <Zakim> -sylvaing
- # [19:03] <Zakim> -cesar
- # [19:03] <Zakim> -plinss
- # [19:04] * Quits: glazou (glazou@82.247.96.19) (Quit: glazou)
- # [19:04] <Zakim> -kojiishi
- # [19:04] <Zakim> -[Microsoft.a]
- # [19:04] * Parts: cesar (acebal@85.152.178.140)
- # [19:04] <Zakim> - +1.415.920.aaee
- # [19:04] <Zakim> - +1.408.536.aaff
- # [19:04] <Zakim> -TabAtkins
- # [19:04] * Quits: johnjan (qw3birc@128.30.52.28) (Quit: Page closed)
- # [19:04] * Quits: murakami (murakami@118.154.209.3) (Quit: Leaving...)
- # [19:04] <Zakim> -Bert
- # [19:04] <Zakim> -bradk
- # [19:04] <Zakim> Style_CSS FP()12:00PM has ended
- # [19:04] <Zakim> Attendees were plinss, +1.650.214.aaaa, TabAtkins, arronei, danielweck, +1.206.324.aabb, +1.408.536.aacc, arno, smfr, [Microsoft], kojiishi, johnjan, sylvaing, bradk, +050134aadd,
- # [19:04] <Zakim> ... +1.415.920.aaee, Cathy_Chan, +1.408.536.aaff, +34.92.38.aagg, Bert, glazou, cesar, hober
- # [19:04] * Quits: danielweck (dweck2@86.171.48.72) (Quit: danielweck)
- # [19:04] * Quits: dsinger (dsinger@17.197.32.11) (Quit: dsinger)
- # [19:05] * Parts: smfr (smfr@17.203.14.12)
- # [19:05] * Quits: bradk (bradk@99.7.175.117) (Quit: Get MacIrssi - http://www.sysctl.co.uk/projects/macirssi/ )
- # [19:06] * Quits: kojiishi (kojiishi@222.158.227.129) (Quit: Leaving...)
- # [19:11] * Quits: TabAtkins_ (tabatkins@216.239.45.4) (Quit: leaving)
- # [19:13] * Quits: szilles (chatzilla@192.150.10.200) (Ping timeout)
- # [19:19] * Quits: arno (arno@192.150.10.201) (Quit: Leaving.)
- # [19:19] * Joins: arno (arno@192.150.10.201)
- # [19:28] * Quits: arno (arno@192.150.10.201) (Quit: Leaving.)
- # [19:34] * Quits: cathy (qw3birc@128.30.52.28) (Quit: Page closed)
- # [19:46] * Quits: fantasai_ (fantasai@76.14.69.234) (Quit: leaving)
- # [19:47] <fantasai> RRSAgent: pointer
- # [19:47] <RRSAgent> See http://www.w3.org/2011/05/11-css-irc#T17-43-57
- # [19:47] <fantasai> RRSAgent: make logs public
- # [19:47] <RRSAgent> I have made the request, fantasai
- # [19:47] <fantasai> RRSAgent: make minutes
- # [19:47] <RRSAgent> I have made the request to generate http://www.w3.org/2011/05/11-css-minutes.html fantasai
- # [20:08] * Joins: szilles (chatzilla@209.133.115.254)
- # [20:11] * Quits: szilles (chatzilla@209.133.115.254) (Quit: ChatZilla 0.9.86.1 [Firefox 4.0.1/20110413222027])
- # [20:26] <fantasai> why is there a thread called Spec Annotations that talks about gradients?
- # [20:26] <fantasai> @_@
- # [20:33] * Quits: myakura (myakura@61.203.115.160) (Client exited)
- # [20:35] <fantasai> Bert: so, on the topic of the website, how would we go about updating the template for the blog?
- # [20:35] <fantasai> Bert: Is that something I can help with?
- # [20:35] * fantasai doesn't really understand the make system for the website, but could maybe do that part
- # [20:37] * Quits: Martijnc (Martijnc@84.192.44.100) (Quit: Martijnc)
- # [21:12] * Zakim excuses himself; his presence no longer seems to be needed
- # [21:12] * Parts: Zakim (rrs-bridgg@128.30.52.169)
- # [21:46] <Bert> Fantasai, there may be nothing to do for the blog.
- # [21:46] <Bert> The blog is a "skin" in PHP.
- # [21:46] <Bert> I already added a link to the style sheet and it seems to work without any other changes.
- # [21:47] * fantasai looks
- # [21:47] <fantasai> ?
- # [21:48] <Bert> Unless I discover errors, all I have to is remove the word "alternate"
- # [21:49] <fantasai> ...
- # [21:49] <Bert> Same for all other pages. I'm testing them, but the changes are getting less and less.
- # [21:49] <fantasai> Bert, that's not the right style sheet
- # [21:49] <Bert> I'm confident I can switch by the ebd of the month.
- # [21:49] <fantasai> Bert, that's not the right style sheet
- # [21:49] <fantasai> the right style sheet is this one http://www.w3.org/Style/CSS/StyleSets/W3CPro/main.css
- # [21:50] <Bert> It's called "Main" in the list of styles.
- # [21:50] <fantasai> I know
- # [21:50] <fantasai> that's not the style sheet for the redesign
- # [21:50] <fantasai> Main links to a different style sheet
- # [21:51] <Bert> I mainly worked from the zip file.
- # [21:51] <fantasai> what zip file?
- # [21:51] <fantasai> Why?
- # [21:51] <Bert> Still have a frustrating bug with Opera.
- # [21:51] <fantasai> BERT!
- # [21:51] <fantasai> why did you use the zip file?
- # [21:51] <fantasai> why didn't you use the style we resolved on?
- # [21:51] <fantasai> why did you change things around so much for no reason??
- # [21:51] <Bert> The zip file and the one on dropbox
- # [21:52] <fantasai> I don't understand what you used
- # [21:53] <fantasai> This is the WG resolution:
- # [21:53] <fantasai> http://lists.w3.org/Archives/Public/www-style/2011Apr/0429.html
- # [21:53] <fantasai> This is the design that was resolved on :http://csswg.inkedblade.net/staging/redesign/index-divya.html
- # [21:54] <fantasai> Why are you using anything other than what's there?
- # [21:54] <fantasai> I even put it on the W3C server for you!
- # [21:54] <Bert> The WG cannot decide on those pages, they aren't the WG's responsability.
- # [21:54] <fantasai> See, load the source, the links are to W3C
- # [21:55] <fantasai> Whose responsibility are they, then?
- # [21:55] <Bert> There were different colors on different browsers, so I had to choose.
- # [21:55] <Bert> The W3C Team, and in this case me, because I'm the Style Activity Lead.
- # [21:57] <Bert> The pages exist whether or not there are any WGs in that area.
- # [21:58] <fantasai> There were differnet colors on different browsers because they have differing levels of CSS support
- # [21:58] <fantasai> That's fine
- # [21:58] <fantasai> Nothing broke because of it
- # [21:58] <fantasai> It was designed to fall back gracefully
- # [21:58] <Bert> I also added an @media for very narrow windows, and used the background from http://dl.dropbox.com/u/952/csswg/csswg-onecol.html
- # [22:03] <fantasai> Bert, I've repeatedly asked you to explain what the problem is with the style sheet that you had to go change it
- # [22:03] <fantasai> so that we could work on it together
- # [22:04] <fantasai> and get something that we all agree looks as nice as the original design
- # [22:04] <fantasai> you haven't done that
- # [22:04] <fantasai> you just went and changed things around
- # [22:05] <fantasai> I still don't understand why you think there's a problem with Divya's design
- # [22:05] <fantasai> and why we can't just use it
- # [22:06] <fantasai> So I request that you post an explanation of why you took the approach you are taking
- # [22:06] <fantasai> which is to change the design
- # [22:06] <fantasai> without any consultation with either the WG or the original designer
- # [22:07] <fantasai> or me, who did a fair bit of technical cleanup on the design
- # [22:07] <fantasai> instead of taking the approach of explaining the problems you saw with the design
- # [22:07] <Bert> I was hoping Divya would spot the differences without me pointing them out, but so far she hasn't responded, at least not with any remarks about the design.
- # [22:08] <fantasai> and working with everyone to solve those problems
- # [22:08] <Bert> I can try to make list of the things I changed.
- # [22:09] <fantasai> That's not going to help me understand why you changed them
- # [22:09] <fantasai> me or the WG
- # [22:09] <Bert> Apart from the HTML background and the color of the shadows, they are just implementation details: using em where possible instead of px, not setting the font size, things like that.
- # [22:10] <Bert> Certain things where easy to make consistent in most browsers, other things I don't so much care about.
- # [22:11] <fantasai> Ok, fine, make an exhaustive list of changes
- # [22:11] <fantasai> /with/ explanations
- # [22:11] <fantasai> so that I can work it into the style sheets I uploaded to W3C
- # [22:12] <fantasai> because those are much easier to understand
- # [22:12] <fantasai> they have more comments
- # [22:12] <fantasai> they don't use hsl notation so they work in more browsers
- # [22:12] <fantasai> they have better indentation
- # [22:12] <fantasai> etc.
- # [22:13] <fantasai> I still don't understand why you didn't use those style sheets as the base for your work
- # [22:13] <fantasai> I really really don't
- # [22:16] <fantasai> Bert: Other than using em instead of px and not setting the font size, were there other *problems* with the style sheets?
- # [22:17] <fantasai> Bert: Because understanding /why/ you changed things is a lot more useful to me than understanding /what/ you changed.
- # [22:37] * Joins: arno (arno@192.150.10.201)
- # [22:38] * Quits: arno (arno@192.150.10.201) (Quit: Leaving.)
- # [23:31] * Quits: arronei (arronei@131.107.0.85) (Ping timeout)
- # [23:31] * Joins: arronei (arronei@131.107.0.81)
- # [23:42] * Joins: vhardy (vhardy@192.150.10.201)
- # Session Close: Thu May 12 00:00:00 2011
The end :)