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.
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.
I don't know what we should do here, but I do think that this deserves a
discussion.
- Marco.
On 10/08/2013 03:00 PM, Dave Townsend wrote:
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 now.
There is a comment towards the end of the bug asking whether backing
out a single part of the patch instead of the whole feature would
solve the problems, we probably need an answer to that before
considering whether a full backout is appropriate.
It's not totally clear to me what the new feature gives us (i.e. what
we would lose from desktop Firefox if we backed it out but left it on
the b2g branch) and what has regressed as a result because it is
spread over too many bugs. Is it possible to summarise that?
On Tue, Oct 8, 2013 at 2:48 PM, Marco
<mar.castelluc...@studenti.unina.it
<mailto:mar.castelluc...@studenti.unina.it>> 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 notifications, because XUL notifications don't behave
correctly on those systems (multi-monitor support is broken, etc.).
The patch to remove this support was reviewed, but the reviewer
said to ask to the dev-platform newsgroup before landing, because
the change had some impact. I couldn't find any thread on this
list where this was discussed...
There are proposals of backout in the bug. What should we do?
- Marco.
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org <mailto:dev-platform@lists.mozilla.org>
https://lists.mozilla.org/listinfo/dev-platform
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
