My favorites | Sign in
Project Home Downloads Wiki Issues Code Search
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 56764: Regression - Desktop Notifications only receives keyboard events when its browser window has the focus
24 people starred this issue and may be notified of changes. Back to list
 
Reported by phistuck, Sep 24, 2010
Chrome Version       : 7.0.517.8 dev

What steps will reproduce the problem?
1. Create a desktop notification with an input field and make it show up.
2. Type "I can see me typing." in the input field of the desktop notification.
3. See "I can see me typing" being typed in the input field of the desktop notification.
4. Delete what you typed.
5. Focus on a different window (Windows Explorer, Google Talk, a Google Chrome window with a different profile - everything but the current browser profile, Notepad).
6. Focus on the input field.
7. Type "Can you see me typing?".

What is the expected result?
The text will show up in the input field of the desktop notification.

What happens instead?
If you focus Notepad, it will get this input and you will see "Can you see me typing?" being typed in Notepad.

Code sample (execute it in the Omnibox) -
javascript:webkitNotifications.requestPermission(function(){webkitNotifications.createHTMLNotification("data:text/html,<!DOCTYPE HTML><html><body>Drag me<br/><input/></body></html>").show()});
Sep 24, 2010
#1 phist...@chromium.org
(No comment was entered for this change.)
Status: Untriaged
Labels: -Area-Undefined Area-UI Area-WebKit Feature-Notifications Regression WebKit-Core Mstone-7
Oct 2, 2010
#2 dglazkov@chromium.org
John, can you look into this?  Adjust priority/mstone if needed.
Status: Assigned
Owner: john...@chromium.org
Oct 2, 2010
#3 john...@chromium.org
Are you sure this worked before?  There are known issues with inputs in notifications, which are slated for m8.
Labels: -Regression -Mstone-7 Mstone-8
Oct 2, 2010
#4 phistuck
John, I am sure this has worked before. It was fine before, there were other issues, but this specific issue - it was not happening before.
Oct 2, 2010
#5 john...@chromium.org
Does it work in 6.0?  I can't think of anything that changed in this area for M7, but I will look.
Oct 2, 2010
#6 phistuck
I can reproduce it on 6 as well, but it was fine before...
Oct 19, 2010
#7 lafo...@chromium.org
Since we are passed the branch, moving all mstone-8 issues to mstone-9 for triage/punting
Labels: -Mstone-8 Mstone-9
Oct 22, 2010
#8 lafo...@chromium.org
Moving all P2 bugs w/ owners into Mstone-10.  I'll leave this to the owners discretion if they want to move the work back into M9, however, my caveat would be that the priority should be on completing P0/P1 bugs in the span of the next few weeks.
Labels: Mstone-10
Dec 9, 2010
#9 kerz@chromium.org
P2 bugs with an owner that are not marked as started are being automatically moved to mstone:11.
Labels: -Mstone-10 MovedFrom-10 Mstone-11
Feb 1, 2011
#10 ldsfutbo...@gmail.com
Desktop notifications launched by extensions (with input fields), exhibit similar behavior. A chrome window needs focus, and then the desktop notification needs focus before the input box can be typed into.

Desktop notification input box shows focus (orange outline), but typing will go to whatever program/window has focus, not the desktop notification.
Mar 9, 2011
#11 kar...@google.com
rolling non releaseblocker mstone 11 bugs to mstone 12. 
Labels: -Mstone-11 MovedFrom-11 Mstone-12
Apr 25, 2011
#12 kerz@google.com
Moving out of M12.
Labels: -Mstone-12 Mstone-13 MovedFrom12
May 18, 2011
#13 CalebEgg
On both Mac and Linux, this doesn't even work if the browser window is focused. The notification's form elements are basically unfocusable.
Labels: OS-All
May 19, 2011
#14 flashki...@gmail.com
I'm not sure how user-friendly this method is. But, as a replacement, I just created a window that auto-refocuses itself, positions and sizes itself just like a notification. It's worked out really well, almost no functionality lost.
May 23, 2011
#15 ehrlich....@gmail.com
I'm starting to get a lot of complaints about this issue (I use desktop notifications as an important part of a chrome extension). Is there some way to fix/bypass this without reimplementing the entire notification system?

I've tried having the parent window automatically refocus itself (seems to be required by this bug), but then I can't get the notification to regain focus for typing. 
Jun 2, 2011
#16 lafo...@chromium.org
Moving !type=meta|regression and !releaseblocker to next mstone
Labels: -Mstone-13 Mstone-14 MovedFrom13
Jun 2, 2011
#17 evan@chromium.org
Ping.  Someone from the gmail team says this might be blocking them.
Jun 2, 2011
#18 ldsfutbo...@gmail.com
This becomes more problematic with the new "background" permission for extensions. Notifications created by an extension with no windows active creates an unfocusable desktop notification.
Jun 2, 2011
#19 lafo...@chromium.org
(No comment was entered for this change.)
Labels: -MovedFrom12 MovedFrom-12
Jun 9, 2011
#20 tessa...@chromium.org
Is anyone working on this?
Cc: dglazkov@chromium.org
Jul 27, 2011
#21 kerz@google.com
Punting out non-critical bugs.  Please move back to 14 if you believe this was done in error.
Labels: -Mstone-14 Mstone-15 MovedFrom-14
Sep 8, 2011
#22 kar...@google.com
moving non-essential bugs from 15 to 16. Please feel free to move back if this is an error and your bug is a blocker for 15.
Labels: Mstone-16 MovedFrom15 bulkmove
Oct 24, 2011
#23 lafo...@google.com
(No comment was entered for this change.)
Labels: -Mstone-16 MovedFrom-16 Mstone-17
Dec 19, 2011
#24 kerz@google.com
Moving bugs marked as Assigned but not blockers from M17 to M18.  Please move back if you think this is a blocker, and add the ReleaseBlock-Stable label.  If you're able.
Labels: -Mstone-17 Mstone-18 MovedFrom-17
Jan 19, 2012
#25 mihaip@chromium.org
 Issue 108891  has been merged into this issue.
Cc: john...@chromium.org
Feb 7, 2012
#26 kar...@google.com
(No comment was entered for this change.)
Labels: MovedFrom18 Mstone-19
Mar 27, 2012
#27 lafo...@google.com
(No comment was entered for this change.)
Labels: -Mstone-19 Mstone-20 MovedFrom-19
Apr 27, 2012
#28 kerz@google.com
These bugs have hit their limit of moves to new milestones.  Please retarget when appropriate.
Labels: -Mstone-20 MovedFrom-20
Mar 10, 2013
#29 bugdro...@chromium.org
(No comment was entered for this change.)
Labels: -Area-UI -Area-WebKit -Feature-Notifications -WebKit-Core Cr-UI-Notifications Cr-Content Cr-UI Cr-Content-Core
Apr 5, 2013
#30 bugdro...@chromium.org
(No comment was entered for this change.)
Labels: -Cr-Content Cr-Blink
Apr 16, 2013
#31 Marvin.O...@googlemail.com
Any workaround yet ? 
Jul 17, 2013
#32 som...@chromium.org
createHTMLNotification has been deprecated. Please use the rich notifications API (http://developer.chrome.com/apps/notifications.html) for creating notifications. 
Status: WontFix
Sign in to add a comment

Powered by Google Project Hosting