Last Comment Bug 636455 - (lion-compatibility) [10.7] Investigate compatibility with Mac OS X 10.7 "Lion" [meta]
(lion-compatibility)
: [10.7] Investigate compatibility with Mac OS X 10.7 "Lion" [meta]
Status: NEW
: meta
Product: Core
Classification: Components
Component: General (show other bugs)
: Trunk
: x86 Mac OS X
: -- normal with 67 votes (vote)
: ---
Assigned To: Nobody; OK to take it and work on it
:
Mentors:
Depends on: 232919 639707 647720 649184 654350 654842 665138 667456 668900 673675 674371 676852 677545 683414 685392 688412 688678 688990 689012 690910 695524 703724 708211 708461 708887 714147 714605 716038 725596 726034 733704 738335 739012 740148 741671 742178 752450 780021 807685 836456 history-swipe 636564 638004 639705 643150 645556 647227 648700 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 686113 686849 687026 693451 694896 698761 700223 704456 709484 714172 715856 717896 723834 738640 738995 752452 753248 758931 766106 773375 785667 836430
Blocks:
  Show dependency treegraph
 
Reported: 2011-02-24 08:05 PST by Josh Aas
Modified: 2016-03-29 09:50 PDT (History)
71 users (show)
See Also:
Crash Signature:
(edit)
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---


Attachments
Mockup of OS X Theme Refresh for Lion (270.14 KB, image/jpeg)
2011-06-26 06:28 PDT, Dominic Spitaler
no flags Details

Description Josh Aas 2011-02-24 08:05:34 PST
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.
Comment 1 Steven Michaud [:smichaud] (Retired) 2011-02-24 09:44:19 PST
> The developer preview is available now.

Where can you get it?  I don't see it on ADC.
Comment 2 Scott Greenlay [:sgreenlay] 2011-02-24 09:47:06 PST
(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
Comment 3 Steven Michaud [:smichaud] (Retired) 2011-02-24 10:28:29 PST
Thanks!  Now I see it (I'd missed it before).
Comment 4 Steven Michaud [:smichaud] (Retired) 2011-03-27 14:00:41 PDT
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.
Comment 5 Steven Michaud [:smichaud] (Retired) 2011-03-27 14:31:04 PDT
> 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/).
Comment 6 Dominic Spitaler 2011-06-25 12:54:58 PDT
Are there any plans/concepts for updating the firefox theme for OS X Lion, or are there any bugs filed yet concerning this?
Comment 7 Dominic Spitaler 2011-06-25 12:55:27 PDT
Are there any plans/concepts for updating the Firefox theme for OS X Lion, or are there any bugs filed yet concerning this?
Comment 8 Steven Michaud [:smichaud] (Retired) 2011-06-25 14:09:17 PDT
> 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.
Comment 9 Dominic Spitaler 2011-06-26 06:28:02 PDT
Created attachment 542014 [details]
Mockup of OS X Theme Refresh for Lion

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?
Comment 10 Steven Michaud [:smichaud] (Retired) 2011-06-26 08:55:48 PDT
> 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.
Comment 11 Sam Illingworth 2011-07-01 23:17:02 PDT
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).
Comment 12 d 2011-07-04 13:16:24 PDT
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.
Comment 13 Josh Aas 2011-07-06 07:41:49 PDT
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
Comment 14 John Ford [:jhford] 2011-10-24 12:38:31 PDT
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.

Note You need to log in before you can comment on or make changes to this bug.