[Tickets #10810] Re: New message hangs with "Loading..."

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/10810
------------------------------------------------------------------------------
  Ticket             | 10810
  Updated By         | Michael Rubinsky <mrubinsk at horde.org>
  Summary            | New message hangs with "Loading..."
  Queue              | Kronolith
  Version            | Git master
  Type               | Bug
  State              | Resolved
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             | Jan Schneider
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2012-09-03 23:09) wrote:

> Changes have been made in Git (FRAMEWORK_4):

>     I still don't get the permission request from Chrome though.  
> Does it work for anybody?

Desktop Notifications in Chrome can only be initially authorized as  
the result of an explicit user action like E.g., in response to  
onClick.  In Safari they do not have this limitation. The only way you  
can (currently) get this to work in Chrome is to enable all  
notifications or manually type the js code in the location bar as a  
"javascript:" url (typing in js console will not work).

We need to add a button in the user prefs for Chrome users to  
explicitly click to enable desktop notifications.