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 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 necessary features,
but I don't know if they're right.
A quick summary of the regressions:
1) Thunderbird and other products that don't need web
notifications, are now using XUL notifications.
2) On some Linux distributions, notifications are logged somewhere
(in the status bar, for example) to allow people to see
notifications that were triggered while they were away. With XUL
notifications we don't support this anymore.
3) XUL notification may cover system notifications.
4) On Linux, XUL notifications always appear on the top right
corner. System notifications may appear in other places according
to the DE that you're using.
5) On Linux, XUL notifications have a different theme than system
notifications.
6) XUL notifications are ugly compared to system notifications.
7) XUL notifications don't properly support multi-monitor
configurations. It's extremely easy to miss a notification when
you're using multiple monitors.
8) XUL notifications are just windows, so they may interfere with
what the user is doing. For example, they cause drag&drop
operations to fail.
Awesome, thanks
#2 is also for Mac. Chrome has native notifications and its
notifications are shown in this bar on the right:
http://tinypic.com/view.php?pic=fwucrk&s=6
The options proposed in the bug were:
1) Use native notifications for Firefox notifications and XUL
notifications for web notifications.
2) Backout the entire feature.
3) Backout the native notification removal.
How is option 3 different to option 1?
I guess they're pretty similar. I'd say we have two options if we want
to back out the native notification removal:
1) Use native notifications for Firefox notifications and XUL
notifications for web notifications.
2) Try to always use native notifications.
I don't know what we should do here, but I do think that this
deserves a discussion.
For sure. I assume there are reasons why we can't use native
notifications for web notifications? That being the case to me option
1 seems like the best course, but I don't know the work involved in
making that happen and that still leaves us with some regression
around the interactions between the two.
I'm not sure. Reading through the bug, looks like there are reasons we
can't. At the same time in different bugs there are conflicting
statements (see bug 858919 for Linux).
The opinion from UX (comment 18 in bug 782211) was: "When the system
supplies a notification center we should use that. In cases where that
isn't true we will need display our own custom notifications. This
includes all versions of Windows before 8 and all versions of OSX before
10.8."
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 about all the capabilities, so it's possible that
libnotify could work but I just can't find it in the documentation."
- Marco.
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
