[adam1185]

woo, no more dummy window when you use expose with firefox, unless i'm blind. Also they fixed the bookmarks bug so you can now import from a file! ...now to just get that scroll speed fixed

[MacGorilla]

Whats a dummy window?

[adam1185]

in older builds, when you wanted to have firefox still running but all windows closed, there was a small dummy window that was only visible when using expose. I guess it was just used as a cheap way to get around the fact that closing the window of an app in osx doesn't actually quit the app.

[adam1185]

one other nice feature i found, you can have links that normally open in a new window always open in a new tab. Finally someone implemented that type of feature!

[King Bob On The Cob]

Originally posted by adam1185:
one other nice feature i found, you can have links that normally open in a new window always open in a new tab. Finally someone implemented that type of feature!

Sorta like Saft has allowed Safari to do for awhile?

[adam1185]

that being an addon, this one being built into the app

[Krypton]

Where have you people been?!

[TETENAL]

Originally posted by adam1185:
woo, no more dummy window when you use expose with firefox, unless i'm blind.

I bet it still has the dummy window. Are all of these fixed:

• Exposé
• ⌥click in minimize window widget minimizes dummy window
• ⌘` through windows activates dummy window (all windows appear to be deactivated)

[nooon]

this is SO last week.

[adam1185]

Originally posted by TETENAL:
I bet it still has the dummy window. Are all of these fixed:

• Exposé
• ⌥click in minimize window widget minimizes dummy window
• ⌘` through windows activates dummy window (all windows appear to be deactivated)

no, it really is gone

[TETENAL]

Originally posted by adam1185:
no, it really is gone

You're right, it can't be revealed with the above methods any more. But if you look at the window list with Quartz Debug, you can see that there is still a 102x102 pixel window on screen at origin -32000/-31978. So it's not really gone.

[adam1185]

interesting, but at least I can't see it. Every other program has a ton of windows open according to quartz debug so i'm not too worried

[Thain Esh Kelch]

Originally posted by TETENAL:
You're right, it can't be revealed with the above methods any more. But if you look at the window list with Quartz Debug, you can see that there is still a 102x102 pixel window on screen at origin -32000/-31978. So it's not really gone.

Strange... How come expose doesnt trigger it anymore?

[TETENAL]

Originally posted by Thain Esh Kelch:
Strange... How come expose doesnt trigger it anymore?

Exposé only exposes windows in the document window layer. Windows in other layers fade away. There is also a private SPI to make windows not react to Exposé.

What they actually did you'd have to look up in the Firefox code.

[wataru]

Welcome to September 24.

[Mediaman_12]

This seams to come with a side-affect of not being able to quit the app (command Q or from the menu) unless the window is closed (in the latest build anyway). So not the total solution then.

[wataru]

Originally posted by Mediaman_12:
This seams to come with a side-affect of not being able to quit the app (command Q or from the menu) unless the window is closed (in the latest build anyway). So not the total solution then.

You mean unless the browser window is closed? I can assure you that that is not true.

[adam1185]

Originally posted by wataru:
You mean unless the browser window is closed? I can assure you that that is not true.

I'll second that

[Mediaman_12]

Originally posted by wataru:
You mean unless the browser window is closed? I can assure you that that is not true.

Sorry I thought that was implied, I forgot about the download window etc.

[wataru]

I didn't know if you meant the hidden window, which wouldn't make much sense, but you never know.

Anyway, sometimes Firefox is slow to quit for me too, but that has nothing to do with what windows are open.