> "Say I have a GWT-powered eBook reader." That would be really cool :)
Ok, fair enough. Let's just leave it as is then. LGTM. On Wed, Jan 13, 2010 at 3:55 PM, Isaac Truett <itru...@gmail.com> wrote: > I like it except for one scenario: > > Say I have a GWT-powered eBook reader. I hide some navigation controls > in the corner; mouse over and they pop up. I want them to disappear if > you click outside the popup, so auto-hide=true. But If you click "next > page" I want to set a history token (for the next page) and I want the > controls to stay visible so that you don't have to mouse back over the > trigger in the corner in order to flip the page again, or flip back. > If auto-hide-on-click implied auto-hide-on-history then you would have > to jump through some more hoops (keep track of the popup state and > re-show after history change if it was visible before). > > > On Wed, Jan 13, 2010 at 3:43 PM, <j...@google.com> wrote: > > An idea: What if we just considered "auto-hide on history" to be > > equivalent to "auto-hide"? I definitely see that we can't hide *all* > > popups on history events, but ones mark auto-hide seem like fair game. > > What do you think? > > > > http://gwt-code-reviews.appspot.com/132804 > > > > -- > > http://groups.google.com/group/Google-Web-Toolkit-Contributors > > > > -- > http://groups.google.com/group/Google-Web-Toolkit-Contributors >
-- http://groups.google.com/group/Google-Web-Toolkit-Contributors
