The problem with that approach is that you can't cleanly close a sheet in
the general case. If it's our sheet then perhaps that'd work, but for
something like the save file sheet, there's no good way to convince it to
close that isn't more hacky than what I'm doing...

Avi

On Fri, May 8, 2009 at 12:44 PM, Scott Hess <[email protected]> wrote:

> I hate to suggest this, since it's sort of icky (*), but would it make
> sense to instead use regular old sheets, and save/restore state across
> tab switches?  I mean so that if the tab is not visible, there is no
> OS-level sheet, there's a state container somewhere in the tab which
> will be restored with the tab.  That should short-circuit a lot of
> funky interactions that are broken in places we cannot see them, at a
> cost of making some "for free" stuff not work (we'll have to manually
> manage those interactions).
>
> (*) I don't like icky, but icky where you own the code is preferable
> to icky where you're having to reverse-engineer someone else's code.
>
> -scott
>
>
> On Fri, May 8, 2009 at 11:20 AM, Avi Drissman <[email protected]> wrote:
> > On Thu, May 7, 2009 at 9:49 AM, Mark Mentovai <[email protected]> wrote:
> >>
> >> Hit "login", then play with Exposé.  The "show me my desktop" function
> >> leaves the sheet hanging; the "show me my app's windows" and "show me
> >> all windows" functions send the sheet offscreen.
> >
> > These are all fixed by the system in SL.
> > Unfortunately, everything else is broken in SL. Putting the sheet back
> > leaves it ignoring all mouse input, and when it's hidden the blurring
> effect
> > on the host window remains.
> > Urgh.
> > I've fiddled around with several approaches and gotten nowhere. I might
> end
> > up having to use that DTS incident after all...
> > Avi
> > > >
> >
>

--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: [email protected] 
View archives, change email options, or unsubscribe: 
    http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---

Reply via email to