2008/9/13 Thomas Broyer [EMAIL PROTECTED] > > I don't get it, sorry. >
Never mind. > There cannot be change events if there's nothing to change, so History > needs a newItem() method (and back(), forward() and go()). Apart from > that, it's just what you described: it "fires history listeners when > the history actually changes". > It fires history events when the history changes, it also fires history listeners when the history *hasn't* changed and it fails to fire history listeners when the history *does* change. What I'm trying to get an answer to is why it *used* to be OK to fire history listeners with a token but without affecting the history stack, but now, suddenly, it isn't. It doesn't matter if you can't envisage a use for it, it's not been superceeded, so what is so evil about it? Why was it thought necessary to a) remove it completely and then b) reinstate it but deprecated? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
