15:22:25 RRSAgent has joined #css 15:22:25 logging to http://www.w3.org/2011/10/12-css-irc 15:22:30 Zakim, this will be Style 15:22:30 ok, glazou; I see Style_CSS FP()12:00PM scheduled to start in 38 minutes 15:22:34 RRSAgent, make logs public 15:30:49 sylvaing has joined #css 15:44:34 arno has joined #css 15:54:38 danielweck has joined #css 15:57:07 ChrisL has joined #css 15:57:10 Style_CSS FP()12:00PM has now started 15:57:17 +??P18 15:57:22 alexmog has joined #css 15:57:22 Zakim, ??P18 is me 15:57:22 +glazou; got it 15:57:42 +??P19 15:57:44 -glazou 15:57:46 +glazou 15:57:57 Zakim, having a hickup? 15:57:57 I don't understand your question, glazou. 15:58:02 Zakim, ??P19 is me 15:58:02 +danielweck; got it 15:58:32 duga has joined #css 15:59:05 johnjansen has joined #css 15:59:12 +[Microsoft] 15:59:21 oyvind has joined #css 15:59:21 zakim, microsoft has johnjansen 15:59:22 +johnjansen; got it 15:59:39 +??P29 15:59:44 + +1.949.477.aaaa 15:59:50 + +1.206.324.aabb 15:59:52 + +1.619.846.aacc 15:59:53 Zakim, who is noisy? 15:59:55 zakim, ??P29 is me 15:59:56 +duga; got it 15:59:58 Zakim, aacc is me 15:59:58 +hober; got it 16:00:01 cesar has joined #css 16:00:03 +ChrisL 16:00:11 glazou, listening for 10 seconds I heard sound from the following: ??P29 (29%) 16:00:15 +Molly_Holzschlag 16:00:43 Zakim, aabb is sylvaing 16:00:43 +sylvaing; got it 16:00:56 + +975901aadd 16:01:03 Zakim, aaaa is duga 16:01:03 +duga; got it 16:01:10 + +1.215.286.aaee 16:01:11 zakim, microsoft has me 16:01:12 +[Microsoft.a] 16:01:12 +arronei; got it 16:01:24 kimberlyblessing has joined #css 16:01:26 +Bert 16:01:39 Zakim, mute duga 16:01:39 duga should now be muted 16:01:41 zakim, aadd is me 16:01:43 +cesar; got it 16:01:45 Zakim, unmute duga 16:01:47 duga should no longer be muted 16:01:49 + +1.206.552.aaff 16:01:53 Zakim, mute aabb 16:01:53 sorry, glazou, I do not know which phone connection belongs to aabb 16:01:54 thanks glazou 16:02:04 Zakim, who is noisy? 16:02:08 zakim, aaff is me 16:02:08 +nimbupani; got it 16:02:15 glazou, listening for 10 seconds I heard sound from the following: cesar (35%) 16:02:37 + +1.206.550.aagg 16:02:47 zakim, aagg is me 16:02:47 +stearns; got it 16:02:55 florianr has joined #css 16:03:14 + +47.23.69.aahh 16:03:41 howcome has joined #css 16:03:58 Zakim, aahh is howcome 16:03:58 +howcome; got it 16:04:06 Zakim, who is here? 16:04:10 On the phone I see glazou, danielweck, [Microsoft], duga, duga.a, sylvaing, hober, ChrisL, Molly_Holzschlag, cesar, +1.215.286.aaee, [Microsoft.a], Bert, nimbupani, stearns, 16:04:14 ... howcome 16:04:20 [Microsoft] has arronei 16:04:20 Zakim, aaee is me 16:04:24 On IRC I see howcome, florianr, kimberlyblessing, cesar, oyvind, johnjansen, duga, alexmog, ChrisL, danielweck, arno, sylvaing, RRSAgent, Zakim, glazou, kojiishi, Ms2ger, myakura, 16:04:31 ... mollydotcom, nimbupani, Florian, stearns, arronei, Hixie, plinss, lhnz, Bert, davve, gsnedders, hober, TabAtkins, krijnh, CSSWG_LogBot, ed, fantasai, pjrm, trackbot, shepazu 16:04:35 zakim, where is 215? 16:04:35 tabatkins_ has joined #css 16:04:40 +??P62 16:04:43 +kimberlyblessing; got it 16:04:46 + +1.425.246.aaii 16:04:48 bradk has joined #css 16:04:50 North American dialing code 1.215 is Pennsylvania 16:04:51 ChrisL 215 is Philadelphia 16:04:52 +[IPcaller] 16:04:52 Zakim, I am ??P62 16:04:58 +[Mozilla] 16:05:00 +florianr; got it 16:05:14 zakim, aaii is me 16:05:15 dbaron has joined #css 16:05:18 +alexmog; got it 16:05:22 +SteveZ 16:05:32 I can be. 16:05:33 + +1.650.275.aajj 16:05:46 Zakim, aajj is me 16:05:47 +bradk; got it 16:05:47 glazou: ^^ 16:05:49 -bradk 16:06:08 ScribeNick nimbupani 16:06:16 ScribeNick: nimbupani 16:06:31 bradk: wants to discuss epub discussion at TPAC 16:06:35 dsinger_ has joined #css 16:06:37 TabAtkins: wants to talk about … in 2.1 16:06:47 fantasai: discuss values and units 16:06:48 + +1.281.305.aakk 16:06:49 + +1.415.832.aall 16:06:55 Zakim, aakk is me 16:06:55 +tabatkins_; got it 16:06:58 Zakim, aakk is me 16:07:02 howcome: on Opera's implementation of GCPM 16:07:02 sorry, arno, I do not recognize a party named 'aakk' 16:07:12 +bradk 16:07:13 glazou: aboutf2f in paris 16:07:19 zakim, aall is me 16:07:22 glazou: there are 26 or 27 people registered which is a lot 16:07:29 +arno; got it 16:07:33 glazou: 1st choice has max attendance of 24 so its not feasible 16:08:21 smfr has joined #css 16:08:23 glazou: w3c office in paris suggests we can have 2 meeting rooms. conf from 6th - 8th of Feb. It is in downtown, 14 mins from subway station 16:08:37 + +1.408.636.aamm 16:08:38 I added the map link to http://wiki.csswg.org/planning/paris-2012 (and also the dates). 16:08:40 glazou: i will send list of hotels asap 16:08:45 Zakim, aamm is m 16:08:45 +m; got it 16:08:47 Zakim, aamm is me 16:08:47 sorry, smfr, I do not recognize a party named 'aamm' 16:08:53 Topic: TPAC 16:08:58 http://www.w3.org/mid/7534F85A589E654EB1E44E5CFDC19E3D0C29DDAE47@wob-email-01.agfamonotype.org 16:09:01 glazou: 2 reqs joint meeting with webfonts wg 16:09:21 ??: webfonts is not meeting at tpac but some members will be there. 16:09:43 glazou: ChrisL will be part of joint meeting on behalf of webfonts WG 16:09:56 ChrisL: i dont have a preferred time. 4 or 5people might be there. 16:10:08 ChrisL: the discussion topic is part of css3 fonts 16:10:23 ChrisL: rather than be specific for WOFF rather than font face for all formats 16:10:33 glazou: will john daggett attend TPAC? 16:10:53 dbaron: i suspect he is, i am not sure. 16:11:06 glazou: when is the best time to have meeting for japanese people in santa clara 16:11:19 dbaron: 5pm in CA is 9am in Japan 16:11:42 RESOLVED: Monday 5pm Web fonts joint meeting 16:11:45 or something, depending on sommer time 16:11:52 +??P13 16:12:01 bradk: can only attend for one day. preference tuesday. 16:12:10 RESOLVED: Tuesday meeting for e-pub 16:12:14 nimbupani: That's not Brad. 16:12:16 oops 16:12:24 who was it 16:12:28 Yes 16:12:31 Hang on 16:12:40 I built one out 16:12:45 http://wiki.csswg.org/planning/paris-2012 16:12:59 http://wiki.csswg.org/planning/tpac-2011 16:13:05 http://wiki.csswg.org/planning/tpac-2011 16:13:33 glazou: add meetings to the agenda http://wiki.csswg.org/planning/tpac-2011 16:13:39 nimbupani: Suspect it was jdaggett 16:13:58 I suspect it was brady duga 16:13:59 mollydotcom: is there some activity on sunday? 16:14:07 glazou: its a day of meeting for CSSWG 16:14:28 Yes, Brady not Brad 16:14:34 ah 16:14:41 s/bradk/brady 16:14:46 glazou: bert do we have a room 16:14:58 Bert: doubt it. i have not heard from orgn. Better to look for another place. 16:15:05 glazou: who can host meeting on sunday 16:15:09 fantasai: mozilla. 16:15:14 mollydotcom: we could also ask stanford. 16:15:25 ??: we can host in San jose @ Adobe 16:15:28 smfr has joined #css 16:15:37 I think ?? was Arno 16:15:39 glazou: san jose seems closest. 16:15:48 yep, that's me 16:15:54 arno: will check it out and get an official answer this week. 16:16:15 ChrisL: step out on monday 11-12 16:16:25 I would also step out with ChrisL 16:16:29 glazou: is there some overlap with AC meeting during days of CSS WG meeting. 16:16:37 Florian: i am not but dont think so. 16:16:46 glazou: if there is, he is not sure he is able to attend TPAC as he is sick. 16:16:55 glazou: if I am the only one chairing I will have a problem 16:17:10 Florian: there are AC meetings on tuesday 16:17:28 Florian: there is AC exec session for AC chairs 16:17:42 glazou: we will find a soln and I will discuss with ChrisL and Brady via email 16:17:42 https://www.w3.org/2011/11/TPAC/ac-agenda has AC starting at 2pm Tuesday 16:17:50 TabAtkins: ^ 16:17:53 are u on call? 16:17:58 I"m here, one sec. 16:18:02 attendees list for CSS WG at TPAC http://www.w3.org/2002/09/wbs/35125/TPAC2011/registrants#css 16:18:18 TOPIC: Gradients 16:18:40 Apparently no one can hear me. >_< 16:18:44 nope 16:18:46 no we can't 16:19:14 glazou: like to have an update. 16:19:56 TabAtkins: suggest we do what elika suggested defer final decision until TPAC and make quick decision and go to last call. 16:20:01 ChrisL: i think its a good plan 16:20:28 glazou: requesting everyone interested in gradients reads it and is ready before the joint TPAC 16:20:36 TabAtkins: will alert when I got something that is not a placeholder 16:20:42 glazou: how long do u need at TPAC 16:20:43 http://wiki.csswg.org/ideas/radial-gradients 16:20:49 TabAtkins: we need 20 to 30 mins 16:20:56 Florian: for such a heated topic? 16:20:57 8 hours! 16:20:59 ??: an hour 16:21:15 glazou: TabAtkins can u add to TPAC wiki page 16:21:28 s/??/arronei 16:21:44 TOPIC: Implied types and att annotation 16:21:44 http://www.w3.org/mid/CAAWBYDDasgHLxCjTk0gC-Qy_kmrt+Q_DqcuaukEB58d7=Dd8Pg@mail.gmail.com 16:21:54 TabAtkins: minor issues 16:21:55 s/att annotation/attr() notation 16:22:19 TabAtkins: there is an issue in spec for implied types. Wonder if we can have attr default to that type rather than string. 16:22:34 TabAtkins: me and fantasai dont think its workable. you are breaking uses of attr in the wild 16:22:49 -danielweck 16:22:51 howcome: by dropping issue you require type to be specified always? 16:22:57 +??P19 16:23:04 Zakim, ??P19 is me 16:23:04 +danielweck; got it 16:23:04 TabAtkins: default to string 16:23:15 i/wild/if you change one of those properties to accept other types/ 16:23:19 howcome: issue comes up when you have width = 200 and you want width to be pixels 16:23:29 TabAtkins: its not ideal. 16:23:46 glazou: does it have more downsides than upsides i dont htink its the case. 16:23:59 howcome: if its a number its unlikely that you want it to be a string 16:24:06 fantasai: then u need to parse to make sure its a number 16:24:22 fantasai: if you want width to be pixels then you need to specify as pixels otherwise it would be a string. 16:24:28 fantasai: you need to specify the unit 16:24:43 howcome: wondering if there is something else smart we can do and save people typing 3 chars 16:24:53 glazou: howcome do you want ot take an action item? 16:25:02 howcome: i dont think i will create a counter proposal 16:25:27 TabAtkins: alt is to allow properties to define default attr vals for themselves but seems like a lot of overhead 16:25:39 TabAtkins: auto inference is not possible. 16:25:48 howcome: if it has to be a default is string hte best? 16:25:59 TabAtkins: one requires no parsing and cannot fail 16:26:10 TabAtkins: for legacy reasons it is already required to be a string 16:26:21 glazou: accept this for time being and then if we find something smarter we use that 16:26:33 RESOLVED: accept default type of attr() as string 16:26:41 TOPIC: Question from sylvaing about new stuff in CSS OM 16:26:45 http://www.w3.org/mid/3C4041FF83E1E04A986B6DC50F01782938A101@TK5EX14MBXC297.redmond.corp.microsoft.com 16:26:52 dsinger__ has joined #css 16:27:10 we have a wiki page now, at least! 16:27:11 sylvaing: everytime we add a new @ rule we need a new constant in css4 for a new rule type 16:27:32 sylvaing: how do you define them without creating conflicts, need a branch for prefixed version. 16:27:47 sylvaing: one for viewport rule for e.g. brittle mechanism so what do we do next? 16:28:19 TabAtkins: we can continue same way with numeric constant and standardize on wiki page. Wiki is normative defn for num consts. do same for ranges for vendor prefix constants 16:28:27 TabAtkins: or switch over to string. 16:28:36 dbaron: i dont think memory aspect of string is smthing to worry about. 16:28:45 dbaron: good practice for api design is to use strings than constants. 16:28:55 sylvaing: we should agree on a cut off point. 16:29:06 TabAtkins: agreed. 16:29:09 Martijnc has joined #css 16:29:14 glazou: is this smthing to forward to annevk? 16:29:17 dsinger has joined #css 16:29:19 TabAtkins: ya 16:29:21 if we add a new string api, we could make all the things that don't get constants report UNKNOWN_RULE as the constant, or something like that. 16:29:25 :s 16:29:50 glazou: will it be a 20-30 min discussion at TPAC? 16:30:12 sylvaing: we should tidy up and assign constants. 16:30:25 dbaron: anne created a wiki page for the constants 16:30:37 glazou: we will discuss what we do at TPAC 16:30:44 http://wiki.csswg.org/spec/cssom-constants 16:30:55 sylvaing: wondering for W3C reffing a wikipage anyone can edit is that scary 16:31:00 glazou: are u sure about that? 16:31:12 TabAtkins: only those with wiki accounts possibly the testers 16:31:23 fantasai: we have ACLs for wiki page easy to restrict to wg 16:31:34 ChrisL: we have complete changelog so malicious changes can be rolled back 16:31:48 mollydotcom: assuming wiki is not that … in a secure way 16:31:55 fantasai: right now entire wiki is public 16:32:06 TabAtkins: restrict writing to WG members 16:32:19 glazou: readable by public and writable only by working group members 16:32:24 fantasai: which page. 16:32:32 glazou: the url dbaron pasted 16:32:47 glazou: need to add viewport rule to that list 16:32:56 that's what I've been doing 16:33:02 glazou: sylvaing edit wikipage for TPAC and add discussion 16:33:04 Sylvain: no need, just got it there 16:33:14 well, the discussion - I'm adding the URL 16:33:17 http://www.w3.org/mid/CAHSVx=8sOOh=5Wr2cv4eUhT8AzWTdnPybpFF-WR5ujEqEESwiA@mail.gmail.com 16:33:18 TOPIC: req from paul_irish on css3 conditional 16:33:30 glazou: dbaron i think u commented on that. 16:33:39 glazou: adding an api matching 16:33:53 TabAtkins: i dont think much needs to be discussed. dbaron seemed agreeable to adding that 16:33:58 glazou: everyone agrees on that? 16:34:11 http://lists.w3.org/Archives/Public/www-style/2011Oct/0323.html 16:34:13 cssom-constants is already locked down as edit only for css-wg members and a group made for other trusted members 16:34:23 whats the resolution? 16:34:39 TOPIC: LC for css3-speech 16:34:42 http://wiki.csswg.org/spec/css3-speech 16:35:29 RESOLUTION: add paul irish's suggested api to the spec 16:35:34 TOPIC: LC for css3-speech 16:35:41 I can't edit the CSSOM Constants page anymore :( 16:35:56 danielweck: Currently 18 issues filed. cant go thro each. 16:36:21 sylvaing, try now? 16:36:25 danielweck: WG needs to reach consensus on each of these issues. When we accept suggested change in spec, whats the next step? 16:37:00 glazou: let the commenter know that you addressed the comments, say smthing about the resolution. that person needs to accept or reject your resolution of hte problem 16:37:01 fantasai, thanks! 16:37:17 danielweck: what about bigger issues? potential blocker language selection features for TTS voice. 16:37:24 danielweck: irrespective of nature of markup. 16:37:47 danielweck: would be a new feature, if we were to accept to introduce the new feature, we mark it at-risk and we republish another LC? 16:37:50 ChrisL: yes 16:38:07 glazou: or you can reject the feature and say you will consider for future version 16:38:48 fantasai: if there is an issue where you and commenter is not agreeing escalate to WG either we make the change or reject. that becomes the official WG response, they either accept or formally object. tht will get recorded in the list of issues and presented to director. 16:39:07 -smfr 16:39:30 fantasai: we can go to LC when commenter disagrees with us 16:39:45 danielweck: paul ba* co-author of … 16:39:54 bagshaw? 16:40:04 danielweck: it was one of the major changes of 1.0 to 1.1 of SSML(?) 16:40:24 danielweck: the abstract of css3 speech states that ssml 1.1 model it implies it follows to letter, it is more flexible goal 16:40:25 +smfr 16:40:34 ChrisL: which of these options do u want to do? 16:40:47 danielweck: i would rather stick to our guns 16:41:07 danielweck: forcing the implementers to convey a set of info about tts voices to styling engine 16:41:30 danielweck: risk it will be implemented badly and normative stuff needs to be added to spec if it needs to work 16:41:40 glazou: reasonable to reject and kind of argument we can show to dir. 16:41:48 ChrisL: do we have a WG resolution to back that? 16:42:05 danielweck: eventually perhaps next week we should go thro the issues and record the WG consensus 16:42:13 danielweck: i am happy to work thro this one now. 16:42:29 glazou: sounds perfect 16:42:43 fantasai: make sure you end every response with "please let us know if this satisfies your concern" 16:42:46 danielweck: totally 16:42:54 -ChrisL 16:43:22 glazou: the FPWGPC and u still added them for official list of issues for last call 16:43:28 +ChrisL 16:43:31 glazou: you have an option to reject htem coz its too late. 16:43:37 fantasai: they got an extension 16:43:42 glazou: it arrived only ½ days ago 16:43:47 er 1 or 2 days 16:44:35 -nimbupani 16:45:01 nimbupani1 has joined #css 16:45:09 oops got d/ced 16:45:24 danielweck: Many of their issues argue that the features in CSS Speech hijack the screen-reader experience, which is.. interesting. 16:45:32 +nimbupani 16:45:33 danielweck: I think we need to clarify that 16:45:58 RESOLVED: WG backs danielweck's decision to reject issue-2 for good technical reasons. 16:46:12 http://wiki.csswg.org/spec/css3-speech#issue-2 16:46:15 -glazou 16:46:21 ChrisL: are u clear on next steps danielweck? 16:46:36 danielweck: i hope you can take a look at the issues next week so we can make informed decision 16:46:54 ChrisL: listing of issues and then look at commenters disagreed on resolution. 16:47:14 danielweck, just let me know when you're done with the DoC in the wiki and I'll convert and colorize it for you 16:47:22 TOPIC: 2.1 inherit 16:47:28 Thanks Fantasai! 16:47:38 tab 2.1 inherit http://www.w3.org/Bugs/Public/show_bug.cgi?id=14420 16:47:42 TabAtkins: address issue on inital value in draft 16:47:55 TabAtkins: orgn 2.1 said inherit computed to computed value of its parents 16:48:12 TabAtkins: currently: if cascaded value is inherit specified value = specified value of parent. both wrong 16:48:20 dbaron: currently sez is ambiguous 16:48:34 TabAtkins: if cascade value is inherit, specified value is computed value. 16:48:39 Florian: what is specified value 16:48:53 TabAtkins: specified value is pre-any-transformation any value 16:49:08 thought specified was the value written by the author in their stylesheet 16:49:22 dbaron: whats not clear to me is why specified value isnt just inherit 16:49:28 if the parent value is also inherit? 16:49:50 -[Microsoft] 16:50:10 TabAtkins: not how normal inheritance works, 2. issues with inherit being a specified value, probably not a problem in practice. 16:50:17 TabAtkins: consistency with real inheritance. 16:50:41 /works/, inheritance takes the computed value of the parent as the specified value on the child/ 16:50:49 seems like there's some duplication in 6.2.1 vs 6.1.1... 16:50:51 ChrisL: i dont hear anyone expressing much of an opinion. are people comfortable with the change. it would be an errata. 16:50:59 TabAtkins: it would also change values * units 16:51:14 dbaron: change in 6.1.1 and 6.2.1 16:51:25 TabAtkins: both needs to be changed 16:51:38 The spec generally assumes that the specified value resolves to a real value, and says "if the specified value is foo, do ..." in many places 16:51:40 TabAtkins: we will resolve inherit and initial at that point. 16:52:15 howcome: its consistent with css3 cascade module 16:52:17 sylvaing, I think it changed after http://lists.w3.org/Archives/Public/www-style/2011Mar/0507.html 16:52:25 whats the resolution 16:52:53 -danielweck 16:52:56 -SteveZ 16:53:03 RESOLVED: accept TabAtkins and fantasai inherit turns the specified value into the parent's computed value 16:53:15 +??P19 16:53:18 fantasai/tab CSS 3 V@U issues http://www.w3.org/Style/CSS/Tracker/products/8 16:53:29 RESOLVED: accept TabAtkins and fantasai's proposal such that inherit turns the specified value into the parent's computed value 16:53:33 Zakim, ??P19 is me 16:53:33 +danielweck; got it 16:54:10 fantasai: vm unit is really a v min unit min of vh and vw 16:54:21 fantasai: since we hae a min f() we can remove it. 16:54:27 fantasai: alt we can rename it 16:54:35 fantasai: its not clear what it is 16:54:38 to vmin 16:54:47 dbaron: concerned coz min() is at risk and likely to get dropped 16:55:13 TabAtkins: at min we should rename to vmin we can mark it as at-risk and at our at-risk notes one or the other should be dropped 16:55:29 howcome: : why dont we continue to have 2char units 16:55:39 fantasai: i dont think its worth the confusion 16:56:09 ChrisL: is that a strong obj 16:56:14 fantasai: Could stand for vmin or vmax 16:56:18 howcome: going to 4 is suddenly outside of tradition 16:56:18 tabatkins_: or vmean :) 16:56:34 ChrisL: in this case there is a motivation for the change as its ambiguous 16:56:59 fantasai: vmin makes it very obv to person reading the stylesheet 16:57:08 TabAtkins: salvage min f() it would be preferable 16:57:27 ??: are there places where u can use unit cant use min 16:57:43 TabAtkins: calc should be usable anywhere that expects a length (min/max too) 16:57:54 ??: even with 4 char its compact than using min 16:57:58 -duga.a 16:58:23 mollydotcom: does not have an opinion at this point. 16:58:33 mollydotcom: vmin on its own make more sense 16:58:41 min(5vh, 5vw) 16:58:44 vs 5vmin 16:59:37 TabAtkins: we can see if there is any use in the wild of those 16:59:46 TabAtkins: not sure what the usecase of vmin 17:00:02 howcome: make sure your image does not get outof hte viewport 17:00:12 mollydotcom: cant imagine a usecase 17:00:19 -dbaron 17:00:22 howcome, use max-height: 100%; max-width: 100%; 17:00:25 ??: no vmax to ensure complete coverage? 17:00:48 -howcome 17:00:54 ChrisL: cant get to your topic howcome is it okay to do it on next call 17:01:02 ChrisL: lets take it to email. 17:01:09 ChrisL: call adjourned! 17:01:16 bye! 17:01:17 Just use 71% ;) 17:01:20 -[Microsoft.a] 17:01:21 -kimberlyblessing 17:01:22 -smfr 17:01:23 -Molly_Holzschlag 17:01:23 -hober 17:01:23 max-height/-width only works if containing block is the ICB, right? 17:01:24 -sylvaing 17:01:24 -ChrisL 17:01:25 smfr has left #css 17:01:25 -arno 17:01:27 -tabatkins_ 17:01:29 -??P13 17:01:31 -cesar 17:01:33 -duga 17:01:35 -nimbupani 17:01:37 oyvind: ah, good point 17:01:39 -stearns 17:01:41 -alexmog 17:01:43 -Bert 17:01:45 -florianr 17:01:47 -[IPcaller] 17:01:47 florianr has left #css 17:01:49 -danielweck 17:01:51 oyvind: max-height: 100vh; max-width: 100vw 17:02:13 nimbupani, that was me with the vmax comment 17:02:19 bradk: oops 17:02:26 fantasai: will fix it =) 17:02:29 's OK 17:02:43 -bradk 17:02:44 Style_CSS FP()12:00PM has ended 17:02:45 Attendees were glazou, danielweck, johnjansen, +1.949.477.aaaa, +1.206.324.aabb, +1.619.846.aacc, duga, hober, ChrisL, Molly_Holzschlag, sylvaing, +975901aadd, +1.215.286.aaee, 17:02:50 ... [Microsoft], arronei, Bert, cesar, +1.206.552.aaff, nimbupani, +1.206.550.aagg, stearns, +47.23.69.aahh, howcome, kimberlyblessing, +1.425.246.aaii, [IPcaller], florianr, 17:02:52 ... alexmog, SteveZ, +1.650.275.aajj, dbaron, bradk, +1.281.305.aakk, +1.415.832.aall, tabatkins_, arno, +1.408.636.aamm, smfr 17:03:00 fantasai, right, I guess that would work 17:03:11 TabAtkins, someday I should sit down with you and explain how hard min() and max() are... 17:03:41 dbaron: I'd like to understand 17:04:04 dbaron: I think it would make a fascinating article for devs 17:05:26 I would be interested also,conceptually min and max functions seems simple 17:05:46 cesar has left #css 17:05:49 ChrisL, like floats? :) 17:06:18 like IEEE floats with scientific notation.dead simple 17:06:19 they seem simple, but how often do you nest them in a tree and then resolve them ? 17:06:47 so it needs a rootwards tree walk to resolve? 17:07:11 rootwards sounds like a dental procedure 17:07:14 is there an issue with circularity? 17:12:25 no, the problem is that many times percentage widths are used in computations in manners other than "take the input and multiply it by the percentage" 17:12:54 one of the problems, anyway 17:13:24 can you give a simple example? 17:13:47 I believe calc() with min() and max() allows all piecewise-linear continuous functions from percentage-basis to result, which makes things pretty messy. 17:14:05 An example would be: 17:14:34
second cell
17:14:40 the table ends up 400px wide 17:16:07 is there another width somewhere on the table? 17:16:11 this is where I'm confused. 17:17:05 25% of what is my question. 17:17:26 mollydotcom, no. content of the first cell is 100px, but because it's also 25% of the total you end up with a 400px table 17:18:35 ah okay, took me a minute 17:18:38 ;) 17:20:07 nimbupani1 has joined #css 17:28:58 danielweck has joined #css 17:52:14 mollydotcom has left #css 18:05:37 stearns has joined #css 18:08:36 fantasai, so given that everybody seems to forget about the 1/100 factor for vh/vw/vm, I really wonder if we shouldn't have the 1/100 factor... 18:09:46 +1 18:14:46 hmm, I wrote a response and then realized the email I was responding to was on the WG list... 18:18:37 miketaylr has joined #css 18:21:23 howcome has joined #css 18:23:53 arronei, is it ok with you if I reply to https://lists.w3.org/Archives/Member/w3c-css-wg/2011OctDec/0041.html on the public list, quoting part of your message? 18:33:23 dbaron: Sounds like a plan. When would you like to do so? 18:33:39 TabAtkins, at tpac? 18:33:53 kk 18:35:34 dbaron: (reading scrollback) Yeah, that table example is why I tried arguing against that behavior last time it came up. Layout should proceed downward as much as possible. 19:22:20 Zakim has left #css 20:54:27 arronei_ has joined #css 22:19:32 alexmog has joined #css 23:25:28 arno has joined #css