The bugfix was by kareila: The major change in behavior is that it opens the link in a new window when clicked on. I did it this way for two reasons.
1) Inbox stays open in background, and will show refreshed state when the user returns. If the link replaces the inbox, then when you click the back button,the link still shows as unread, although it is actually read and will update state on refresh.
2) Attempts to change the window location with JS resulted in some sort of error message being triggered from devel.js (in cvs/js). "Logger popup window blocked. Using confirm() instead." I couldn't figure out what was going on with that.
Seems like it's not an easy thing to have it both ways: no new window, but also mark things as read when they are acted upon.
Oh, okay, that was linked to in the original suggestion. I didn't completely read throug that, just saw your comment. Please disregard then.
no subject
http://bugs.dwscoalition.org/show_bug.cgi?id=1284
The bugfix was by
clicked on. I did it this way for two reasons.
1) Inbox stays open in background, and will show refreshed state when the user returns. If the link replaces the inbox, then when you click the back button,the link still shows as unread, although it is actually read and will update state on refresh.
2) Attempts to change the window location with JS resulted in some sort of error message being triggered from devel.js (in cvs/js). "Logger popup window blocked. Using confirm() instead." I couldn't figure out what was going on with that.
Seems like it's not an easy thing to have it both ways: no new window, but also mark things as read when they are acted upon.
Oh, okay, that was linked to in the original suggestion. I didn't completely read throug that, just saw your comment. Please disregard then.