900634 - Improve XUL alerts styling on Linux

Status: NEW

(Toolkit :: Alerts Service, defect)

Description

[Marco Castelluccio [:marco]]

They're really ugly at the moment, could we do something to improve their look?

Comment 1

[Marco Castelluccio [:marco]]

I see three options here:
1) Improve the alert.css and keep using XUL notification, keeping a consistent look between the three platforms.
2) Use a platform-specific nsAlertsService that creates notifications like notification-daemon/notify-osd/whatever (not directly using those services, but using their same "bubble" windows).
3) Use a platform-specific nsAlertsService that uses libnotify and falls back to option 1 or option 2 when the notification server doesn't support features needed for the notifications API.

Comment 2

[Philip Chee]

> 3) Use a platform-specific nsAlertsService that uses libnotify and falls back to
> option 1 or option 2 when the notification server doesn't support features needed
> for the notifications API.

Not that I disagree with you, but the original rationale for removing libnotify support was that it didn't support the features needed for the w3c notifications. So what you are proposing is a NOOP.

Comment 3

[Marco Castelluccio [:marco]]

(In reply to Philip Chee from comment #2)
> > 3) Use a platform-specific nsAlertsService that uses libnotify and falls back to
> > option 1 or option 2 when the notification server doesn't support features needed
> > for the notifications API.
> 
> Not that I disagree with you, but the original rationale for removing
> libnotify support was that it didn't support the features needed for the w3c
> notifications. So what you are proposing is a NOOP.

Yes, I know, I was proposing to use libnotify for simple notifications and custom alerts when libnotify isn't enough.

Comment 4

[Matthew N. [:MattN]]

Bulk move to Toolkit::Notifications and Alerts

Filter on notifications-and-alerts-component.