Closed
Bug 348956
Opened 19 years ago
Closed 1 year ago
window.focus() and window.blur() do not function on Debian
Categories
(Core :: General, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: jvlb, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.5) Gecko/20060626 Firefox/1.5.0.5 (Debian-1.5.dfsg+1.5.0.5.x.1-2)
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.5) Gecko/20060626 Firefox/1.5.0.5 (Debian-1.5.dfsg+1.5.0.5.x.1-2)
This bug has been reported before, then erroneously classed as resolved. It has existed since at least Firefox 1.0.3 and has continued unabated through Firefox 1.5.0.5. I have found it on every version of Sarge I've tested, most recently with Xandros 4 and SimplyMEPIS 6 (Ubuntu Dapper Drake core). Please do not test this in a non-Debian distro and proclaim, as has happended before, that there is no problem.
Reproducible: Always
Steps to Reproduce:
1. Simply use the "build windows in background"
2. and the "display windows" features on the page
3.
Actual Results:
The target windows are unresponsive.
Expected Results:
The windows should blur() or focus()
Comment 1•19 years ago
|
||
I rather doubt that anyone has said that there's no problem; instead, I'd guess they've said "we didn't break it, and we don't know how Debian did break it, and we don't have write access to their repository, which makes this their bug, not ours." So, I'd go ahead and resolve your bug invalid (which it is, in a number of other ways, too: if you don't approve of the resolution of a bug that you know of, filing a new bug and not even admitting to the other bug's number isn't the proper approach to getting it reconsidered) except I expect that you'll want to dispute that it's invalid, and reopen, so what say we get that out of the way without bothering with the INVA/REOPEN/INVA/REOPEN/INVA dance?
Bugs in a distro's version which don't exist in Mozilla's version are that distro's bug, right up until they say "we're breaking it because of this underlying bug that Mozilla doesn't expose, but needs to fix." So, imagine I resolved this invalid, and you reopened, and let's have your next shot ;)
Product: Firefox → Core
QA Contact: general → general
Version: unspecified → 1.8 Branch
Reporter | ||
Comment 2•19 years ago
|
||
I'm not sure where your "next shot" business is coming from, but, yes, it has been classed as resolved by someone testing in another distro and proclaiming that the bug no longer existed. Unfortunately, I do not have the number for the prior bug report at my disposal. Someone privy to more of the process than I did discover that different libraries were being used to compile the source for the deb distribution. I'm afraid I wouldn't know where to begin in recitifying that issue, but since you seem to have more insight into such matters, perhaps you might see clear to do more than snark.
Could you try running a build from mozilla.com? That comes without the Debian patches. If that works, then it's probably something introduced by Debian and thus we can't fix. Thanks.
http://www.mozilla.com/products/download.html?product=firefox-1.5.0.6&os=linux&lang=en-US
(You'll probably need to install some supporting packages from Debian too, since that links against an older version of libstdc++ )
For reference, the related bug is bug 311956 which has a corresponding Ubuntu bug open at https://launchpad.net/distros/ubuntu/+source/firefox/+bug/33840
Reporter | ||
Comment 4•19 years ago
|
||
Thanks, Mook, for the constructive input. I'm not sure I'll have time to pursue this further, but I am reminded that this problem predates the Ubuntu bug. It first appeared as a regression on Woody, as it was not found in the then current Mozilla suite.
Reporter | ||
Comment 5•19 years ago
|
||
Here is at least one earlier reference to the bug in question: https://bugzilla.mozilla.org/show_bug.cgi?id=311956
Reporter | ||
Comment 6•19 years ago
|
||
I should add that the Mozilla browser in the Mozilla Suite continues to function properly, at least through release 1.7.12; this is a Firefox-only bug.
Updated•3 years ago
|
Severity: normal → S3
Comment 7•1 year ago
|
||
According to the comment 3 and comment 4, this wasn't a bug on Gecko.
FWIW, please file a new bug if you see a similar problem with the latest linux distro on the latest Firefox.
Status: UNCONFIRMED → RESOLVED
Closed: 1 year ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•