232919, 639707, 654350, 654842, 665138, 667456, 668900, 673675, 677545, 685392, 688412, 688678, 689012, 703724, 708887, 714147, 714605, 725596, 726034, 738335, 739012, 740148, 741671, 742178, 752450, 807685, 836456, 636564, 638004, 639705, 643150, 645556, 647227, 647720, 648700, 649184, 651618, 654725, 655339, 656990, 660372, 661638, 663688, 664020, 666325, 667476, 667480, 668953, 670099, 670105, 670175, 670842, 670910, 671377, 672188, 672852, 673016, 673023, 673213, 673348, 673541, 673696, 673875, 674370, 674373, 674461, 674610, 674868, 675410, 677573, 677613, 678392, 678607, 678834, 678891, 679771, 683414, 686113, 686849, 687026, 690910, 693451, 694896, 695524, 698761, 700223, 704456, 708211, 708461, 709484, 714172, 715856, 716038, 717896, 723834, 733704, 738640, 738995, 752452, 753248, 758931, 773375, 780021, 785667, 836430, history-swipe
We should investigate compatibility with Mac OS X 10.7 "Lion". The developer preview is available now. We can use this as a tracking bug.
> The developer preview is available now. Where can you get it? I don't see it on ADC.
(In reply to comment #1) > > The developer preview is available now. > > Where can you get it? I don't see it on ADC. If you are enrolled in the Mac Developer Program (paid membership), there is a lion tab on this page: http://developer.apple.com/devcenter/mac/index.action
Thanks! Now I see it (I'd missed it before).
I've finally managed to download and install the Lion developer preview, and have started playing around with Java in it. You do need to install Java separately (using a download available from Apple's Developer Connection or Mac Developer Program). But once it was installed, I was amazed (and very pleased) to find that the JEP works just fine with Lion! I tested in FF 3.6.16, using the bundled JEP 0.9.7.4 and my newly released JEP 0.9.7.5. I normally have to make at least minor changes to the JEP to make it compatible with each new major release of OS X. This is the first time I haven't had to do so. Not surprisingly, Java also works fine in Safari. But it doesn't work in FF 4.0. I'll open a bug on that and make it block this one.
> You do need to install Java separately (using a download available > from Apple's Developer Connection or Mac Developer Program). The separate download is called "Java Web Components for Mac OS X 10.7". It's available to those who have accounts at Apple's Apple Developer Connection (log in at http://connect.apple.com/).
Are there any plans/concepts for updating the firefox theme for OS X Lion, or are there any bugs filed yet concerning this?
Are there any plans/concepts for updating the Firefox theme for OS X Lion, or are there any bugs filed yet concerning this?
> Are there any plans/concepts for updating the Firefox theme for OS X > Lion, or are there any bugs filed yet concerning this? Not that I'm aware of. Feel free to open one yourself (and make it block this bug). Be as explicit (and detailed) as possible about what you think it should contain. I can't promise we'll actually create a Lion theme -- I don't believe we've ever had an OS X-specific theme before. But there's a Gingerbread theme (for Fennec on Android), so the idea isn't entirely without precedent.
I believe Firefox should match the native UI-Theme. As Aqua has been updated for Lion I think Firefox should follow and incorporate those changes, as done in the past. This is just a quick mockup I made to illustrate what changes (I think) are necessary and how they could look like. Should I open a new tracking bug for the theme refresh, or just create the individual bugs and let them block this one? Or is the UI-Team already working on this?
> Should I open a new tracking bug for the theme refresh Please do. It's "component" should probably be "Firefox", and its "product" "Theme". Make it block this bug.
I've just added 668953, to add support for the new gestures that replace swiping backwards and forwards (that currently don't even work in Safari).
I do realize that this kind of post is most likely against the rules, and for that reason I will only post it once. By now it is most likely less than 20 days until Lion will be released. Even though a developer version of Lion has been out since February 24th (which is a very long time), work on creating a version of Firefox which is compatible, both functionality-wise and style-wise has just started. Where are all the people? Why isn't there at least 5-10 Mozilla employees working on this by now? An OS release isn't a small thing. There are some great people who have started working on this and who's doing a good job considering the circumstances, but they are still too few. At this rate, it'll be six months before it's at in an acceptable stage, and a year before it's on par with Safari. A lot of people will have bought Lion by then, and will find a version of Firefox which is incomplete and doesn't look like other applications. Users aren't forgiving in those aspects. I am not saying it has to have all the fancy features provided in the new OS from scratch, but shouldn't you as a user at least expect a version that fully works and looks like it's native environment? This post is a result of anger which has been growing inside me for a long time. I rarely, if ever, make this kind of post. Firefox means a lot to me, because it's managed by a company which cares about open-source. Not just for marketing purposes, as Mozilla stands up against proprietary standards and lock-in concepts. It isn't a surprise that Google Chrome is gaining ground while Mozilla is standing still. People have been complaining about memory leaks for years, yet just now, when Chrome is getting closer, a group to deal with the issue seriously has been formed. Please, do put priority on the right things. Having an unfinished product by the time of an OS release is terrible. There are fantastic people working on Mozilla, and contributing to the Firefox-project, but in this case they appear to have gone into hiding. Next time, be it Windows.next or a new version of Ubuntu, make sure you start as soon as you have access to developer builds.
Magne - You're right, this is definitely not the place for that kind of post. Acknowledging that you know what you're doing is wrong doesn't make it OK. https://bugzilla.mozilla.org/page.cgi?id=etiquette.html
Depends on: 643150, 647227, 647720, 649184, 655339, 660372, 664020, 665138, 666325, 667476, 667480, 668900, 670099, 670105, 670175, 670910, 671377, 672188, 672852, 673016, 673023
Summary: investigate compatibility with Mac OS X 10.7 "Lion" → (osx-lion-compatibility) investigate compatibility with Mac OS X 10.7 "Lion"
Depends on: 654350
Summary: (osx-lion-compatibility) investigate compatibility with Mac OS X 10.7 "Lion" → [10.7] (osx-lion-compatibility) investigate compatibility with Mac OS X 10.7 "Lion"
Summary: [10.7] (osx-lion-compatibility) investigate compatibility with Mac OS X 10.7 "Lion" → [10.7] Investigate compatibility with Mac OS X 10.7 "Lion"
Summary: [10.7] Investigate compatibility with Mac OS X 10.7 "Lion" → [10.7] Investigate compatibility with Mac OS X 10.7 "Lion" [meta]
Fwiw, I am setting up 10.7 testing machines in bug 693760. When that work is done, we will have unit tests and talos running for 10.7.
No longer depends on: 663691
You need to log in before you can comment on or make changes to this bug.