Regression range would be very useful.
I don't known how to get a regression range. I'm trying to get builds on ftp://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/ but it's a pain to find things: I'm trying to look in *-mozilla-central directories, but in most of them, there is no linux build. Is there an easy way to get old xulrunner/firefox builds ?
nightly builds are usually used to find regression range. Linux builds are typically in the same -XX-mozilla-central, but from time to time the -XX- changes. It is usually best to use binary search (or similar) to find regression range. We know that 1.9.1 doesn't have the bug and 1.9.1 branched late November 08. So I'd start from a build around mid March 09.
This one does not have the bug: ftp://ftp.mozilla.org/pub/firefox/nightly/2009/06/2009-06-10-03-mozilla-central/ This one does: ftp://ftp.mozilla.org/pub/firefox/nightly/2009/06/2009-06-11-03-mozilla-central/
Sounds like a regression from the focus landing.
Created attachment 387493 [details] [diff] [review] windows don't GetInterface to nsIDocShellTreeItem, so use GetPrivateRoot instead
Assignee: nobody → enndeakin
Status: NEW → ASSIGNED
The code here is checking if the window is active and doesn't fire a select event if it is not. This was added by bug 92879 to avoid a focus stealing issue. I have a feeling that check may not be even needed anymore though. Perhaps we could simplify the code entirely.
Created attachment 387538 [details] [diff] [review] with working test
Attachment #387538 - Flags: review?(bzbarsky) → review+
Status: ASSIGNED → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → FIXED
status1.9.2: --- → beta1-fixed
Flags: blocking1.9.2? → blocking1.9.2+
Priority: -- → P2
You need to log in before you can comment on or make changes to this bug.