Options:
Previous day, Next day
- # Session Start: Wed Dec 17 00:00:00 2014
- # Session Ident: #css
- # [00:00] * Joins: dbaron (~dbaron@public.cloak)
- # [00:08] * Joins: lajava (~javi@public.cloak)
- # [00:11] <fantasai> TabAtkins: http://lists.w3.org/Archives/Public/www-archive/2014Dec/0001.html
- # [00:12] * Joins: emeyer (~emeyer@public.cloak)
- # [00:22] * Quits: Ms2ger (~Ms2ger@public.cloak) ("nn")
- # [00:38] * Quits: emeyer (~emeyer@public.cloak) (emeyer)
- # [00:38] * Quits: lajava (~javi@public.cloak) (Client closed connection)
- # [01:10] * Quits: thinkxl (~thinkxl@public.cloak) (Ping timeout: 180 seconds)
- # [01:20] * Quits: antonp (~Thunderbird@public.cloak) (antonp)
- # [01:22] * Joins: tommyjtl (~tommyjtl@public.cloak)
- # [01:22] <fantasai> https://etherpad.mozilla.org/tab-and-fantasai
- # [01:30] * Quits: dbaron (~dbaron@public.cloak) ("8403864 bytes have been tenured, next gc will be global.")
- # [01:31] * Joins: dbaron (~dbaron@public.cloak)
- # [01:36] * Quits: tommyjtl (~tommyjtl@public.cloak) ("brb")
- # [01:46] <SimonSapin> fantasai: the current work page is missing a link to http://dev.w3.org/csswg/css-will-change/
- # [01:47] <fantasai> TabAtkins: https://dvcs.w3.org/hg/csswg/diff/b051771aca6c/css-align/Overview.bs
- # [01:48] <fantasai> TabAtkins: We can't write justify-content: true stretch
- # [01:48] <fantasai> TabAtkins: So it's stupid to allow justify-self: true stretch
- # [01:48] <fantasai> TabAtkins: It's stupid to allow either
- # [01:51] <fantasai> SimonSapin: Which category do I put it in?
- # [01:52] <SimonSapin> fantasai: the document is already listed, there is just no link
- # [01:52] <fantasai> question still stands :)
- # [01:53] <SimonSapin> do you mean sections like "Exploring"?
- # [01:54] <fantasai> yeah
- # [01:54] * fantasai is still trying to find the source file, it's been moved
- # [01:55] * tantek reads the scrollback to see emeyer showed up.
- # [01:55] <SimonSapin> I’m not sure what is the profound meaning of these sections. And I haven’t followed will-change closely enough to tell where it’s at these days.
- # [02:01] <fantasai> SimonSapin: Updated, should show up in a few minutes if I did it right
- # [02:01] <SimonSapin> cool, thanks
- # [02:10] <fantasai> well, it's on the server.
- # [02:10] <fantasai> but there seems to be some kind of rebuild that hasn't happened yet
- # [02:10] <fantasai> If it's not on a cron, then Bert will have to trigger it
- # [02:14] <fantasai> TabAtkins: Maybe modify http://dev.w3.org/csswg/css-flexbox/images/flex-pack.svg to put it in css-align?
- # [02:15] * Quits: adenilson (~anonymous@public.cloak) (adenilson)
- # [02:24] * Joins: jdaggett (~jdaggett@public.cloak)
- # [02:36] * Quits: tantek (~tantek@public.cloak) (tantek)
- # [02:58] * Quits: estellevw (~estellevw@public.cloak) ("Snuggling with the puppies")
- # [03:03] * Joins: emeyer (~emeyer@public.cloak)
- # [03:12] * Joins: liam (liam@public.cloak)
- # [03:44] * Quits: dbaron (~dbaron@public.cloak) ("8403864 bytes have been tenured, next gc will be global.")
- # [03:55] * Joins: dauwhe_ (~dauwhe@public.cloak)
- # [03:55] * Quits: dauwhe (~dauwhe@public.cloak) (Client closed connection)
- # [04:06] * Joins: estellevw (~estellevw@public.cloak)
- # [04:37] * Quits: estellevw (~estellevw@public.cloak) ("Snuggling with the puppies")
- # [04:41] * Joins: estellevw (~estellevw@public.cloak)
- # [04:45] <fantasai> dauwhe_: Does WebKit implement initial-letter: <size> <sink> or initial-letter: <sink> <size> atm?
- # [04:45] <fantasai> dauwhe_: Also, can you prep the draft and send it to ChrisL, or should I do that?
- # [04:45] <dauwhe_> fantasai: <sink> <size>. I filed a bug yesterday.
- # [04:46] <fantasai> dauwhe_: Cool
- # [04:46] <dauwhe_> fantasai: my first browser bug. Very scary.
- # [04:46] <fantasai> lol
- # [04:46] <fantasai> http://fantasai.inkedblade.net/style/talks/filing-good-bugs/
- # [04:46] <dauwhe_> fantasai: To prep, I change status to FPWD, add date, is there anything else?
- # [04:46] <fantasai> for less-scary bug filing in the future
- # [04:47] <fantasai> dauwhe_: I don't think so. I think ChrisL should be able to handle it from there.
- # [04:47] <dauwhe_> Overview.html validates and links are OK.
- # [04:47] <dauwhe_> The shortname changed, which may cause excitement.
- # [04:48] <fantasai> If it didn't, then it wouldn't be FPWD
- # [04:48] * dauwhe_ :)
- # [04:48] * fantasai hopes ChrisL can figure it all out
- # [04:48] * fantasai writes email about that
- # [04:48] <dauwhe_> I just sent him Overview.html?
- # [04:48] <dauwhe_> s/sent/send/
- # [04:49] <fantasai> No, he needs the whole folder, duh
- # [04:49] <fantasai> Did you seriously want to leave all your lovely illustrations behind? :)
- # [04:50] <dauwhe_> Ah, I was under the mistaken impression he had access to the repository :)
- # [04:50] <fantasai> In that case you could just check in the Overview.html and he could pull the whole thing, no?
- # [04:50] <fantasai> Otherwise can send a zipfile
- # [04:51] * fantasai is tired
- # [04:51] <dauwhe_> folder is small; easy to send zipped. Will do that.
- # [05:05] * plinss changes topic to 'logs: https://log.csswg.org/irc.w3.org/css/today - 2014-12-17 telcon agenda: http://lists.w3.org/Archives/Public/www-style/2014Dec/0266.html'
- # [05:11] * Quits: jdaggett (~jdaggett@public.cloak) (Ping timeout: 180 seconds)
- # [05:18] * Quits: estellevw (~estellevw@public.cloak) ("Snuggling with the puppies")
- # [05:25] * Joins: yamamoto (~yamamoto@public.cloak)
- # [05:25] * Quits: yamamoto (~yamamoto@public.cloak) ("Page closed")
- # [06:06] * Quits: emeyer (~emeyer@public.cloak) (emeyer)
- # [06:06] * Quits: dauwhe_ (~dauwhe@public.cloak) ("")
- # [06:19] * Joins: estellevw (~estellevw@public.cloak)
- # [06:31] * Joins: dbaron (~dbaron@public.cloak)
- # [07:12] * Quits: estellevw (~estellevw@public.cloak) ("Snuggling with the puppies")
- # [07:19] * Quits: liam (liam@public.cloak) (Ping timeout: 180 seconds)
- # [08:54] * Joins: zcorpan (~zcorpan@public.cloak)
- # [08:55] * Quits: zcorpan (~zcorpan@public.cloak) (Client closed connection)
- # [08:55] * Joins: zcorpan (~zcorpan@public.cloak)
- # [08:55] * Joins: antonp (~Thunderbird@public.cloak)
- # [09:48] * Joins: Ms2ger (~Ms2ger@public.cloak)
- # [10:00] * Quits: dbaron (~dbaron@public.cloak) (Ping timeout: 180 seconds)
- # [10:48] * Joins: lajava (~javi@public.cloak)
- # [11:07] * Joins: glazou (~glazou@public.cloak)
- # [12:03] * Joins: Florian (~Florian@public.cloak)
- # [12:04] * Joins: darktears (~darktears@public.cloak)
- # [12:29] <zcorpan> why do we have "rules for HTML4" appendices at all? http://dev.w3.org/csswg/css-writing-modes/#bidi-html
- # [12:30] * Quits: Florian (~Florian@public.cloak) (Client closed connection)
- # [12:30] <gsnedders> zcorpan: presumably it's just taken from the CSS 2.1 appendix
- # [12:30] * Joins: Florian (~Florian@public.cloak)
- # [12:31] * Quits: Florian (~Florian@public.cloak) (Client closed connection)
- # [12:31] * Joins: Florian (~Florian@public.cloak)
- # [12:31] <zcorpan> gsnedders: that doesn't answer my question
- # [12:31] * Quits: Florian (~Florian@public.cloak) (Client closed connection)
- # [12:40] <gsnedders> zcorpan: because HTML 4 doesn't define them and they had to be defined somewhere so they ended up in CSS 2, and then they got copied over when modularising it?
- # [12:40] <gsnedders> and nobody's bothered getting rid of them?
- # [13:45] <SimonSapin> gsnedders: since that involves updating a REC, yes
- # [13:51] * Joins: plh (plehegar@public.cloak)
- # [13:51] <gsnedders> SimonSapin: I mean why are they still in the CSS 3 modules that are WDs, not why it's still in CSS 2
- # [13:52] <SimonSapin> oh, sorry
- # [13:52] <SimonSapin> yeah, we should just remove these
- # [13:52] <SimonSapin> fantasai: ^
- # [14:02] * Joins: Florian (~Florian@public.cloak)
- # [14:09] * Quits: Florian (~Florian@public.cloak) (Ping timeout: 180 seconds)
- # [14:17] * Joins: liam (liam@public.cloak)
- # [14:51] * Joins: dauwhe (~dauwhe@public.cloak)
- # [15:09] * Quits: lajava (~javi@public.cloak) (Ping timeout: 180 seconds)
- # [15:17] * Joins: emeyer (~emeyer@public.cloak)
- # [15:21] * Joins: lajava (~javi@public.cloak)
- # [15:29] * Quits: dauwhe (~dauwhe@public.cloak) (Client closed connection)
- # [15:29] * Joins: dauwhe (~dauwhe@public.cloak)
- # [15:53] * Joins: Florian (~Florian@public.cloak)
- # [16:00] * Quits: Florian (~Florian@public.cloak) (Ping timeout: 180 seconds)
- # [16:02] * leaverou_away is now known as leaverou
- # [16:06] * plh is now known as plh-away
- # [16:19] * plh-away is now known as plh
- # [16:25] * Quits: liam (liam@public.cloak) (Ping timeout: 180 seconds)
- # [16:41] * Joins: estellevw (~estellevw@public.cloak)
- # [16:55] * Joins: Florian (~Florian@public.cloak)
- # [16:56] * Joins: thinkxl (~thinkxl@public.cloak)
- # [17:24] * Quits: glazou (~glazou@public.cloak) (glazou)
- # [17:24] * Quits: estellevw (~estellevw@public.cloak) ("Snuggling with the puppies")
- # [17:25] * Joins: liam (liam@public.cloak)
- # [17:45] * Joins: RRSAgent (rrsagent@public.cloak)
- # [17:45] <RRSAgent> logging to http://www.w3.org/2014/12/17-css-irc
- # [17:45] * Joins: Zakim (zakim@public.cloak)
- # [17:45] <plinss> zakim, this will be style
- # [17:45] <Zakim> ok, plinss; I see Style_CSS FP()12:00PM scheduled to start in 15 minutes
- # [17:48] * Joins: Rossen___ (~uid21900@public.cloak)
- # [17:49] * Joins: dbaron (~dbaron@public.cloak)
- # [17:52] * Joins: bcampbell (~chatzilla@public.cloak)
- # [17:52] * Joins: dael (~dael@public.cloak)
- # [17:56] <Zakim> Style_CSS FP()12:00PM has now started
- # [17:56] <Zakim> +dael
- # [17:57] <dael> ScribeNick: dael
- # [17:57] <Zakim> +plinss
- # [17:57] * Joins: adenilson (~anonymous@public.cloak)
- # [17:57] <Zakim> + +1.479.764.aaaa
- # [17:58] <Florian> Zakim, I am aaaa
- # [17:58] <Zakim> +Florian; got it
- # [17:58] * Joins: tantek (~tantek@public.cloak)
- # [17:58] * Joins: gregwhitworth (~gregwhitworth@public.cloak)
- # [17:59] <Zakim> + +1.415.832.aabb
- # [17:59] <Zakim> +??P29
- # [17:59] <adenilson> Zakim, ??P29 is me.
- # [17:59] <Zakim> +adenilson; got it
- # [17:59] <Zakim> + +1.907.315.aacc
- # [17:59] <sgalineau> Zakim, aabb is me
- # [17:59] <Zakim> +sgalineau; got it
- # [17:59] <Zakim> + +1.805.453.aadd
- # [17:59] <Zakim> +SteveZ
- # [17:59] <gregwhitworth> Zakim, 1.907.315.aacc is me
- # [17:59] <Zakim> sorry, gregwhitworth, I do not recognize a party named '1.907.315.aacc'
- # [18:00] <gregwhitworth> Zakim, +1.907.315.aacc is me
- # [18:00] <Zakim> +dauwhe
- # [18:00] <Zakim> +gregwhitworth; got it
- # [18:00] * Joins: murakami (~murakami@public.cloak)
- # [18:00] * leaverou is now known as leaverou_away
- # [18:00] <tantek> good morning #css - I will be IRC only til ~9:15 PST
- # [18:00] * Quits: emeyer (~emeyer@public.cloak) (emeyer)
- # [18:01] <Zakim> +??P36
- # [18:01] * Joins: MaRakow (~MaRakow@public.cloak)
- # [18:01] * Florian waves hi to Tantek
- # [18:01] <SimonSapin> Zakim, ??P36 is me
- # [18:01] <Zakim> +SimonSapin; got it
- # [18:01] <Zakim> +??P38
- # [18:01] * tantek waves at Florian :)
- # [18:01] <Zakim> +[Microsoft]
- # [18:01] * Joins: smfr (~smfr@public.cloak)
- # [18:01] * Joins: KeshavP (~KeshavP@public.cloak)
- # [18:01] <Zakim> +Stearns
- # [18:01] <Zakim> -??P38
- # [18:02] * Joins: BradK (~bradk@public.cloak)
- # [18:02] * Joins: emeyer (~emeyer@public.cloak)
- # [18:02] <Zakim> + +1.206.992.aaee
- # [18:02] <Zakim> +smfr
- # [18:02] <Zakim> +BradK
- # [18:03] <MaRakow> zakim, aaee is me
- # [18:03] <Zakim> +MaRakow; got it
- # [18:03] <Zakim> +??P38
- # [18:03] <Zakim> +[Microsoft.a]
- # [18:04] <Zakim> +[IPcaller]
- # [18:04] <murakami> zakim, ??P38 is me
- # [18:04] <Zakim> +murakami; got it
- # [18:04] <Rossen___> zakim, Microsoft.a is me
- # [18:04] <Zakim> +Rossen___; got it
- # [18:04] <bcampbell> aadd is me
- # [18:04] <Zakim> +[IPcaller.a]
- # [18:04] <dael> zakim, aadd is bcampbell
- # [18:04] <Zakim> +bcampbell; got it
- # [18:04] <fantasai> Zakim, IPcaller.a is me
- # [18:04] <Zakim> +fantasai; got it
- # [18:04] * Joins: bkardell_ (~uid10373@public.cloak)
- # [18:04] <antonp> Zakim, code
- # [18:04] <Zakim> I don't understand 'code', antonp
- # [18:04] <fantasai> Good morning everyone!
- # [18:04] <bkardell_> good morning
- # [18:05] <bcampbell> Mornin'
- # [18:05] * dauwhe [Beatles singing "good morning, good morning"]
- # [18:05] * fantasai is on 4G, this may be nstable
- # [18:05] <dael> plinss: Let's get started.
- # [18:05] * Florian antonp: the conference code is style (78953)
- # [18:05] <dael> plinss: I got the additional items from fantasai and sgalineau
- # [18:05] <Zakim> +??P46
- # [18:05] <dael> Rossen___: I have another about the inagural meeting about the whatever-its-called taskforce
- # [18:05] <Zakim> +dbaron
- # [18:05] * astearns the whatever task force
- # [18:06] <antonp> Zakim, ??P46 is me
- # [18:06] <Zakim> +antonp; got it
- # [18:06] * antonp thanks Florian
- # [18:06] <dael> Rossen___: Just quick update, I have a number of replies. The two days before the CSS F2F works for everyone. We will hold the meeting a Sydney on Feb 7 and 8 which is a Sat and Sun.
- # [18:06] <Zakim> +TabAtkins
- # [18:07] <dael> Rossen___: shans_ will follow-up with exact location, but it will prob be the same place. In the meantime we've resolved on a name, so we'll create a ML and wiki soon. It'll be similar to CSS meetings.
- # [18:07] <tantek> Florian - re: CSS3-UI pending edits - planning to do a block this week as other tasks have quieted down. http://lists.w3.org/Archives/Public/www-style/2014Dec/0201.html
- # [18:07] <dael> plinss: I'll ask about the domain. You can start on the extf name and we'll carry over.
- # [18:07] * dauwhe Thanks Rossen!
- # [18:07] <dael> plinss: Do we know where CSS is meeting in Sydney yet?
- # [18:07] <bkardell_> ?+
- # [18:07] <dael> TabAtkins: It's in the Sydney office.
- # [18:07] * Joins: andreyr (~andreyr@public.cloak)
- # [18:07] <dael> Rossen___: I thought it was on the wiki.
- # [18:07] <bkardell_> +?
- # [18:07] * Zakim wonders where ? is
- # [18:07] <dael> plinss: I looked, but maybe I missed it.
- # [18:07] <dael> TabAtkins: It's all on one line that says place.
- # [18:08] <dbaron> https://wiki.csswg.org/planning/sydney-2015 , under "Place"
- # [18:08] <tantek> Florian - please don't worry about writing patches for the simple edits, it's easier for me to just do edits directly than deal with all the machinations of applying patches.
- # [18:08] <dael> Rossen___: Has anyone been to the office?
- # [18:08] <dael> TabAtkins: Yeah. I can rec any of the hotels in China Town. Central business is maybe 15 min walk, but has nice hotels.
- # [18:08] <dael> Rossen___: Central is to the east?
- # [18:08] <dael> TabAtkins: Yes. Chinatown is to the south.
- # [18:08] <dael> Rossen___: Either is close enough to walk?
- # [18:08] <dael> TabAtkins: Yeah.
- # [18:08] <dael> plinss: If you can get actual names that would help.
- # [18:08] <dael> Topic: Box Alignment
- # [18:09] <dael> fantasai: Can you paste the link?
- # [18:09] <plinss> http://lists.w3.org/Archives/Public/www-style/2014Dec/0267.html
- # [18:09] * Florian tantek: thanks.
- # [18:09] * Florian Tantek: Can you join the call, since this has been put on the agenda...
- # [18:09] <dael> fantasai: The issue is in the previous draft we didn't let stretch combine with overflow. The issue is that this doesn't make sense because stretch doesn't respond to the keywords.
- # [18:09] <bkardell_> I tried to jump in there but couldnt ... trying to find out if we will be opening up WebRTC or a conf line for that inaugural meeting
- # [18:10] <astearns> I'm assuming "'true'/'self'" should be "'true'/'safe'" in the message?
- # [18:10] <dael> fantasai: stretch is more sim to content-distribution keywords. On content-alignment they can't combine with overflow position keywords. You can have a fallback alignment which can combine, but if you just just specify stretch there is no meaning.
- # [18:10] <dael> fantasai: TabAtkins checked in with some changes to change how things are organized and folded stretch in and it now means you can combine true and safe with stretch in align-self.
- # [18:11] <Zakim> +Alex
- # [18:11] <dael> fantasai: Do we revert that aspect, or do we want to allow this, bt only for align-self
- # [18:12] <dael> TabAtkins: And what safe/true do, for a couple of the alignment prop if you do align-self it does, but if it's bigger it oes outside and that might make it go outside scrollable. we made these so that you can say don't do whatever alignment you were going to do, just allow the start alignment.
- # [18:12] * Bert Sorry for being late, was discussing something away from my desk.
- # [18:12] * Bert zakim, alex is me
- # [18:12] * Zakim +Bert; got it
- # [18:12] <dael> TabAtkins: Stretch got it in there, it's always going to be safe anyoen, but there are a few other values like start that can't be un-safe. It doesn't do anything to have safe, but it allows it because calling out those things would make the grammar more complex.
- # [18:13] <dael> TabAtkins: This happened to make safe and true apply and it doesn't do anything. That's what fantasai is objecting to.
- # [18:13] <dael> fantasai: I don't think the grammar is more complex, it par content property more.
- # [18:13] <BradK> /me would rather have complicated grammar than meaningless values.
- # [18:13] <dael> fantasai: TabAtkins and I don't agree, so you all need an opinion.
- # [18:13] <dael> plinss: That you can't scroll in opp direction is a bug and we should fix that.
- # [18:13] <dael> TabAtkins: Yes, but for now that's not the question.
- # [18:14] <dael> dbaron: I think there's decent arguments on both sides. I can see authors having a way of gen values for these prop where you'd rather not deal with not producing safe or true. It also seems odd to have values that don't do anything
- # [18:14] * Florian tantek: i misread your earlier message, and now see that you will be on the call from 9:15. Include my previous request to join, since you are joining already
- # [18:15] <dael> fantasai: Another issue is in the future we might want fallback for stretch keyword in which case the grammar doesn't work the way it's supposed it. It doesn't work in the way it does with content-alignment
- # [18:15] * Florian s/include/ignore/
- # [18:15] <dael> TabAtkins: We'd be in the same boat as align-content properties.
- # [18:15] <astearns> I have a slight preference for not allowing a meaningless combination of keywords
- # [18:16] <dael> TabAtkins: fantasai one thing I realized is the baseline that don't alow safe/true will need it. The last-basseline defaults to end so you need to know if it's safe or true. We need to apply those to baseline so that would leave stretch as the only one without.
- # [18:16] <dael> fantasai: But in the baseline we have 4 that don't including stretch. We need consitant
- # [18:16] * fantasai thinks people who have an opinion should speak up and not just talk into the minutes
- # [18:16] <dael> TabAtkins: Or we can loosen on the other side. It won't do anything because it will default to reasonable things.
- # [18:16] * Ms2ger mumbles something about telcons
- # [18:16] <dael> fantasai: We need to have someone else speak up so we're going to be quiet for 30 sec
- # [18:17] * astearns thinks that recording an opinion in IRC should be sufficient :)
- # [18:17] * dbaron hasn't really had the chance to digest the issue
- # [18:17] <Zakim> + +1.201.892.aaff
- # [18:17] <gregwhitworth> I'm with dbaron
- # [18:17] <gregwhitworth> I would like more time
- # [18:17] <dael> plinss: We have 4 people with opinions and we're evenly split.
- # [18:17] <Bert> (Sorry, still trying to understand the issue. :-( )
- # [18:18] <dael> gregwhitworth: I'd echo dbaron. There's good arguements on both sides, it's difficult to pull the trigger on one.
- # [18:18] <dael> Rossen___: Should we wait until next week. I'm in the same group as dbaron. I haven't had a chance to review and absorb so I can have an opinion. It's important enough that we shouldn't just resolve for progress. I suggest doing this over mail. We can have a deadline for mail.
- # [18:19] <bkardell_> dael: s/gregwhitworth/bkardell_
- # [18:19] <dael> fantasai: We want to pub tomorrow b/c that's the last publish for end of year. I propose we revert the syntax to the old text, publish the spec tomorrow, and keep this on the telecon agenda.
- # [18:19] <dael> fantasai: I'd like the published and I'm okay to publish and add later.
- # [18:19] <dael> Rossen___: That sounds good if TabAtkins doesn't object.
- # [18:19] <bkardell_> this sounds p reasonable
- # [18:20] <dael> TabAtkins: I'll go with it.
- # [18:20] <bkardell_> +1
- # [18:20] <dael> plinss: I rec thaty ou revert and add an issue?
- # [18:20] <dael> TabAtkins: We'll need to since we have to apply the baseline. We'll pop something in there.
- # [18:20] <dael> plinss: Everyone okay with pub the WD?
- # [18:20] <dael> RESOLVED: Publish a new WD that doesn't have the changes, but instead has an issue
- # [18:21] <dael> Topic: WD of Inline Layout
- # [18:21] <dael> fantasai: There was an issue about floats, I don't know if we need to deal with that. Are we deferring?
- # [18:21] <dael> dauwhe: I think so. ChrisL has already started the process.
- # [18:21] <dael> fantasai: Okay. We'd like to pub a WD.
- # [18:22] <dael> ??: Now that I've reviewed, I think it has some issues, but it's a WD and it's going in the right dir so go ahead.
- # [18:22] <dael> plinss: Obj?
- # [18:22] <dael> RESOLVED: Publish Inline Layout WD
- # [18:22] <Florian> s/??/florian/
- # [18:22] <dael> Topic: Counter Styles to CR
- # [18:22] <Florian> s/I think it has some issues/I've sent some comments about it, some of which have been addressed already/
- # [18:22] * fantasai was pretty sure we had a standing resolution to take counter styles to CR
- # [18:23] <dael> TabAtkins: I haven't written the new DoC. There was one comment during LC period. It was a comment asking us to add the additional counter styles impl by at least two browsers. Made sense so I did so.
- # [18:23] <dael> TabAtkins: They were present in the old draft, we had removed them, I added them back and that was it. I've had no other comments to I believe it's stable.
- # [18:23] <dael> Florian: I'd echo fantasai comment, but yeah.
- # [18:23] <dael> plinss: obj?
- # [18:23] <dael> RESOLVED: Take Counter Styles to CR
- # [18:23] <dael> plinss: Do we have tests for the new ones?
- # [18:24] <dael> TabAtkins: I'm not sure if the existing tests do, but it's trivial to adjust so that can be done.
- # [18:24] <dael> plinss: That would be good. Standard CR period?
- # [18:24] <dael> TabAtkins: Yeah.
- # [18:24] <dael> Topic: findRule/deleteRule
- # [18:24] * fantasai wonders where ChrisL is
- # [18:25] <dael> sylvaing: Last time we talked we agreed to spec what browsers do as much as possible with the warning about a new API. For these two methods, the key job is to define the key arguement, which is a keyrame selector
- # [18:25] <dael> sylvaing: That can be sinlge value, % value or from/to keyword
- # [18:26] <dael> sylvaing: That works fine across browsers. One thing we need to agree on is if multi rules match your selector, which do you return. Webkit, Blink and IE return the first, Gecko does the last.
- # [18:26] <dael> TabAtkins: Other way around, I think. The bug Timothy Lo (sp?) said we switched to last.
- # [18:26] <dael> sylvaing: Let me check.
- # [18:26] <dael> Rossen___: Can you paste the test?
- # [18:26] <sgalineau> http://jsbin.com/jelili/5/edit?html,css,js,console
- # [18:26] <dael> sylvaing: Yeah.
- # [18:26] <TabAtkins> https://code.google.com/p/chromium/issues/detail?id=438387
- # [18:27] <dael> TabAtkins: Here's the bug that said we switched.
- # [18:27] <dael> sgalineau: The build I had returns first. So that means we have 2 doing each.
- # [18:27] <dael> TabAtkins: We had 2 before, we're now 3 to one.
- # [18:27] <dael> sgalineau: I don't think so.
- # [18:27] <dael> TabAtkins: That mplies we previously were 3 to 1
- # [18:27] <dael> sgalineau: I have 3 to 1 on doing it first.
- # [18:28] <dael> sgalineau: Point is...is there a good reason to pick one or the other? We need to pick. I think the last made most sense.
- # [18:28] <Zakim> +??P15
- # [18:28] <dael> sgalineau: Now that we cascade the benefit isn't asobvious to using last.
- # [18:28] <dael> TabAtkins: I'm in favor of sticking to last since we switched.
- # [18:29] <dael> dbaron: The code comment says, well, no it doesn't say why. It just says last instead of first and ref www-style posts.
- # [18:29] <Zakim> -adenilson
- # [18:29] <dael> sgalineau: It used to be the last one had the effect so it was reasonable at some point.
- # [18:29] <dael> dbaron: I think the internt was the last one was the winning one.
- # [18:29] <dbaron> http://lists.w3.org/Archives/Public/www-style/2011Apr/0037.html
- # [18:29] <Zakim> +??P24
- # [18:29] <dael> sgalineau: If we do the last, does anyone from Apple or Microsoft object to changing?
- # [18:30] <adenilson> Zakim, ??P24 is me.
- # [18:30] <Zakim> +adenilson; got it
- # [18:30] <dael> TabAtkins: In your earlier e-mail you said IE was returning the last.
- # [18:30] <Zakim> -adenilson
- # [18:30] <dael> sgalineau: That was wrong. I tried remote IE and it did first.
- # [18:30] <dael> sgalineau: The fact they can swing, I think we can change without distroying anything. I'm happy with doing last.
- # [18:30] <tantek> Zakim, ??P15 is me
- # [18:30] <Zakim> +tantek; got it
- # [18:30] <tantek> Zakim, mute me
- # [18:30] <Zakim> tantek should now be muted
- # [18:30] <dael> Rossen___: I wouldn't say I'm excited, but if we have to switch we still have a chance. What about webkit?
- # [18:30] * tantek reads scrollback.
- # [18:30] <dael> ??: We're fine switching
- # [18:31] <astearns> s/??/smfr/
- # [18:31] <dael> RESOLVED: findRul and deleteRule will apply to the last keyframe with a specified valeu
- # [18:31] <dbaron> (that resolution is no change to spec)
- # [18:31] <TabAtkins> sorry, accidentally pressed 6, like, a million times.
- # [18:31] <Zakim> +??P24
- # [18:31] * tantek TabAtkins maybe 6 6 times?
- # [18:31] <dael> sgalineau: When you spec value, what browsers agree on is the number and order must match the selector you agree on.
- # [18:31] <adenilson> Zakim, ??P24 is me.
- # [18:31] <Zakim> +adenilson; got it
- # [18:31] * TabAtkins tantek, surely 66 times?
- # [18:31] * dauwhe TabAtkins: thought you were playing us Christmas carols on your phone
- # [18:32] * tantek TabAtkins >:)
- # [18:32] <bkardell_> +1, that's lame
- # [18:32] * Quits: emeyer (~emeyer@public.cloak) (emeyer)
- # [18:32] <dael> sgalineau: So are we okay with requiring the same order and the interop today is that some browsrs aren't happy if you have spaces in there. You have to put your value without spaces. I think we should get ride of that.
- # [18:32] <dbaron> Gecko converts the selector to an array of floats and then tests deep equality on the arrays
- # [18:33] <dael> sgalineau: You need to know the values and query in the same order. So if the stylesheet says 50%,75% you need to go in that order. Is that are problem, or is it okay? That'st he interop today.
- # [18:33] * tantek realizes our IRC logs depend on JS :(
- # [18:33] <dael> sgalineau: The main issue is the whitespace. everyone agrees that the order mustmatch. The whitespace is the only wierdness. I haven't tried escaping and whatnot.
- # [18:34] <dael> dbaron: Is there interop on from and to matchin 0% and 100%?
- # [18:34] <dael> sgalineau: Yes.
- # [18:34] <dael> dbaron: And 100% matchin 100.0%?
- # [18:34] <dael> sgalineau: Good question.
- # [18:34] * tantek Florian are we good re: Agenda item 3? Per http://krijnhoetmer.nl/irc-logs/css/20141217#l-221 and http://krijnhoetmer.nl/irc-logs/css/20141217#l-234 ?
- # [18:34] <dael> dbaron: Gecko converts to an array of floats and does testing on the arrays. That's how we handle both conversions.
- # [18:34] * tantek notes that the krijnhoetmer logs work without JS, whereas the log.csswg.org IRC logs are *blank* without JS.
- # [18:34] <dael> smfr: I'd prefer we ignore whitespace which would be a change for webkit, but I think it's fine.
- # [18:35] <dael> sgalineau: So the user does the trimming?
- # [18:35] <dael> smfr: Basically whitespace is ignored or normalized. I think that would match expectations?
- # [18:35] <dael> plinss: And normallizing float numbers?
- # [18:35] <dael> sgalineau: It works in Chrome, I can check.
- # [18:35] <dael> smfr: Webkit does it via string, so I suspect we would fail. I'd be okay changing that.
- # [18:36] <dael> sgalineau: Webkit and Blink are happy with 100.0. I haven't tried FF. It's reasonable.
- # [18:36] <BradK> And 100% = 99.999999999999%?
- # [18:36] <dael> sgalineau: So we're saying for multi-value...for sinlge value it's matching of number values. For multi value we expect the number and order of values to match, but whitespace will be trimmed by browser.
- # [18:36] <dael> sgalineau: As long as number and order is good, you'll get the last rule that matches.
- # [18:37] <dbaron> sounds good to me
- # [18:37] <dael> RESOLVED: For multi value we expect the number and order of values to match, but whitespace will be trimmed by browser. As long as number and order is good, you'll get the last rule that matches.
- # [18:37] <tantek> zakim, unmute me
- # [18:37] <Zakim> tantek should no longer be muted
- # [18:37] <dael> Topic: CSS3 UI pending edits
- # [18:37] <dael> Florian: tantek said on IRC that he'd resolve them. Also we made a comment as to if I should write patches. I work better if I work on an issue until it's over.
- # [18:38] <dael> tantek: That's what the issues list is for. I keep notes on the wiki.
- # [18:38] <dael> Florian: So I'm not sure if you want me to do less...?
- # [18:38] <dael> tantek: I won't use patches for simple things because it's faster to make edits directly
- # [18:38] <dael> plinss: Lets not get into the weeds of editing techniques. It sounds like you have how to do the eidts done worked out.
- # [18:39] <dael> tantek: I can get a big block done in the next week.
- # [18:39] <dael> Florian: Since there's a patch for everything it shouldn't take long.
- # [18:39] <dael> tantek: Well, the patches do take long.
- # [18:39] <dael> plinss: You can sort that out offline
- # [18:39] <dael> Florian: I jsut want to make sure we keep making progress.
- # [18:39] <dael> Florian: We've been making a lot of progress on the telecons. I don't want to bring this up again since it's holding me up.
- # [18:40] <dael> tantek: I think we went over it, so I don't know what else to discuss.
- # [18:40] <dael> plinss: I think Florian wants a commitment to keep up on edits.
- # [18:40] <dael> Florian: I think that 5 of 23ish things are done. I'm hoping it's not tied up too much in the future. To be honest, I don't know why you don't like me doing them. In the past you said you'd do them and it wouldn't hold me up.
- # [18:41] <dael> tantek: I typically edit in bursts. I'll get to a block this week.
- # [18:41] <dael> plinss: I think when we discussed offline at TPAC, we just wanted to set a reasonable timeframe of something like 2 weeks. I think that's the expectation.
- # [18:41] <dael> tantek: lright.
- # [18:41] <dael> Topic: Flexbox and Tabbing
- # [18:41] <tantek> zakim, mute me
- # [18:41] <Zakim> tantek should now be muted
- # [18:42] <dael> bcampbell: Thanks to everyone that's been helping me. The problem we've been having is when visual order changes the tab order is following and there's a bu in mozilla realing with residual order.
- # [18:42] <dael> bcampbell: In a discussion, especially for screen reader, it surprisde me screen readers would like to follow the visual order instead of from the DOM. So the tab order, I was prop that it followed the visual order.
- # [18:43] <dael> bcampbell: The suggested wording is basically saying that rather than saying the order doesn't effect the default, we say that it does effect the order
- # [18:43] * Joins: ChrisL (clilley@public.cloak)
- # [18:44] <Zakim> +ChrisL
- # [18:44] <ChrisL> zakim, mute me
- # [18:44] <Zakim> ChrisL should now be muted
- # [18:44] <dael> fantasai: The reason the spec is how it is currently it because in cases you want the order different and it's better different, this makes it possible. If you always follow visual, you can't have a different order unless you futz with your layout. So if you have mobile and desktop layout and you have desktop side by side, but the logical order matches mobile, you want tab to follow mobile
- # [18:45] <dael> fantasai: You don't want to just left ot right because that visually looked better. You don't want to follow in that case. There's another case where someone is using visual to make changes that should have been at the source level. If you tie them together you can't split. I can see that maybe it's better becaue all the pages are terrible, but are we giving something up?
- # [18:45] <dael> fantasai: Should we never follow the source order or is it peole write bad pages?
- # [18:45] <dael> bcampbell: That's a good question and a long one.
- # [18:46] <ChrisL> rrsagent, here
- # [18:46] <RRSAgent> See http://www.w3.org/2014/12/17-css-irc#T17-46-03
- # [18:46] <ChrisL> rrsagent, make logs public
- # [18:46] <RRSAgent> I have made the request, ChrisL
- # [18:46] <fantasai> fantasai^: Are you saying that we should always follow the visual order on principle and it's bad to do otherwise, or are you saying that we should follow the visual order because there are too many bad pages and we should accommodate those at the expense of good pages?
- # [18:46] <dael> bcampbell: I think the suggestion is that, and I'd like to see an ex of what you talked about, we're talking about the majority of the cases that are keyboard only. I think the may be the weakness regarding how are the majority using flexbox andjust not knowing.
- # [18:47] <Rossen___> +q
- # [18:47] * Zakim sees Rossen___ on the speaker queue
- # [18:47] <dael> bcampbell: Having information that using flexbox for mobile and we're causing an issue, I'd like to bring that evidence back to th group. THe way I'm seeing it right now, they're asking for the same exp generally for web pages. This allows nav-index to fall away, but to change after that point we have to use tab index and you're forcing someone to use tab-index through the page.
- # [18:48] <dael> fantasai: So an ex would be something like the WG homepage where there's a title, an intro paragraph, and then quick links to things you'd want to hit fast and then we have short articles. We present linearly. When you increase wage width, we put the quicklines side-by0side on the left becausae that looked better.
- # [18:49] <dael> fantasai: in this case you're saying tab order would do links and then intro para even though the logical order is the opposite. We use order because you want this on the left even though the sourcce order is different.
- # [18:49] * Joins: emeyer (~emeyer@public.cloak)
- # [18:49] <dael> fantasai: I don't htink you'll see this in colum flexbox often, but left ot right for a viual person, there isn't quite as strong of a this comes first. Sometimes these are equally interesting. Or here's the stuff on the side that comes first, but I'll color it differently to make it less interesting.
- # [18:49] <dael> Rossen___: I have a few things.
- # [18:50] <fantasai> s/interesting/emphasized/
- # [18:50] <dael> Rossen___: What fantasai is explaining based on our experience with windows store that use grid and flex to control application layout. What we've seen and the feedback we've recieved, controlling tabbing or mag and new related apps, the visual order isn't nec what's desired.
- # [18:51] <tantek> zakim, unmute me
- # [18:51] <Zakim> tantek should no longer be muted
- # [18:51] <fantasai> bcampbell: Here's the layout I was talking about: http://csswg.inkedblade.net/staging/redesign/divya/
- # [18:51] <dael> Rossen___: So if you have sections nad usb sections, you want to nav between the sections. So you have business, sport, etc before you tab inside a section. If you only have visual order you have to go through all the business before you get to sport.
- # [18:51] * leaverou_away is now known as leaverou
- # [18:51] <dael> Rossen___: I would strongly suggest that you take that feedback/this kind of feedback back.
- # [18:52] <ChrisL> having to tab throughh all ityems of a list is even more annoying
- # [18:52] <dael> bcampbell: Isn't that a huge problem for a keyboard user? If you're jumping from section header to section header and not going into the sections to interact. The keyboard only user...
- # [18:52] <ChrisL> zakim, unmute me
- # [18:52] <Zakim> ChrisL should no longer be muted
- # [18:52] <tantek> q+
- # [18:52] * Zakim sees Rossen___, tantek on the speaker queue
- # [18:52] <tantek> ack Rossen___
- # [18:52] * Zakim sees tantek on the speaker queue
- # [18:52] <ChrisL> q+
- # [18:52] * Zakim sees tantek, ChrisL on the speaker queue
- # [18:53] <dael> Rossen___: You can always...this is somewhat in the hands of the app. If the only thing you use for nav is the tab key, which is hardly ever the case, this makes sense. But there's also the direction keys where this hub selection makes sense.
- # [18:53] <dael> bcampbell: I've seen a lot like this and this is a major challange right now. You have powerful shortcuts and you have an advantage over a keyboard user. So you're saying each section has a header, you have to do some code to get the person into a section. It's another facet of keyboard use. I understand what you're saying and I'd like to research more
- # [18:54] <Rossen___> q-
- # [18:54] * Zakim sees tantek, ChrisL on the speaker queue
- # [18:54] <dael> bcampbell: I'd really want to understand the impact of the responciveness of flexbox and when we're trapping peole into a particular flow if we flip this as suggested.
- # [18:54] <fantasai> bcampbell: (That page responds to media queries. Try resizing it very large/very small.)
- # [18:54] <dael> bcampbell: I'd like to keep the convo going and maybe bring it up in the next meeting.
- # [18:55] <dael> Rossen___: I can point you to come windows apps that use complex layout that use flex and grid and frag content with regions where you'll have even more challanges. There hass been a lot of qork done on our end and I believe the prop that you have will be quite limiting.
- # [18:55] <fantasai> bcampbell, The example here in Flexbox shows the use of reordering a column flexbox in an illogical way (pulling an image up above its header): http://dev.w3.org/csswg/css-flexbox/#overview
- # [18:55] <dael> bcampbell: OK. I understand what you're saying. I want to get my head around what you're saying and understand it really well.
- # [18:56] <dael> bcampbell: I see it in a different way. It'll take a long time to explain, but maybe I can lay it out in a better way.
- # [18:56] <bkardell_> maybe it is worth collecting a bunch of use cases and say how all are impacted by any choice
- # [18:56] <dael> plinss: We'll come back to it in the new year.
- # [18:57] <ChrisL> q- ChrisL
- # [18:57] * Zakim sees tantek on the speaker queue
- # [18:57] <bkardell_> +1 to what tantek is saying
- # [18:57] <dael> tantek: One of the challenges I find in the discussion is there aren't screenshots or URLs pointing to the examples. I've seen many layouts that need something more complex than sequential tabbing. I've seen it where you have to tab through 100 links to get to the next section. If there's a passion to fix this, rather than shoehorn an auto behavior, I'd like to see documented cases.
- # [18:57] <Rossen___> q+
- # [18:57] * Zakim sees tantek, Rossen___ on the speaker queue
- # [18:57] <dael> tantek: A link to a real website where we can see, or at least a screenshot that anyone can see. Anyone researching, please document incrementally. That allows the best analysis and particiaption from the group
- # [18:57] <tantek> ack tantek
- # [18:57] * Zakim sees Rossen___ on the speaker queue
- # [18:58] <tantek> ack Rossen___
- # [18:58] * Zakim sees no one on the speaker queue
- # [18:58] <ChrisL> tab navigation in maps is really poor
- # [18:59] <ChrisL> yes, its active exploration not "go through everything"
- # [18:59] <dael> Rossen___: And to add to that, while the examples you brought was a tab nav throug a visual map of something, that is for me a pretty connonical example where tab reordering would be the perfect tool to give an idea, like go through in order of pop size. The point is you have the same set of data, but you want to change the order based on the semantic you want to use. Visual only is limiting there.
- # [18:59] <tantek> I wonder if there are any good examples of sequential navigation for these examples.
- # [18:59] <dael> bcampbell: I agree in that situation, that makes sense. I'm trying to speak to keyboard only users.
- # [18:59] <dael> Rossen___: We understand.
- # [18:59] <tantek> perhaps on a /sequential-navigation page on the wiki?
- # [18:59] <dael> bcampbell: Let me try and get my research and I'll keep a running place for the information and have a good way to have a conversation. I see links people have been giving me
- # [19:00] <tantek> please keep the running documentation on the wiki
- # [19:00] <tantek> not some offline file
- # [19:00] <bcampbell> will do
- # [19:00] * Quits: KeshavP (~KeshavP@public.cloak) ("Page closed")
- # [19:00] <tantek> thank you bcampbell! appreciated!
- # [19:00] <Zakim> -[IPcaller]
- # [19:00] <Zakim> -sgalineau
- # [19:00] <bcampbell> thank you
- # [19:00] <Zakim> -smfr
- # [19:00] <Zakim> -adenilson
- # [19:00] <Zakim> -[Microsoft]
- # [19:00] <Zakim> -gregwhitworth
- # [19:00] <Zakim> - +1.201.892.aaff
- # [19:00] <Zakim> -BradK
- # [19:00] <Zakim> -fantasai
- # [19:00] <Zakim> -dbaron
- # [19:00] <Zakim> -antonp
- # [19:00] <Zakim> -dauwhe
- # [19:00] <Zakim> -Bert
- # [19:00] * Quits: gregwhitworth (~gregwhitworth@public.cloak) ("Page closed")
- # [19:00] <Zakim> -tantek
- # [19:00] <Zakim> -TabAtkins
- # [19:00] <Zakim> -Rossen___
- # [19:00] <Zakim> -Stearns
- # [19:00] <Zakim> -Florian
- # [19:00] <Zakim> -bcampbell
- # [19:00] <dael> plinss: That's the end of the hour. No meeting for the next two weeks. Happy Christmas, New Years etc. Travel safe. I'll miss the first meeting of the new year.
- # [19:00] <Zakim> -murakami
- # [19:00] <Zakim> -SimonSapin
- # [19:00] <Zakim> -plinss
- # [19:00] <dael> plinss: Thanks everyone.
- # [19:00] <Zakim> -SteveZ
- # [19:00] <Zakim> -dael
- # [19:00] <Zakim> -MaRakow
- # [19:00] <Zakim> -ChrisL
- # [19:00] <Zakim> Style_CSS FP()12:00PM has ended
- # [19:00] <Zakim> Attendees were dael, plinss, +1.479.764.aaaa, Florian, +1.415.832.aabb, adenilson, sgalineau, +1.805.453.aadd, SteveZ, dauwhe, gregwhitworth, SimonSapin, [Microsoft], Stearns,
- # [19:00] <Zakim> ... +1.206.992.aaee, smfr, BradK, MaRakow, [IPcaller], murakami, Rossen___, bcampbell, fantasai, dbaron, antonp, TabAtkins, Bert, +1.201.892.aaff, tantek, ChrisL
- # [19:00] * Quits: dael (~dael@public.cloak) ("Page closed")
- # [19:01] * Quits: MaRakow (~MaRakow@public.cloak) ("Page closed")
- # [19:01] * leaverou is now known as leaverou_away
- # [19:01] * Quits: adenilson (~anonymous@public.cloak) (adenilson)
- # [19:01] * Parts: BradK (~bradk@public.cloak) (BradK)
- # [19:16] * Joins: jcraig (~jcraig@public.cloak)
- # [19:19] * Quits: smfr (~smfr@public.cloak) (smfr)
- # [19:20] * Quits: liam (liam@public.cloak) ("the train has reached the station")
- # [19:29] * Quits: ChrisL (clilley@public.cloak) ("Client combusted")
- # [19:29] * Quits: andreyr (~andreyr@public.cloak) ("Page closed")
- # [19:32] * Joins: liam (liam@public.cloak)
- # [19:39] * Quits: Florian (~Florian@public.cloak) (Client closed connection)
- # [19:40] * Quits: liam (liam@public.cloak) (Ping timeout: 180 seconds)
- # [19:42] * Joins: adenilson (~anonymous@public.cloak)
- # [19:46] <bcampbell> Looking for link to best place in the wiki to create a page about flexbox testing/examples/etc?
- # [19:49] <TabAtkins> bcampbell: https://wiki.csswg.org/spec/css3-flexbox
- # [19:50] <bcampbell> Thank you. Do I need to request edit capabilities? I am logged in and do not see any.
- # [19:52] * leaverou_away is now known as leaverou
- # [19:52] <plinss> bcampbell: you should be good to go now
- # [19:53] <bcampbell> plinss: thank you, I see edit buttons now. do you recommend tacking onto/into this page or creating a new one?
- # [19:54] <TabAtkins> Tack onto the existing.
- # [19:54] <bcampbell> ok
- # [19:54] <plinss> start with that one, if you start to need a lot of space, make a new page and link to it form the main flexbox page
- # [19:54] <bcampbell> ok thanks
- # [19:55] <TabAtkins> Protip: never create a new page directly. Always do it by adding a link to the new page from an existing page, then follow it and create it from there. That guarantees you won't forget to link it in somewhere. ^_^
- # [19:56] <bcampbell> Excellent
- # [20:02] * leaverou is now known as leaverou_away
- # [20:02] * Joins: jcraig_ (~jcraig@public.cloak)
- # [20:03] * Quits: zcorpan (~zcorpan@public.cloak) (Client closed connection)
- # [20:05] * Quits: jcraig (~jcraig@public.cloak) (Ping timeout: 180 seconds)
- # [20:05] * jcraig_ is now known as jcraig
- # [20:26] * Quits: jcraig (~jcraig@public.cloak) (jcraig)
- # [20:30] * Joins: jcraig (~jcraig@public.cloak)
- # [20:34] * Quits: darktears (~darktears@public.cloak) (Ping timeout: 180 seconds)
- # [20:36] * Quits: dbaron (~dbaron@public.cloak) (Ping timeout: 180 seconds)
- # [20:39] * Joins: Florian (~Florian@public.cloak)
- # [20:41] * Joins: estellevw (~estellevw@public.cloak)
- # [20:48] * Quits: Florian (~Florian@public.cloak) (Ping timeout: 180 seconds)
- # [20:53] * leaverou_away is now known as leaverou
- # [20:59] * Zakim excuses himself; his presence no longer seems to be needed
- # [20:59] * Parts: Zakim (zakim@public.cloak) (Zakim)
- # [21:01] <tantek> good protip TabAtkins
- # [21:02] <tantek> bcampbell: for navigation issues in general - perhaps a page like "sequential-navigation" (implying the kind of navigation you get from tab index)
- # [21:03] * leaverou is now known as leaverou_away
- # [21:08] * Joins: dbaron (~dbaron@public.cloak)
- # [21:13] * Joins: zcorpan (~zcorpan@public.cloak)
- # [21:20] * Quits: zcorpan (~zcorpan@public.cloak) (Ping timeout: 180 seconds)
- # [21:21] * Quits: bkardell_ (~uid10373@public.cloak) ("Connection closed for inactivity")
- # [21:54] * leaverou_away is now known as leaverou
- # [21:58] * Quits: bcampbell (~chatzilla@public.cloak) (Ping timeout: 180 seconds)
- # [22:05] * leaverou is now known as leaverou_away
- # [22:05] * Joins: gregwhitworth (~gregwhitworth@public.cloak)
- # [22:11] * Quits: gregwhitworth (~gregwhitworth@public.cloak) ("Page closed")
- # [22:15] <emeyer> For TabAtkins, dbaron, and any other browser people: should I bother filing bugs about computing average gradient colors, or do you already have reports on file? My initial searches didn’t turn up anything, but thought I’d check before creating duplicates.
- # [22:15] <TabAtkins> I dont' think we have bugs on Chrome. Go for it.
- # [22:16] <emeyer> TabAtkins: https://code.google.com/p/chromium/issues/list or?
- # [22:19] * Joins: liam (liam@public.cloak)
- # [22:21] <tantek> emeyer - go for it for Moz too
- # [22:21] <emeyer> tantek: Okay, thanks.
- # [22:21] <TabAtkins> emeyer: Or new.crbug.com
- # [22:21] <emeyer> TabAtkins: thanks.
- # [22:22] <emeyer> I am finding many, many… interesting behaviors in various browsers around this. And not more than a few outright crashes.
- # [22:27] * Joins: bcampbell (~chatzilla@public.cloak)
- # [22:28] <bcampbell> tantek: thanks, sounds good.
- # [22:32] * Quits: shans_ (~shans@public.cloak) (Ping timeout: 180 seconds)
- # [22:32] * Joins: Florian (~Florian@public.cloak)
- # [22:39] * Quits: Florian (~Florian@public.cloak) (Ping timeout: 180 seconds)
- # [22:41] * Quits: estellevw (~estellevw@public.cloak) ("Snuggling with the puppies")
- # [22:53] <fantasai> emeyer: Awesome :)
- # [22:53] * fantasai does have your email on the to-reply list, just the last two weeks have been insane
- # [22:54] * Quits: adenilson (~anonymous@public.cloak) (adenilson)
- # [23:01] * Quits: dbaron (~dbaron@public.cloak) ("8403864 bytes have been tenured, next gc will be global.")
- # [23:01] * Joins: dbaron (~dbaron@public.cloak)
- # [23:08] * Joins: estellevw (~estellevw@public.cloak)
- # [23:17] * Quits: emeyer (~emeyer@public.cloak) (emeyer)
- # [23:37] * Quits: dauwhe (~dauwhe@public.cloak) (Client closed connection)
- # [23:56] * leaverou_away is now known as leaverou
- # [23:58] * Quits: Ms2ger (~Ms2ger@public.cloak) (Ping timeout: 180 seconds)
- # Session Close: Thu Dec 18 00:00:00 2014
Previous day, Next day
Think these logs are useful? Then please donate to show your gratitude (and keep them up, of course). Thanks! — Krijn