Closed Bug 728385 Opened 8 years ago Closed 7 years ago

[10.8] Include support for Mountain Lions "Notification Center" into Thunderbird

Categories

(Thunderbird :: OS Integration, enhancement)

x86
macOS
enhancement
Not set

Tracking

(Not tracked)

RESOLVED FIXED
Thunderbird 19.0

People

(Reporter: Nomis101, Unassigned)

References

(Blocks 1 open bug, )

Details

(Whiteboard: [gs][fixed by bug 728106])

Attachments

(1 file)

OS X 10.8 has a new service "Notification center", which is a bit similar to Growl. Would be nice if we include support for this into Thunderbird for new mails, for the instant messaging feature, for news (and what else).
Blocks: tb-mac
Is there already toolkit support for this?
Not yet, toolkit support is Bug 728106.
Depends on: 728106
Cool, after building TB with the WIP patch from Bug 728106 I see TB in my notification center preferences. I also get a Growl-like notification for new mails, which than dissapears. But I don't see the notification in the notification center bar (or whatever this is named) if I toggle it.
I have just upgraded to OS X 10.8 and it would be great, if I could use TB with the new notification center. When will it be available in the stable release of TB on Mac?
(In reply to markusd112 from comment #4)
> I have just upgraded to OS X 10.8 and it would be great, if I could use TB
> with the new notification center. When will it be available in the stable
> release of TB on Mac?

Bug 728106 needs to be fixed for this first. So I expect it (in the stable release) when TB 17 (or 18?) will be released.
Note: Growl support will be removed completely in Bug 777409.
(In reply to Philipp Kewisch [:Fallen] from comment #1)
> Is there already toolkit support for this?
Now there is toolkit support for this, but only if the application is in the background.
Firefox 17.0 is adding support for 10.8 Notification Center. Since both Firefox and TB share the some common core code, why can't that piece of code be included into TB 17 to add support for Notification Center?
Oh, thanks for reminding me to that. Because it is Core code it is in TB 17 and above and works if TB is in the background. There is nothing we need to do for this specific for TB, so I will close this Bug. So, fixed by Bug 728106.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Whiteboard: [gs] → [gs] [fixed by bug 728106]
Target Milestone: --- → Thunderbird 17.0
Hi all -- Apologies for this note.  I noticed that, though I am currently running Thunderbird 17 beta 2 on my mac, this support for the Notification Center is not appearing to be in there yet.  I saw this ticket was marked "resolved and fixed," so I wondered if someone could flag when it would appear in the product.  THANKS --eric
This bug is not fixed in TB 17 and the Status need to be Changed from the existing Resolved Fixed. FF 17 Beta at one time added the support and based on that this bug was marked as Resolved for TB 17 as well. But looks the support for Notification Center has been pulled from the final FF 17 according to https://bugzilla.mozilla.org/show_bug.cgi?id=806351 "Bug 806351 - disable Notification Center support on beta (Firefox 17), it isn't ready". Hence this bug also need to be re-opened. Thanks
Whiteboard: [gs] [fixed by bug 728106] → [gs]
Target Milestone: Thunderbird 17.0 → ---
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
It was only disabled in 17/18. The notification support hasn't been backed out of trunk.
Status: REOPENED → RESOLVED
Closed: 7 years ago7 years ago
Resolution: --- → FIXED
Target Milestone: --- → Thunderbird 19.0
Whiteboard: [gs] → [gs][fixed by bug 728106]
When will this finally be incorporated in the release channel? Apparently there will not be a Thunderbird 19.0 because the release schedule has been upended (see https://etherpad.mozilla.org/tb-releases ). So can we expect it in 17.1? 17.2? Version 24 in September?
Sorry to keep asking, but this is becoming a bit weird. The code that solves this bug (or 'obvious lacking feature') was apparently added in October, and it is still not in Thunderbird... because they changed the _numbering_ of their release cycle!

How do we get the TB managers to put this in a version number that is coming up before Christmas 2015?
Yes, thats a bit confusing. It was in Thunderbird, but is now replaced with this new XUL notifications. So there will be no Thunderbird with native Notification center support. But it is planed to link the new XUL notifications with Notification center. (Therefore I've build my own TB with native Notification center support with the old NC code)
As a longtime Thunderbird user/fan, I'm saddened by the extent to which Thunderbird is out of touch with users, who simply want seamless integration with their operating system. It looks like they've really given up.

Please change the status of this bug to RESOLVED FIXED BUT ABANDONED THE SOLUTION, or whatever this situation is called.

Is there any ETA on the link between the XUL notifications and Notification center?
Disclaimer: this is an end-user message

Why does this bug is marked as "RESOLVED" ?

I don't see anything now (TB 24.0.1) that allow to use Notification Center except Growl (which must be purchased to be used).

Bug 728106 is in the same state but nothing appears in TB24.
Flags: needinfo?(Nomis101)
(In reply to lau.hub from comment #18)
> Disclaimer: this is an end-user message
> 
> Why does this bug is marked as "RESOLVED" ?
> 
> I don't see anything now (TB 24.0.1) that allow to use Notification Center
> except Growl (which must be purchased to be used).
> 
> Bug 728106 is in the same state but nothing appears in TB24.

See #16. 
It was added here: http://hg.mozilla.org/mozilla-central/rev/67c5213dfe2b
And removed here: http://hg.mozilla.org/mozilla-central/rev/c9732200552d
Maybe Bug 852648 will fix the current Mac unpleasantness.
Flags: needinfo?(Nomis101)
This is not resolved. The issue is still there in TB 24.6. Shoul another bug be created or this one can be reopened?
Is is resolved since TB 28. So, it will be resolved if TB 31 will be released around July 22. I don't think it will ever be fixed in TB 24.
You need to log in before you can comment on or make changes to this bug.