browser.js uses the non-standard "for each" loop in handleClearHistory(). "for each" has recently been removed by bug 804834 and in m-c builds today the browser app does not work because of this.

Comment on attachment 696117 [details] link to patch on github Dale, I've fixed the nearby bug with the undefined tabId identifier. But it looks like the bug was deeper... There were multiple closures created in a for loop, so the tabId value would change before the nested callback function would be invoked. So I had to restructure the code to use Object.keys(this.tabs).forEach() instead of a for in loop. So I'm asking for another review before landing it.

Dale, The main reason I need more review on this is that I don't know what self.refreshButtons() is supposed to do, so I can't tell if it is getting called appropriately.

Comment on attachment 696117 [details] link to patch on github Fix is good, merged in: https://github.com/mozilla-b2g/gaia/commit/12b722515af8df6eabad59ac8ecd19d8b0b24734 Just for reference sake, the buttons are refreshed as the history of all tabs including the currently visible one is removed, meaning the user cannot go back / forwards