| === asac_ is now known as asac | ||
| Omega | the global menu doesn't work on fx 9 | 17:29 |
|---|---|---|
| chrisccoulson | Omega, it happens every time the version number is bumped | 17:50 |
| chrisccoulson | it will be fixed in the next build | 17:51 |
| Omega | chrisccoulson: thanks for the reply :) | 18:09 |
| === m_conley` is now known as m_conley | ||
| BUGabundo | Power Night o/ | 21:57 |
| JanC | does anybody know if most extensions "support" the latest firefox by now? | 22:08 |
| * JanC hates these quick updates | 22:08 | |
| BUGabundo | does this work for anyone? http://madebyevan.com/webgl-water/ | 22:09 |
| JanC | and I'm pretty sure this is gonna hurt Firefox's security reputation too... :-( | 22:09 |
| BUGabundo | chromium 15 chrashes | 22:09 |
| BUGabundo | and FF trunk complains of lacking a open gl lib | 22:10 |
| BUGabundo | JanC: all my addons are running in firefox trunk | 22:10 |
| BUGabundo | Installed: 9.0~a1~hg20110818r75479+nobinonly-0ubuntu1~umd1 | 22:10 |
| JanC | well, I have a lot of addons, and some of them are written by people in their free time, so they don't always have the time to keep up with 4-6 week "major" releases | 22:11 |
| JanC | I already had to replace one addon with another less-feature-full one because the author gave up :-( | 22:13 |
| BUGabundo | I'm sure it will happen more and more, if mozilla keeps changing API | 22:17 |
| === m_conley is now known as m_conley_away | ||
| micahg | JanC: it's every 6 weeks | 22:42 |
| micahg | and the changes are smaller | 22:42 |
| micahg | 99% of the major extensions are compatible with 6: https://addons.mozilla.org/en-US/firefox/compatibility/dashboard/6.0 | 22:43 |
| JanC | micahg: changes might be smaller, but "extensions" don't know that ;) | 22:44 |
| micahg | the extensions on AMO get an automatic bump if they're compatible | 22:45 |
| JanC | if they think they are compatible? | 22:45 |
| JanC | which is a workaround at best | 22:46 |
| micahg | no, if they're not using any APIs that changed | 22:46 |
| JanC | micahg: how do they test no APIs changed? | 22:46 |
| JanC | (APIs have changed accidentally) | 22:47 |
| micahg | JanC: http://blog.mozilla.com/addons/2011/04/19/add-on-compatibility-rapid-releases/ | 22:47 |
| JanC | they onkly test for what they think changed | 22:47 |
| JanC | and of course extensions that aren't on their site are left to scramble | 22:48 |
| micahg | yes, but authors get 12 weeks to test with | 22:49 |
| micahg | once the branch to aurora happens, the extensions can be ported to the new APIs | 22:49 |
| JanC | micahg: if the authors have the time... | 22:49 |
| micahg | and extension compatability shouldn't have anything to do with Firefox's security reputation | 22:51 |
| JanC | micahg: it has, when people delay upgrading because incompatibility problems | 22:52 |
| JanC | because of | 22:52 |
| micahg | well, compatibility on AMO was 95 or 98% on release day, it's getting better, I think 7 will see even more compatible on release day | 22:52 |
| JanC | I am delaying upgrading myself, and feel bad about it for security, but I got burned with the previous release (3 extensions that took a couple of days to a couple of weeks to "officially" become "compatible" + 1 extension that dropped out entirely) | 22:55 |
| BUGabundo | nite tech world | 23:33 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!