OK, i have looked into this and found some connections.
Specifically, all major OSs seem to have APIs providing the following:
1. download progress
2. native notifications.
As older versions don't have those, and linux systems are pretty modular in any
case, i propose that we use no fallback
On Monday, October 28, 2013 6:38:07 AM UTC-5, Philip Chee wrote:
On 28/10/2013 16:02, Florian Bender [:fbender] wrote:
Mac OS X Mavericks has been released with improvements to NC. Safari
uses NC to display Web/PushNotifications and seems to work quite
well.
I'd like you to
Not mapping Web Notifications to native notifications seems very
unfortunate, since it means Web apps can't use Web Notifications to
get a native experience.
Is there a summary of what exactly prevents the use of native
notifications and why we shouldn't change the spec so that it can be
mapped
Nothing. Just time. Patches accepted.
On Oct 29, 2013, at 6:26 AM, Henri Sivonen hsivo...@hsivonen.fi wrote:
Not mapping Web Notifications to native notifications seems very
unfortunate, since it means Web apps can't use Web Notifications to
get a native experience.
Is there a summary of
On Oct 29, 2013, at 12:23 PM, Doug Turner doug.tur...@gmail.com wrote:
Nothing. Just time. Patches accepted.
Not really? Last time I looked into this one of the problems was that
AlertsService exposes an alertfinished event (for when the notification goes
away) that we can’t implement when
Mac OS X Mavericks has been released with improvements to NC. Safari uses NC to
display Web/PushNotifications and seems to work quite well.
I'd like you to revisit the decision to drop NC in favor of XUL Notifications,
and have a second look at the new API and capabilities. NC support could be
On 28/10/2013 16:02, Florian Bender [:fbender] wrote:
Mac OS X Mavericks has been released with improvements to NC. Safari
uses NC to display Web/PushNotifications and seems to work quite
well.
I'd like you to revisit the decision to drop NC in favor of XUL
Notifications, and have a second
On 10/12/2013 5:50 AM, Philip Chee wrote:
Um, what? libnotify was removed because the developer was too lazy to
google for the docs?
Phil, you've been in the community long enough to know that this isn't
appropriate participation. Insulting other contributors like this is
not acceptable
On 2013-10-12 12:39:37 +, Philip Chee said:
There was no support for Mac native notifications. Mostly because there
were no notifications native to the Mac (The OS X notification centre
didn't exist then).
But they added Notification Center support pretty recently. It makes
things much
On 09/10/2013 05:48, Marco wrote:
In bug 782211, native notification systems support was removed. A lot of
bugs have been filed to restore support for libnotify and Mac native
There was no support for Mac native notifications. Mostly because there
were no notifications native to the Mac (The
On 09/10/2013 09:14, Marco wrote:
It's not entirely clear to me why libnotify support was removed, the
author of the patch stated:
I removed Growl support because it does not support features needed to
implement the spec. I also removed libnotify support because I can't
find documentation
On Oct 12, 2013, at 2:50 PM, Philip Chee philip.c...@gmail.com wrote:
On 09/10/2013 09:14, Marco wrote:
It's not entirely clear to me why libnotify support was removed, the
author of the patch stated:
I removed Growl support because it does not support features needed to
implement the
In bug 782211, native notification systems support was removed. A lot of
bugs have been filed to restore support for libnotify and Mac native
notifications, because XUL notifications don't behave correctly on those
systems (multi-monitor support is broken, etc.).
The patch to remove this
That's a pretty long bug to ask people to read over but...
The original comment about posting to dev-platform seems to be simply
asking that a thread be made to warn people that this change is coming, not
for any discussion as such. It should have happened at the time but it's a
bit late for it
The bug has regressed a lot of things. To me it looks like the decision
to land it was a bit rushed. For example, I think we shouldn't have
removed the Mac notification system, if it supported the necessary
features for the notifications API. Some people say also libnotify
should support the
On Tue, Oct 8, 2013 at 3:30 PM, Marco mar.castelluc...@studenti.unina.itwrote:
The bug has regressed a lot of things. To me it looks like the decision
to land it was a bit rushed. For example, I think we shouldn't have removed
the Mac notification system, if it supported the necessary
Marco writes:
The bug has regressed a lot of things. To me it looks like the
decision to land it was a bit rushed.
I can't help wondering whether the feature was needed urgently on
b2g, and the people involved just didn't care enough if getting
that done quickly also damaged desktop products.
On 10/08/2013 04:37 PM, Dave Townsend wrote:
On Tue, Oct 8, 2013 at 3:30 PM, Marco
mar.castelluc...@studenti.unina.it
mailto:mar.castelluc...@studenti.unina.it wrote:
The bug has regressed a lot of things. To me it looks like the
decision to land it was a bit rushed. For example, I
: dev-platform dev-platform@lists.mozilla.org
Sent: Tuesday, October 8, 2013 6:14:11 PM
Subject: Re: Removal of native notification systems on desktop platforms
On 10/08/2013 04:37 PM, Dave Townsend wrote:
On Tue, Oct 8, 2013 at 3:30 PM, Marco
mar.castelluc...@studenti.unina.it
19 matches
Mail list logo
