The browser title is sometimes not changed when there is an unread message

[GoogleCodeExporter]

If a message is received and the user either has no tabs open or the message is 
received on the currently open tab then the message is assumed to have been 
read straight away. This means that the browser title text is not changed to 
indicate the unread message.

We could use the browser focus tracking to always change the browser title when 
the chat window doesn't have focus.

Original issue reported on code.google.com by ashward....@gmail.com on 15 Jul 2010 at 1:19

[GoogleCodeExporter]

Original comment by ashward....@gmail.com on 15 Jul 2010 at 3:26

• Changed state: Accepted

[GoogleCodeExporter]

Hello Ash: do you know a easy way to track the browser focus? You implemented 
something similar, isn't it?

Original comment by danigb on 15 Jul 2010 at 8:06

[GoogleCodeExporter]

I added a BrowserFocus class to the signals module which can be used to tell 
whether the browser currently has focus. Perhaps it also needs some events 
added to it so that when the browser regains focus we can stop the tab 
flashing? Or should we leave it flashing so that the user knows that it's the 
focussed tab which had the new message? Perhaps make it flash for a few seconds 
after the browser gains focus or until the user clicks on something?

Original comment by ashward....@gmail.com on 15 Jul 2010 at 8:25

[GoogleCodeExporter]

Ok, now I understand the problem. I like the gmail approach: to remove the 
color from the tab you should either or click over the tab or put the focus on 
the input textarea. So, when the browser is not focused and the open chat 
receives the tab, the tab should be "not readed" (red) and then the user needs 
to 1) focus the browser 2) click over the input textarea or over the tab itself 
(even if its open). What do you think?
Also I think we need to move your BrowserFocus class to other module... Maybe 
create a browserfocus gwt module to handle this? Suggestions welcomed ;)

Original comment by danigb on 15 Jul 2010 at 8:51

[GoogleCodeExporter]

This issue was closed by revision r1515.

Original comment by danigb on 20 Jul 2010 at 12:58

• Changed state: Fixed