[00:01] jcastro, not sure exactly where it is in the code. http://src.chromium.org/svn/trunk/src/chrome/browser/notifications/ comes to mind [00:01] but i could be wrong [00:03] chrisccoulson: firefox-dev contains "debug symbols". really? ;) [00:03] lol [00:03] yes, it's just to confuse you ;) [00:04] :) [00:10] jcastro, cocoa code: http://src.chromium.org/svn/trunk/src/chrome/browser/ui/cocoa/dock_icon.h & http://src.chromium.org/svn/trunk/src/chrome/browser/ui/cocoa/dock_icon.mm [00:14] chrisccoulson, if you feel like patching chromium for unity... [00:15] fta - thanks [01:00] chrisccoulson: BTW, there's bug 533038 for the man page [01:00] Launchpad bug 533038 in firefox "firefox 3.6 needs a man page" [Wishlist,Triaged] https://launchpad.net/bugs/533038 [01:06] micahg, oh, i didn't see that [01:08] chrisccoulson: BTW, I think there should be an announcement about the death of abrowser so people are aware when they are merging they can drop that diff === asac_ is now known as asac [05:27] fta: did you see this? http://packages.debian.org/changelogs/pool/main/c/chromium-browser/current/changelog#versionversion9.0.597.83_r72435-1 [09:25] micahg, nope, thanks [10:00] dpm, http://ftagada.wordpress.com/2011/02/10/chromium-translations-explained-part-2b/ [11:24] hi fta, sorry I was on a call. Reading... [11:34] fta, wow, excellent post! [11:34] I love the diagrams [11:35] :) [11:35] and again, thanks a lot for the work you've put in workarounding LP's limitations [11:51] dpm, but it looks like a Rube Goldberg machine now [11:51] dpm, http://en.wikipedia.org/wiki/Rube_Goldberg_machine [11:52] lol [11:54] I think on the next diagrams you should also add the part that "(C) [...] throws cracker (D) past parrot (E). Parrot jumps after cracker and perch (F) tilts, upsetting seeds (G) into pail" [11:56] yeah === m_conley_away is now known as m_conley [16:05] jdstrand, the firefox and thunderbird respins are building btw [16:06] jdstrand, i'm still not sure what we're going to do about lucid being frozen :/ [16:12] heh, i've DoS's all the i386 builders! [16:12] https://launchpad.net/builders [16:14] chrisccoulson: i'll check if we can push on 2/14 or have to wait until the 17th [16:14] chrisccoulson: we definitely cannot get in the point release unless they need a respin [16:14] err, probably not even then though [16:14] oh, i don't care about making the point release ;) [16:14] i just want us to be able to publish it [16:15] chrisccoulson: ok, I'll check with teh release team [16:15] thanks [16:25] chrisccoulson: thanks [16:25] normally we have not been asked to delay a security update for a point release [16:26] we upload and they can choose to pull in the new bits [16:26] it would be worth bringing up though, as micahg suggested [16:30] it's very odd timing this time out I think [16:35] chrisccoulson, last week, i DoSed almost all builders (official & ppa) when my 4 ch branches were bumped at the same time [16:49] chrisccoulson: ping [16:53] hi m_conley [16:54] chrisccoulson: hey - so I'm working on getting the globalmenu to open the first menu item when F10 is pressed... [16:54] ah, cool [16:55] chrisccoulson: and I've captured the F10 keypress event, and I'm wondering what you think would be the cleanest, most efficient way of determining what the first open-able menu item would be - should we precompute and hold a pointer to this menu item, and then refresh this if the content changes? [16:55] chrisccoulson: or is there a cleaner way? [16:57] m_conley, i'm not too sure. it's pretty quick to just do mMenuObjects[0]->OpenMenu() from the menu bar isn't it? [16:57] it is - but can we guarantee that this first item is open-able? [16:57] i think that would work [16:57] ah, good question. in most cases, i suspect it is, but you probably only want to open the first visible and sensitive item [16:57] mmhmm. [16:58] i've just thought actually, OpenMenu already doesn't check if the menu is sensitive or not ;) [16:58] that probably needs fixing [16:58] whoops, yep it does. [16:58] i bet if you use keyboard shortcuts now, you can open menus that you can't open with the mouse ;) [16:59] chrisccoulson: awesome hacks, but weird UX. :p [16:59] chrisccoulson: ok, so that sounds like a separate issue though - OpenMenu needs to ensure that menus are visible and sensitive. [17:00] chrisccoulson: but for determining the first one...precompute and reupdate, or just iterate each time F10 is pressed? [17:00] i think i'd just iterate over the menus and find the first one that can be opened when someone presses F10 [17:00] it shouldn't be that expensive [17:01] chrisccoulson: okie doke, will do. I'll file the bug for the OpenMenu problem. [17:01] thanks [17:13] chrisccoulson: fun fact - gEdit opens the file menu after F10 even if the menu is hidden and insensitive. [17:13] chrisccoulson: btw, here's a neat tool if you've ever wanted a Firebug for GTK apps: http://chipx86.github.com/gtkparasite/ [17:13] m_conley, heh, nice :) [17:14] chrisccoulson: hm. If gEdit does it, maybe we can afford to ignore the invisible/insensitive case? What do you think? [17:15] m_conley, i think we should take the opportunity to do it better than gedit ;) [17:15] chrisccoulson: sold. [17:15] chrisccoulson: should have a patch later today. :) [17:15] and probably report a bug against appmenu-gtk, which i think is probably responsible for that behaviour in gedit [17:15] i'm not too sure though, it might even be a gedit bug [17:15] or a gtk bug ;) [17:16] chrisccoulson: hrm. who should I report it to then? [17:17] m_conley, don't worry about it too much just yet, i'll try and figure out where it should go later [17:17] chrisccoulson: alright. [17:24] anyone using a non-english desktop here? (and chromium) [18:58] chrisccoulson, http://ubuntuforums.org/showthread.php?p=10445698 [19:05] jdstrand: I assume you want the SM updates all at once? [19:06] micahg: that is fine, but not a requirement [19:07] jdstrand: ok, I'm hoping to have at least maverick by EOD, these VMs are taking a long time (PATA drives, old machine) [19:09] micahg: cool, thanks [19:31] chrisccoulson: wasn't the tee surface support check supposed to happen upstream? [19:31] micahg - yeah, but the build just fails if it's not there ;) [19:31] i'd rather detect it before we try to configure it [19:32] ah, yeah, makes sense [19:43] chrisccoulson: so, we get to publish to at least -security for the Mozilla updates [20:01] mdeslaur: we've got some reports of flash not working after the update to 10.2, but it works for me [20:04] micahg: they can send patches :) [20:04] heh [20:04] micahg: seriously...have bugs been filed? [20:04] bug 716311 [20:04] Launchpad bug 716311 in flashplugin-nonfree "flash not installed" [Undecided,New] https://launchpad.net/bugs/716311 [20:05] hmm [20:07] micahg, yeah, i just saw that. thanks! [20:07] i hope these builds are actually ready by monday :/ [20:07] they seem to be taking ages [20:09] mdeslaur: there's also 716640, but idk if that's Chromium or Flash, I was watching some stuff with the Chromium daily earlier with no issues [20:09] bug 716640 [20:09] Launchpad bug 716640 in chromium-browser "Shockwave Flash plugin crash" [Undecided,New] https://launchpad.net/bugs/716640 [20:10] micahg: not much I can do about 716640 [20:10] chrisccoulson: seems like all the armel builders are offline [20:12] that sucks :( [20:13] m'eh, we're not going to get these tested before the weekend :( [20:13] i should have uploaded them earlier ;) [20:14] chrisccoulson: well, if they're still waiting for testing, I'll do it Tuesday :) [20:14] what's the release date? [20:14] if I ever get my VMs in stalled :-/ [20:14] 2/14 unless there are more issues [20:15] i might try and test them if i can tomorrow [20:15] chrisccoulson: I guess I can do it over the weekend if it's critical [20:15] i don't think we'll know that until monday [20:16] chrisccoulson: ah, armel builders back :) [20:16] oh, cool [20:16] now i just need someone to score all my builds! [20:16] j/k ;) [20:16] they fear lamont apparently :) [20:17] oh, cool. all the builds running on armel are mine anyway [20:17] that's good! [20:35] bdrung: what are you bumping the maxversion to in FF extensions in Debian now? [20:52] micahg: 4.0.* [20:53] bdrung: thanks, what I thought, thanks [20:53] chrisccoulson, not good! [20:53] chrisccoulson, your USE_SYSTEM_CAIRO will run on my h/w [20:54] fta - oh, does that cause a problem? [20:54] hold on, it's in a DEB_DEBUG block [20:54] should be ok then [20:55] bdrung, are you just bumping maxversion or porting them so that they don't break? [20:56] fta - i think it will still run :/ [20:57] i obviously don't have those headers when the bot runs [20:57] chrisccoulson: I'm going to switch mozvoikko to build with firefox-dev, ok? [20:58] fta- that's ok, it doesn't matter if that fails when the bot runs [20:58] it's only really needed when the pre-build target runs [20:59] micahg, i don't mind. if it works, then cool :) [20:59] chrisccoulson: well, it's in main, so we'll have to do it eventually to drop xulrunner [21:02] chrisccoulson: just bumping the version and test if they work. [21:02] some work, others not [21:02] hmmm, we have tee surface support in cairo now, but we don't install the header :/ [21:03] micahg - i guess i'll have to create another pkgconfig file for mozvoikko [21:03] possibly ;) [21:04] i've only provided one that supports building plugins so far [21:04] is prism dead upstream? [21:04] bdrung, i corrected the firefox-dev package description btw. it no longer contains debug symbols ;) [21:04] fta - it's been renamed [21:04] seems like it is [21:05] well, i think it was renamed [21:05] http://mozillalabs.com/projects/ says it's inactive [21:05] chrisccoulson: not exactly renamed, superceded is more like it [21:05] micahg - yeah, i couldn't remember [21:05] fta: you can stop building the dailies for it [21:05] and i don't have the link now [21:06] I still have to have a discussion with upstream about migration paths [21:06] we're going to run into problems when xulrunner gets upgraded in Lucid and Mavericdk [21:06] *maverick [21:08] http://mozillalabs.com/chromeless/ that was it wasn't it? [21:09] yep [21:09] fta^^ [21:13] w00t, firefox will be lintian clean soon [21:13] although [21:13] i cheated a bit === m_conley is now known as m_conley_away [22:32] chrisccoulson: do you know the current status of notify-osd in ff 4.0? [22:33] well, firefox doesn't have anything to do with notify-osd (which is just an implementation of the notification spec) [22:33] firefox can use libnotify [22:33] but notify-osd doesn't support actions, so it's useless for firefox [22:34] chrisccoulson: there was xul-ext-notify that sends the notifications to notify-osd [22:34] right [22:34] people can still use that, but we wouldn't want that by default [22:34] but it doesn't seam to work with ff 4 [22:34] what we want by default is integration with the unity launcher, which i'm going to be working on [22:34] i don't get any notifications at all [22:35] yeah, a lot of extensions that used to work, won't work any more [22:35] if it doesn't have a maintainer, you'll need to port it ;) [22:36] bdrung: is seems to have disappeared upstream [22:37] i want to make use of the launcher for doing progress indication, and quicklists for access to finished downloads [22:37] not sure how that will work out though, i need to talk to the design people really [22:37] and the same for chromium ;) [22:37] and then we could use notify-osd for notifications as well [22:38] but notify-osd on it;s own is a half-baked solution [22:39] * chrisccoulson needs to start hacking on that [22:39] sorry to jump in, but what about those who prefer "Classic Desktop" or where "unity" doesn't work? [22:40] then they will get the current experience [22:40] which is? [22:41] firefox has a download window, which flashes on the titlebar when your download finishes [22:41] nothing. it get neither any progress bar, nor a notification that the download finished [22:41] (configuration: do not open download window) [22:41] then that's a user choice, but it's not the default [22:42] yes, but in ff 3.6 i got a notification when the download finished and the status bar showed the progress [22:42] I've configured firefox to open a download window again for that reason; to get at least some notification when downloads are done [22:43] but I find it suboptimal as it's an other window when using alt+tab to switch between windows/applications [22:44] chrisccoulson: we have some people that want to test Firefox 4 on ARM on maverick, I'm trying to think of various options, (backports with renamed source, security PPA with renamed source, get a native PPA for various stuff next week), any ideas? [22:45] micahg - they could just use the natty build [22:45] I liked xul-ext-notify but the upstream seems dead [22:45] i think it should run fine [22:45] that was to micahg ;) [22:45] chrisccoulson: on maverick? that doesn't sound like it should work, different versions of X libs [22:45] I can suggest it though [22:45] micahg - X libs are ABI stable ;) [22:46] the ABI hasn't changed for many years [22:46] oh, right, firefox uses internal copies for most things...I keep forgetting, that sounds like that best solution :), thanks chrisccoulson [22:46] i can't think of a reason why it wouldn't work, but i could be wrong ;) [22:46] i wish we just shipped a single build of firefox across all of our releases ;) [22:47] upstream manage to provide binaries that work on distro's from the last several years [22:54] geser / bdrung - you could fix xul-ext-notify if it's got no maintainer ;) [22:58] I could try if I would know something about firefox addon programming [23:01] geser - do you get any errors in the error console when it runs? [23:01] that's normally a good starting point [23:01] in any case, i could probably help, but i have a limited amount of time [23:04] first I have to convice it, that it might work with FF 4.0b11 (currently firefox display it as disabled) [23:04] geser: nightly tester tools can fix that [23:05] where do I get it? addons.mozilla.org? [23:05] geser: I think so [23:06] there we go [23:06] it is using nsIExtensionManager, which has gone away in firefox 4 [23:06] geser: modify the maxversion in install.xpi to 4.0.* [23:06] that's why it doesn't work ;) [23:07] it's using nsIExtensionManager to discover it's install location, so it can run the python helper [23:07] that will show up in the error console too [23:14] I see many JS errors in the error log [23:15] i could probably make it work, but it wouldn't be high on my list of priorities :/