Growl doesn't update click context when coalescing notifications

[GoogleCodeExporter]

The feature: When an application passes an identifier, Growl coalesces the 
notification, updating an 
existing display of the notification rather than creating a new one.

The bug: Growl doesn't update the click context of the notification, meaning 
that the application 
may get a click context it considers stale. Growl should always change the 
click context to the 
latest one the app provided.

Original issue reported on code.google.com by chrisf.g...@gmail.com on 18 Oct 2009 at 3:32

[GoogleCodeExporter]

Original comment by chrisf.g...@gmail.com on 18 Oct 2009 at 3:36

• Changed state: New

[GoogleCodeExporter]

Would the switch to GNTP have anything to do with this?

Original comment by chrisf.g...@gmail.com on 6 Dec 2009 at 5:51

• Added labels: Milestone-1.3

[GoogleCodeExporter]

Original comment by chrisf.g...@gmail.com on 29 Jul 2010 at 4:43

• Added labels: Milestone-2.0

[GoogleCodeExporter]

can we get clarification as to where this report came from?

traced through the current code and this is what we have:

when coalesced the notification gets set on the bridge, which then sets it on 
the window controller. when the user clicks on the notification it then 
attaches the dictionary, that's been sent down the line, to the NSNotification 
that GHA is listening to for clicked notifications. GHA extracts the click 
context from the dictionary and passes that along to the app/gntp remote host 
that's waiting to hear.

Original comment by rarich...@gmail.com on 29 May 2011 at 12:09

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

It was on launchpad. Nothing else was really in the ticket.

Original comment by chrisf.g...@gmail.com on 29 May 2011 at 2:46

[GoogleCodeExporter]

Closing. If this is still a problem we can reopen it.

Original comment by ch...@growl.info on 28 Sep 2011 at 6:52

• Changed state: CantReproduce