Comment #8 on issue 9233 by [email protected]: Need new, alternative
first-run bubble
http://code.google.com/p/chromium/issues/detail?id=9233
Sorry, my previous message was written without having read your original
message
fully.
I'm concerned about the fact that we're basically throwing a modal dialog
at the user,
especially if we're going to be throwing a second one up for default
browser on their
second launch - that's two first-impression launches where we're blocking
the user
from getting to what they want. This super sucks for the Nth-setup case.
Can we just disable the dismiss-on-blur behavior if the window just gained
focus? ie
start the 'block dismiss' timer only after the window gains focus, and only
allow
dismiss after that timer has expired.
Attached is a mock - the padding around the text is intentional to help the
bubble
content stick out from the page content. There's no X because I'm assuming
we have
blur-dismiss behavior described above (though maybe it's still necessary,
depending on
the timeout).
Attachments:
search_bubble.png 117 KB
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---
