Possible to confuse open windows about IsMain status

[GoogleCodeExporter]

* I read everything above and have demonstrated this bug only occurs on
10.4Fx by testing against this official version of Firefox 4/up (not
applicable for startup failure) - SPECIFY VERSION YOU TESTED AGAINST:24

* Layout bugs MUST be tested against a system WITHOUT hardware
acceleration. Go to Help, Troubleshooting Information to see if your test
system is accelerated. If your test system IS accelerated, you must make
sure it is OFF, OR test on ANOTHER system that isn't. If this is NOT a
layout or display bug, you can skip this step.

* This is a startup crash or failure to start (Y/N):N

* This is a fault of JavaScript acceleration (Y/N):N (Use the steps above to
find out. Do NOT report if it is not.)

* What steps are necessary to reproduce the bug? These must be reasonably
reliable.
1. Start up T4F.
2. Click outside of the window.
3. Click back inside of the window.
4. Go to the File menu and click "New Private Window"

* Describe your processor, computer, operating system and any special
things about your environment.
It's an iBook G4 with 10.4.11. Nothing special except that my tabs are on the 
bottom.

* If this is a startup crash or failure to start, have you tried restarting
with a clean profile or in safe mode? Does this fix the problem?
N/A

* For crashes or startup failure (optional): paste in any information from
Crash Reporter, or if you are able to run 10.4Fx in gdb, paste in the
backtrace. You can often do it like this from within Terminal.app:

cd appname.app/Contents/MacOS
gdb firefox
run
*crash the app
bt full
N/A
* Include any useful additional information, steps you have tried, etc.:
Files showing the window both selected and unselected can be found here:
https://docs.google.com/file/d/0B_F1gyHiB4fdWGhkR0RJV3lQQ1k/edit?usp=sharing

Thanks for your help!

Original issue reported on code.google.com by Shicky...@gmail.com on 10 Oct 2013 at 12:26

[GoogleCodeExporter]

I see this, but even though it's ugly it's strictly cosmetic and this is not 
something that's likely to be fixed anytime soon (probably at least until 
Australis lands and we refactor the widget code anyway). Obviously, if you find 
the problem and a speculative fix, I'll certainly consider accepting it.

Issue 187 may be partially related.

Original comment by classi...@floodgap.com on 12 Oct 2013 at 7:56

• Changed title: Possible to confuse open windows about IsMain status
• Changed state: Accepted
• Added labels: Priority-Low

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

This has been fixed in Australis, so I am not likely to fix this in 24.

Original comment by classi...@floodgap.com on 30 Apr 2014 at 4:05

[GoogleCodeExporter]

Marking fixed, since this specific problem is repaired in 31. (Issue 247 makes 
it a little less pretty, but that isn't this issue.)

Original comment by classi...@floodgap.com on 25 May 2014 at 5:39

• Changed state: Fixed