User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:22.214.171.124) Gecko/2009061118 Fedora/3.0.11-1.fc9 Firefox/3.0.11 Build Identifier: 3.6 I have bugzilla configured so that when I modify a bug, bugzilla will then display the next bug in my list. If I edit, say, bug 1000, and click "save changes", then the changes are saved and the window displays the next bug in my list, say bug 1200. However, the browser tab still says "bug 1000". It should say "bug 1200", or maybe just say "changes saved". Otherwise, I will click on that tab later, thinking it is bug 1000, and accidentally edit and modify bug 1200. Reproducible: Always Steps to Reproduce: 1. Preferences: after changing a bug, site default (show next bug in my list) 2. Need to "own" more than one bug 3. Open first bug in window, edit, and "save changes" Actual Results: After editing and saving bug 1000, tab shows "bug 1000", but page displays bug 1200. Expected Results: Tab should show something other than "bug 1000", since window no longer has any connection to bug 1000. I don't know how to specify the bugzilla build version. The release notes just say "Welcome to bugzilla 3.6!". I don't see a help/about item.
It says "bug 1000 processed", not "bug 1000" alone. That's a bit less confusing. I have no strong opinion on what should be set as page title. Max, Guy, any opinion? For consistency, we could indeed use the currently displayed bug ID instead of the last edited bug ID (the page header already mentions the bug being displayed).
That would explain it. When I have 10 tabs open in my browser, all I see in the narrow tab is "bug 1000". The "processed" part is not displayed. I guess I shouldn't rely too much on browser tab text! Paul
(In reply to comment #4) > history.push makes Firefox 4 to display the displayed bug ID in the title of > the page. Actually, I'm pretty sure that setting the title via history.push does not work in any browser, and will never work.
is the reason why this bug is still open is because IE doesn't support history.push? We set the title via JS with a document.title. If your suggestion is to move the document.title out to be in another place... we should just be specific if this bug is fixed with the history.push or if it needs some additional work.
It would be nice to have the template actually set the page title properly.
(But that's just an "it would be nice.")