On Sat, Aug 30, 2014 at 2:46 AM, bindar robertbin...@gmail.com wrote:
I have read the spec again and I could not see any information regarding the
actions a replacing notification should trigger. Firefox OS for instance
triggers these actions every time.
Do you mean the Notifications API? As
On 09/06/2014 03:02 AM, Anne van Kesteren wrote:
Do you mean the Notifications API? As with most standards we're not
really touching the UI space at the moment.
That's what I meant. I filed an issue on the github page for that
https://github.com/whatwg/notifications/issues/24.
Robert
On Sat, Sep 6, 2014 at 7:15 PM, Robert Bindar robertbin...@gmail.com wrote:
That's what I meant. I filed an issue on the github page for that
https://github.com/whatwg/notifications/issues/24.
Thanks. As I mentioned earlier I'm not sure when exactly I'll get
around this. If something is urgent
On 08/13/2014 04:36 PM, Jonas Sicking wrote:
On Wed, Aug 13, 2014 at 2:12 PM, Robert Bindar robertbin...@gmail.com wrote:
Concerning web notifications, it would be very helpful for content and web
apps
to have a way of specifying the behavior their notifications should have.
For instance, a
On Fri, Aug 29, 2014 at 9:18 AM, Robert Bindar robertbin...@gmail.com wrote:
My thought is to firstly introduce a small package of behaviors that
would include lights, vibration and disrupting
(and maybe noclear too).
The default value for all these 3 behaviors is false.
I don't think we'll
Jonas Sicking wrote:
On Fri, Aug 29, 2014 at 9:18 AM, Robert Bindar robertbin...@gmail.com
wrote: My thought is to firstly introduce a small package of behaviors that
would include lights, vibration and disrupting
(and maybe noclear too).
The default value for all these 3 behaviors is
Den 15-08-2014 kl. 01:54 skrev Michael Henretty:
On this note, it would be useful if content could query the UA for the
default behaviors of any notifications it would send. Also, it would be
nice to know which of these behaviors could be overridden by the behavior
options. Perhaps something
On Fri, Aug 15, 2014 at 1:37 AM, Robert Bindar robertbin...@gmail.com wrote:
We can not say accurately if the default will always be false because
the platform may or may not support the behavior, or it might be overridden
by a user defined setting.
Well, if we introduce new dictionary members
On Fri, Aug 15, 2014 at 1:54 AM, Michael Henretty
michael.henre...@gmail.com wrote:
On this note, it would be useful if content could query the UA for the
default behaviors of any notifications it would send. Also, it would be
nice to know which of these behaviors could be overridden by the
On Aug 15, 2014 1:57 AM, Anne van Kesteren ann...@annevk.nl wrote:
On Fri, Aug 15, 2014 at 1:37 AM, Robert Bindar robertbin...@gmail.com
wrote:
We can not say accurately if the default will always be false because
the platform may or may not support the behavior, or it might be
overridden
On 08/13/2014 04:36 PM, Jonas Sicking wrote:
On Wed, Aug 13, 2014 at 2:12 PM, Robert Bindar
robertbin...@gmail.com wrote:
Concerning web notifications, it would be very helpful for content
and web
apps
to have a way of specifying the behavior their notifications should
have.
For
On Thu, Aug 14, 2014 at 4:37 PM, Robert Bindar robertbin...@gmail.com
wrote:
On 08/13/2014 04:36 PM, Jonas Sicking wrote:
* vibration - vibrate the device
* silent - true means do not play a sound when firing the
notification(the sound
is enabled by default
Concerning web notifications, it would be very helpful for content and
web apps
to have a way of specifying the behavior their notifications should have.
For instance, a chat client may not always want to play a sound when sending
a notification pertaining to a new message. Or in the mobile web,
On Wed, Aug 13, 2014 at 2:12 PM, Robert Bindar robertbin...@gmail.com wrote:
Concerning web notifications, it would be very helpful for content and web
apps
to have a way of specifying the behavior their notifications should have.
For instance, a chat client may not always want to play a sound
14 matches
Mail list logo
