Status Meetings:2006-10-04:Log

From Camino Wiki
Revision as of 10:39, 4 October 2006 by Sardisson (talk | contribs) (temp log until ss posts one with nice wrapping)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

This is a temporary log until ss posts the official log.

[12:00pm] kreeger joined the chat room.
[12:00pm] pinkerton joined the chat room.
[12:00pm] pinkerton was promoted to operator by ChanServ.
[12:01pm] cl|out joined the chat room.
[12:01pm] cl|out: ooh, look at that
[12:01pm] cl|out: just in time for the meeting.
[12:01pm] cl|out is now known as cl.
[12:01pm] peeja joined the chat room.
[12:02pm] You were promoted to operator by froodian.
[12:02pm] cl was promoted to operator by froodian.
[12:02pm] kreeger was promoted to operator by froodian.
[12:02pm] murph was promoted to operator by froodian.
[12:02pm] peeja was promoted to operator by froodian.
[12:02pm] Pinolo was promoted to operator by froodian.
[12:02pm] ardissone|majnun: ss|gone: are you here?
[12:02pm] froodian: no
[12:02pm] kreeger2_ joined the chat room.
[12:02pm] froodian: sam can't make it
[12:02pm] ardissone|majnun: k
[12:02pm] You are now known as ardissone.
[12:02pm] froodian: maxr opped me and gave the message
[12:02pm] ardissone:                           
[12:02pm] ardissone: so you're running today's show
[12:02pm] froodian: ok
[12:03pm] froodian: anybody missing?
[12:03pm] ardissone: delliott is in the channel but not here
[12:03pm] ardissone: if he's "there"
[12:03pm] froodian: i invited him
[12:03pm] kreeger2_ is now known as kreeger2.
[12:03pm] froodian: so my guess is, he's not
[12:03pm] kreeger2: are we going to take his patch for 1.1
[12:03pm] kreeger2: ?
[12:04pm] kreeger2: or is that a trunk only thing?
[12:04pm] froodian: it's trunk only until some other pieces come together
[12:04pm] froodian: per smorgan
[12:04pm] froodian: and i agree
[12:04pm] ardissone: my guess is no
[12:04pm] froodian: alright, let's start
[12:04pm] ardissone: it needs way more testing that we can get at this point if we want 1.1 before 2007
[12:04pm] froodian: 1.1a1
[12:05pm] froodian: we were planning on releasing this week
[12:05pm] froodian: but a lot of the pieces aren't quite together
[12:05pm] froodian: there's been some progress
[12:05pm] froodian: but not enough imo
[12:05pm] ardissone: i think we need to be out before Fx2 or after Fx2 has died down
[12:05pm] kreeger2: sorry i have been busy
[12:06pm] froodian: when's Fx2?
[12:06pm] ardissone: dunno for sure
[12:06pm] ardissone: it's not on the ics anymore
[12:06pm] kreeger2: my guess is mid-october
[12:06pm] ardissone: it's very close
[12:06pm] kreeger2: granted the security scare might push it back
[12:07pm] froodian: i'd like to release before Fx2
[12:07pm] froodian: personally
[12:07pm] cl: that'd be nice, but is it realistic?
[12:07pm] kreeger2: are we just awaiting the kqueue patch and some popup UI things?
[12:07pm] ardissone: planet says 24 Oct
[12:07pm] ardissone: kreeger: more or less, yes
[12:07pm] froodian: yeah
[12:08pm] ardissone: any of the other "landing followup" bugs are also game
[12:08pm] froodian: there's other stuff, but it matters less
[12:08pm] ardissone: but popup UI is in the worst shape
[12:08pm] peepo joined the chat room.
[12:09pm] ardissone: kreeger: you hope to have kqueue ready fro review this weekend, right?
[12:09pm] kreeger2: yeah
[12:09pm] froodian: if Fx2 is 24 Oct, I think we should definitely be before that
[12:09pm] kreeger is now known as _kreeger.
[12:09pm] ardissone: let's shoot for next week and re-evaluate if needed
[12:09pm] froodian: sounds good to me
[12:10pm] ardissone: pinkerton: ^^^
[12:10pm] cl: when we say "release" are we talking about a1, or the final 1.1?
[12:10pm] ardissone: a1
[12:10pm] froodian: a1
[12:10pm] pinkerton: that's fine
[12:10pm] cl: because there's no way in hell we're getting a full version out before Fx2, is there?
[12:10pm] froodian: jesus no
[12:10pm] cl: ok, just making sre.
[12:10pm] cl: *sure
[12:10pm] froodian: ok, next
[12:10pm] ardissone: no, not with our 3 month break after 1.0 
[12:10pm] froodian: Core bugs
[12:10pm] froodian: take a very long time to get reviewed
[12:11pm] froodian: is there anything we can do to get more loving in that area?
[12:11pm] cl: 4 days? those examples don't look *that* bad to me?
[12:11pm] ardissone: specificially hwaara was concerned that Camino fixes for major Core-caused breakages take too long
[12:11pm] cl: we've waited longer than that for review on Camino patches (albeit not lately)
[12:12pm] ardissone: it also takes us too long to get patches ready for review in those cases 
[12:12pm] cl: mhm
[12:12pm] froodian: yeah, i think the problem is specifically when it's major breakage problems
[12:12pm] ardissone: right, with xpfe going away, for instance
[12:12pm] froodian: anyway, i don't think there are any "answers", it's just something we should be aware of
[12:12pm] ardissone: but other major trunk changes
[12:13pm] cl: right.
[12:13pm] froodian: next?
[12:13pm] cl: i'm all for updating the roadmap 
[12:13pm] froodian: http://www.caminobrowser.org/development/roadmap/ is a big fat liar 
[12:13pm] froodian: let's do it
[12:13pm] cl: make it so.
[12:13pm] froodian: somebody file a bug
[12:14pm] froodian: queues are doing pretty well
[12:14pm] ardissone: "Camino 1.1 is planned for 4th quarter 2006" 
[12:14pm] cl: well, that's still realistic. mostly.
[12:14pm] cl: if we get a1 out next week.
[12:14pm] cl: we could conceivably ship by the end of the year 
[12:14pm] kreeger2: ardissone: when is xpfe going away
[12:14pm] ardissone: kreeger2: slow death
[12:15pm] ardissone: but faster once SeaMokeuy 1.5 ships
[12:15pm] kreeger2: ok good
[12:15pm] ardissone: which will be soon0ish
[12:15pm] froodian: anybody have anything else before we move on to specific bugs?
[12:15pm] ardissone: we need to focus on fixing 1.1 (and a1) bugs
[12:16pm] froodian: yeah.  a1 specifically until it comes out
[12:16pm] ardissone: (unless it's mjr breakage, of course)
[12:16pm] ardissone: we fixed 8 bug last week, but only 3 were a1
[12:17pm] thebot joined the chat room.
[12:17pm] froodian:        bug 303193    
[12:17pm] thebot: froodian: Bug https://bugzilla.mozilla.org/show_bug.cgi?id=303193 enh, --, Camino1.1, nobody@mozilla.org, NEW, Make error pages look less like Windows and more like Camino/Aqua
[12:17pm] froodian: we should make a decision about bullets and land it
[12:17pm] ardissone: smfr and philippe didn't like the loss of bullets
[12:17pm] ardissone: i tend to agree
[12:17pm] froodian: personally, i think philippe's bullets look nice
[12:18pm] ardissone: url?
[12:18pm] froodian:        https://bugzilla.mozilla.org/attachment.cgi?id=240707&action=view    
[12:18pm] cl: i prefer that one as well
[12:19pm] ardissone: that still has the too-big spacing, right?
[12:19pm] froodian: uh, yeah
[12:19pm] cl: yeah
[12:19pm] ardissone: pinkerton: is that attachment ok, once we fix the spacing between sections?
[12:19pm] froodian: just between the bottom of the list and the button
[12:19pm] froodian: i think
[12:20pm] froodian: i think the spacing section would be like that, no?
[12:20pm] cl: and i prefer the bullets to the boxes
[12:20pm] ardissone: hicks made the section spacing really large when he killed the bullets
[12:20pm] froodian: ok
[12:20pm] ardissone: let me look at his css
[12:21pm] ardissone: yeah 1.5em vs 0.5 em in stock and 0.7em in hicks's last one with bullets
[12:21pm] pinkerton: shrugs, looks fine to me
[12:21pm] peepo left the chat room. (Quit: later)
[12:21pm] froodian: ok.  let's land it with reduced margins and spacing then?
[12:22pm] ardissone: yeah
[12:22pm] ardissone: and philippe's bullets
[12:22pm] froodian: yes
[12:22pm] cl: agreed
[12:22pm] froodian: ok.  bug 315340.  too bad that neither of the people who commented in the bug are here
[12:22pm] thebot: froodian: Bug https://bugzilla.mozilla.org/show_bug.cgi?id=315340 nor, --, ---, nobody@mozilla.org, NEW, show inline tooltip for fields that don't fit instead of dropped location as tooltip
[12:23pm] cl: I like the idea of that one better than the "always show a tooltip" idea.
[12:23pm] froodian: the only worry i have is that we'll need double the tracking rects
[12:23pm] froodian: right?
[12:23pm] froodian: so that we can have a url tooltip and a title tooltip
[12:23pm] cl: probably, but is that really as big a deal as smfr seems to think?
[12:23pm] froodian: dunno
[12:24pm] ardissone: do we have 2 right now, or only one for the entire row?
[12:24pm] froodian: one for the entire row
[12:24pm] ardissone: i tend to think that we want the inline version
[12:25pm] froodian: well, i'm not married to my patch, so i'd be ok w/ that
[12:25pm] froodian: though it seems to have caught on on the forae
[12:25pm] cl: also, I think we should *not* have tooltips (we currently do) for columns where you can see the entire thing
[12:25pm] cl: they're useless and they get in the way.
[12:25pm] ardissone: that's what this proposes, no?
[12:25pm] cl: yeah.
[12:25pm] cl: which is the other reason i'm heavily in favour of it
[12:25pm] froodian: i'm not sure it does
[12:26pm] cl: because it would allow us to get rid of the tooltips that hide stuff.
[12:26pm] froodian: it seems weird to have tooltips or not have tooltips based on column width and title length
[12:26pm] cl: for instance, a tooltip on the Location field for a bookmark folder is, well, silly.
[12:26pm] cl: at least, our current one is.
[12:26pm] cl: it's just the title of the folder. well, duh, i can see that!
[12:26pm] ardissone: that's the way finder list views work,tho
[12:27pm] ardissone: only tooltips when truncated
[12:27pm] froodian: so it does
[12:27pm] froodian: i guess i'm ok w/ it then
[12:28pm] froodian: alright, so inline tooltips for titles and urls, and only when the title/url has been truncated?
[12:28pm] cl: right.
[12:28pm] cl: how about for location/description?
[12:28pm] ardissone: pinkerton: ^^^
[12:28pm] cl: s/location/keyword
[12:28pm] froodian: pinkerton: this is in the bm manager
[12:28pm] kreeger2: lunch
[12:28pm] kreeger2 left the chat room. (Quit: Chatzilla 0.9.75 [Firefox 2.0/2006091818])
[12:29pm] pinkerton: what?
[12:29pm] _kreeger: nick kreeger-lunch
[12:29pm] _kreeger is now known as kreeger-lunch.
[12:29pm] ardissone: tooltips in the bookmarks manager
[12:29pm] ardissone: right now they're useless 
[12:29pm] ardissone: the proposal is inline tooltips for titles and urls, but only when the title/url has been truncated
[12:29pm] froodian: pinkerton: when in the bookmarks manager, when you mouseover an item, we want to have inline tooltips (instead of drop tooltips) for the title and url, and only when the title/url has been truncated (by column width)
[12:30pm] pinkerton: sounds fine to me, is that possible to implement in a cocoa tree?
[12:30pm] froodian: has no idea
[12:30pm] Pinolo left the chat room. (Ping timeout)
[12:30pm] froodian: the downside of this decision is that since we made it, the bug is no longer fixed 
[12:30pm] froodian: (or on its way to being fixed)
[12:31pm] ardissone: well,سهمsome enterprising soul can fix it at some point 
[12:31pm] cl: wonders where the random Arabic letters come from in Smokey's IRC text every so often
[12:31pm] ardissone: cmd-space 
[12:31pm] cl: heh
[12:31pm] ardissone: next bug then?
[12:31pm] froodian: ok, next
[12:32pm] froodian: i was going to ask about Bug 290212, but I don't think enough people who could shed brilliance on the subject are here
[12:32pm] ardissone:        bug 290212    
[12:32pm] thebot: ardissone: Bug https://bugzilla.mozilla.org/show_bug.cgi?id=290212 enh, --, Camino1.1, stridey@gmail.com, NEW, Implement bookmark folders' "Open in Tabs"/"Open in New Tabs" with alternate menu items
[12:32pm] cl: pinkerton, mento, smfr probably need to fight that out 
[12:32pm] ardissone: sooon, please 
[12:32pm] froodian: maybe.  maybe it just needs something really clever.
[12:32pm] cl: although...have we seen any big perf hits since the alternates for the bookmark menu landed?
[12:32pm] froodian: not that anybody has mentioned
[12:32pm] ardissone: no one's really complained
[12:32pm] cl: because that seems potentially a lot worse than what this bug is asking for
[12:33pm] ardissone: but i think our testing is too light
[12:33pm] ardissone: right now
[12:33pm] cl: and if that hasn't caused problems, i think we're probably OK with this one.
[12:33pm] ardissone: which is another reason for a1
[12:33pm] froodian: well, the problem isn't the alternates
[12:33pm] froodian: it's getting the text in them to update
[12:33pm] cl: what's the problem, then?
[12:33pm] cl: ah
[12:33pm] froodian: based on the tabs/windows pref
[12:34pm] froodian: personally, i see that as a very minor issue
[12:34pm] froodian: compared to the current one
[12:34pm] cl: have you tried Wevah's suggestion?
[12:34pm] ardissone: yeah
[12:34pm] froodian: yes
[12:34pm] froodian: it's no good
[12:34pm] cl: and it didn't work? shoot.
[12:34pm] froodian: fuck, that's who i didn't invite
[12:34pm] cl: yeah, but he's not there
[12:34pm] ardissone: I think i'd be ok with landing the fix and fixing the text later
[12:34pm] froodian: i'd be very ok with that
[12:34pm] froodian: i dunno about smorgan though
[12:34pm] ardissone: yeah....
[12:35pm] peeja left the chat room.
[12:35pm] cl: i don't have any brilliant ideas there either.
[12:36pm] ardissone: pinkerton: in Bug 290212, there's a regression where you have to hold down cmd before opening the menu to make it "open in NEW tabs"
[12:36pm] ardissone: can we go ahead and land the part of the fix that does that right now, and come back to fixing things so the text updates based on all our tab/window prefs?
[12:36pm] ardissone: ok, why am i seeing that now 
[12:36pm] pinkerton: sure
[12:36pm] ardissone: k
[12:37pm] ardissone: do we want to plug murph's bug for eyeballs, too?
[12:37pm] froodian: we should
[12:37pm] froodian:        bug 341967    
[12:37pm] ardissone: (we should also revisit the color bug for pink's benefit)
[12:37pm] murph: yeah, I have a few points I'd like to ask for opinions on..
[12:37pm] thebot: froodian: Bug https://bugzilla.mozilla.org/show_bug.cgi?id=341967 nor, --, Camino1.1, camino@seanmurph.com, ASSI, Popup blocker notification text doesn't wrap properly
[12:38pm] murph: I've been having a hell of a time with this one, but I should have a (non-hackish) solution pretty soon..
[12:38pm] murph: but
[12:38pm] froodian: specifically bug 341967 comment 10
[12:40pm] froodian: i think the best chance for that bug is to flag the patch you have (or the next iteration) to r?smorgan
[12:40pm] murph: when the window size gets to be a certain [very small] width, I think the text needs to stop wrapping (just like the Fx behavior)
[12:40pm] froodian: because he probably has solutions
[12:40pm] cl: don't we already have a minimum size for the window anyway?
[12:40pm] cl: hrm, guess not.
[12:40pm] murph: yeah, but it's a real small value
[12:41pm] froodian: i have a wild idea.  let's get rid of the text entirely, and just use an icon.  that way, it won't have to wrap.  Plus, we could put it somewhere where it didn't get in peoples' ways, like... um... i dunno...
[12:41pm] froodian: sorry, not helpful
[12:41pm] froodian:                           
[12:41pm] cl: lol
[12:41pm] cl: i second that idea.
[12:41pm] pinkerton: glares
[12:42pm] froodian: sorry
[12:42pm] froodian: hides
[12:42pm] cl is now known as userbase.
[12:42pm] userbase: glares back
[12:42pm] userbase is now known as cl.
[12:42pm] froodian: at this point, i'm just doing it to be snarky
[12:42pm] froodian: i apologize.  back to topic
[12:42pm] froodian: murph: i think that's totally reasonable
[12:42pm] pinkerton: i need food brb
[12:42pm] murph: ok..bc otherwise we'd end up wrapping into about 50 lines with one char each
[12:43pm] froodian: yeah, you have to draw the line somewhere
[12:43pm] cl: can someone take a screenshot of the wrapping behaviour with a window resized as small as it'll go?
[12:43pm] ardissone: what's reasonable? the width of the prefs window?
[12:43pm] cl: cause i'm curious to know just how bad it looks.
[12:43pm] murph: cl: yeah..i'll upload one now
[12:43pm] froodian: we must have at least a couple 800x600 users, right?
[12:44pm] ardissone: yeah
[12:44pm] froodian: prefs window is 595
[12:44pm] ardissone: prefs are 595
[12:44pm] froodian: that seems reasonable
[12:44pm] froodian: if you're browsing at that resolution, you'll be using as much of the screen as possible
[12:44pm] ardissone: we should also fix min-width on the browser window, too
[12:44pm] cl: hey, here's an idea...
[12:45pm] delliott joined the chat room.
[12:45pm] cl: instead of stopping the wrap at some magic number of pixels of width
[12:45pm] cl: can we continue to wrap, but insert a linebreak so the button(s) and text are on separate lines?
[12:45pm] ardissone: ew
[12:45pm] froodian: well, at a certain point you have more popup blocker than content pane
[12:45pm] murph: cl: https://bugzilla.mozilla.org/attachment.cgi?id=241186
[12:46pm] cl: yeah, see, that *does* look awful.
[12:46pm] ardissone: basically, we need to account for l10n and reasonably-small widths
[12:46pm] cl: but what if you stuck the buttons either above or below that message?
[12:46pm] murph: ignore the button's being off-centered in that, btw  
[12:46pm] cl: (probably below)
[12:47pm] ardissone: 278 is really too small
[12:47pm] murph: the funny part about fixing this bug is that popuptest.com probably never had so many hits in one week before I started working on this  
[12:47pm] cl: also, it occurs to me now (i probably should have said something before) that the "Tube" icon and the close widget seem to be two different visual representations of the same sort of idea, which makes me wonder if users are going to try to click the "Tube" icon and get some unexpectedly wrong behaviour (or nothing at all)
[12:47pm] ardissone: if there are popups throwing popups, that's just evil
[12:48pm] cl: ardissone: you've never browsed much pr0n with IE, have you? 
[12:48pm] ardissone: heh, no on both accounts
[12:49pm] ardissone: we could use the standard warning icon if that starts to be a problem, i guess
[12:49pm] cl: i think that might be better than introducing a new icon for an old concept.
[12:49pm] froodian: ok.  so, let's limit the wrapping width.  murph can figure out the details of exactly where the line is, but 595 sounds reasonable to me
[12:49pm] froodian: well, remember that we want to use this icon in the status bar
[12:50pm] ardissone: and then fix browserwindow to match
[12:50pm] ardissone: right
[12:50pm] froodian: if there's just a "warning" icon in the status bar, it doesn't mean anything
[12:50pm] froodian: i like the tube icon
[12:50pm] cl: i like it too, i just don't know that it's appropriate for this.
[12:50pm] murph: alright, 595 should work out fine..I will try to have this one fixed asap then
[12:51pm] froodian: i think having the close button be more visible will help
[12:51pm] froodian: which will prolly happen as part of the existing followups
[12:51pm] ardissone:        bug 355323    
[12:52pm] thebot: ardissone: Bug https://bugzilla.mozilla.org/show_bug.cgi?id=355323 nor, --, Camino1.1, nobody@mozilla.org, NEW, Fix followup issues with changing the color of the pop-up blocker bar
[12:52pm] froodian: (since the hover and mousdown state need to be more visible, and you can only get so much blacker, so the "standard" state will need to be lighter)
[12:52pm] kreeger-lunch is now known as kreeger.
[12:52pm] ardissone: i think we need to switch to a gradient
[12:52pm] ardissone: for the bgcolor
[12:52pm] murph: yeah, the pattern image assumes a fixed height at the moment
[12:53pm] ardissone: this one (i think) http://adggda.com/~ss/camino/mockups/popupblocker2-toned_down_blue.jpg
[12:53pm] cl: mhm
[12:54pm] ardissone: can be done as a gradient perhaps
[12:54pm] murph: and then we have the whole resolution independent migration, and using bitmapped images aren't always future-proof in this regard
[12:54pm] ardissone: yeah (although we're screwed already there)
[12:54pm] cl: can't we generate that gradient programmatically?
[12:55pm] ardissone: the one in that screenshot, or the current glassy one?
[12:55pm] cl: in the screenshot
[12:55pm] murph: cl: sure, with CoreGraphics or CoreImage (CI is 10.4+ only tho)
[12:55pm] ardissone: i think we should be able to generate toned_down_blue in code
[12:56pm] ardissone: i think that instead of trying to match the close icon's color, it should stay grey
[12:56pm] ardissone: which will help with people finding ti
[12:56pm] froodian: i agree
[12:56pm] froodian: especially if we're going with the blue
[12:56pm] murph: yeah, maybe make it's color more in-line with the aqua widgets accompanying it
[12:57pm] murph: since they are the three objects that can be clicked
[12:57pm] froodian: well, let's just keep it the way it is in the tabs
[12:57pm] froodian: since we already have a graphic that means "close this" to people
[12:57pm] murph: true..
[12:57pm] cl: mhm
[12:57pm] froodian: ok.  i have to go make a presentation in class
[12:57pm] froodian: hands ardissone the torch
[12:57pm] ardissone: now the question is, has pinkerton seen any of this or is he still at lunch?
[12:57pm] ardissone: thanks froodian 
[12:57pm] froodian is now known as froodian|class.
[12:58pm] ardissone: pinkerton: did you catch any of this discussion on the problems with the glassy black popup blocker bg?
[12:59pm] cl: fwiw, i think glassy black looks horribly out of place with the rest of the UI
[1:00pm] pinkerton: nope
[1:00pm] ardissone: bug 355323 gives a good summary
[1:00pm] pinkerton: waits for thebot
[1:01pm] ardissone:        https://bugzilla.mozilla.org/show_bug.cgi?id=355323    
[1:01pm] pinkerton: heh
[1:01pm] You are now known as ardissone|thebot.
[1:01pm] You are now known as ardissone.
[1:01pm] thebot: ardissone: Bug https://bugzilla.mozilla.org/show_bug.cgi?id=355323 nor, --, Camino1.1, nobody@mozilla.org, NEW, Fix followup issues with changing the color of the pop-up blocker bar
[1:01pm] pinkerton: js
[1:01pm] pinkerton: ha
[1:02pm] pinkerton: i don't recall the buttons looking out of place in the mockups
[1:02pm] ardissone: hwaara and smorgan both complained about that
[1:03pm] pinkerton: i c
[1:03pm] ardissone: they look "too suspened-in-air" or something; not sure how to describe
[1:04pm] ardissone: but the bigger problem really is with wrapping the text to accomodate l10n and smaller windows
[1:04pm] ardissone: we need something we can do in code rather than as an image
[1:04pm] ardissone: e.g., http://adggda.com/~ss/camino/mockups/popupblocker2-toned_down_blue.jpg
[1:05pm] cl: so what's the end result of the wrapping going to be if the window *is* resized below the 595-pixel threshold?
[1:05pm] cl: murph: can you post a screenshot of that once you have a working patch?
[1:05pm] cl: because if it's more of the current behaviour, that sucks ass.
[1:05pm] murph: cl: sure thing..
[1:06pm] murph: cl: if the window gets too small, and we back out of wrapping, the widgets would (right now) be clipped off-screen (which is what Fx2 does)
[1:06pm] ardissone: pinkerton: our consensus from this meeting discussion is go with a blue like that mockup that can be done in code and go back to the standard close button so it doesn't disappear
[1:07pm] pinkerton: ok
[1:07pm] cl: murph: that's better than what we're currently doing, i suppose.
[1:07pm] ardissone: ok
[1:07pm] cl: i still don't see why we can't wrap the two buttons onto a separate line
[1:07pm] murph: yeah, i don't really like having the close button clipped off-screen though
[1:07pm] cl: which seems like it would solve all the problems and avoid the issue of a magic-number threshold
[1:07pm] ardissone: anyone have anything else?
[1:07pm] cl: yeah, one quick thing
[1:07pm] cl:        bug 337958    
[1:08pm] thebot: cl: Bug https://bugzilla.mozilla.org/show_bug.cgi?id=337958 nor, --, Camino1.1, bugzilla@chrislawson.net, ASSI, Dragging folder/tab group from Bookmark Bar to tab strip should respect shift toggle
[1:08pm] cl: there is no comment 17 
[1:08pm] cl: i assume you meant comment 12.
[1:08pm] ardissone: smorgan's last comment
[1:08pm] ardissone: i was tired and my head hurt last night
[1:08pm] cl: heh
[1:09pm] cl: pinkerton, this is where you come in.
[1:09pm] cl: how is a class method different from what i've done already? 
[1:12pm] ardissone: not to cut off the answer, but anything else, or can we go and let cl wait alone? 
[1:13pm] ardissone: ok then...let's go out and fix a1 nominees and things for the popup blocker, and we'll try again to ship 1.1a1 next week
[1:13pm] ardissone: thanks everyone!
[1:14pm] cl: pinkerton: you can answer over in #camino
[1:14pm] cl: since i'm leaving this channel.
[1:14pm] cl left the chat room.
[1:14pm] murph: sounds good. see everyone later.. (and sorry my bug is taking a while)
[1:14pm] pinkerton left the chat room.
[1:15pm] delliott left the chat room.
[1:15pm] thebot: New build added to Mozilla1.8-SeaMonkey: Linux hoshi Depend (1.1) (status: Success).
[1:15pm] You kicked thebot from the chat room. (ardissone)
[1:15pm] murph left the chat room.
[1:15pm] kreeger left the chat room.