Closed
Bug 226774
Opened 21 years ago
Closed 19 years ago
In <win040.html> and <win041.html> JavaScript Testcase, 'window.screenX' and 'window.screenY' may seem to "fail", if the screen coordonates are already occupied.
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: sgautherie, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.6a) Gecko/20031030 Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.6a) Gecko/20031030 This is spun off from bug 142649 comment 3. Reproducible: Always Steps to Reproduce: 1. Load URL. Actual Results: Description Pass Bug Number Actual Result Expected Result Read window.screenY 0 failed Bug# 5998 28 0
Comment 1•21 years ago
|
||
Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.6a) Gecko/20031029 Hmm. Same thing occur with http://mozilla.org/quality/ngdriver/suites/javascript/win040.html (window.screenX). Desale's testcase in bug 5998 doesn't work either. Looks like window.screenX and window.screenY have become read-only?
Assignee: general → general
Component: Browser-General → DOM: Level 0
QA Contact: general → ian
Comment 2•21 years ago
|
||
Stefan, window.screen[X,Y] are settable here, you don't by any chance have the "Move or resize existing windows" pref unset do you (in Preferences/Advanced/Scripts & Plugins)?
Reporter | ||
Comment 3•21 years ago
|
||
[Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.6a) Gecko/20031030] (BuildId=2003110115, bug 224340#c19) (W98SE) Re comment 1: I get { win040.html Description Pass Bug Number Actual Result Expected Result Read window.screenX 0 passed 0 0 } to a new tab, or from a full window. Only window041 test fails on my system. On the other hand, if both case expected results should not be 0, then both _testcases_ should be updated, as a start. About bug 5998 testcase, it works "fine" for me: copied from bug 5998 comment 0 { On windows everything works fine, its only problem with Mac OS. } May be you should deal with bug 5998 on your system, before looking into the current bug ? Re comment 2: For the record, on my system, the pref. is checked, and Mozilla does resize. Today, the result of window041 is 104 instead of 28; anyway... ***** Oh, well, I found what is going wrong in my case ! Both testcases assumes that Mozilla window _can_ be set to (0+,0+) coordonates; but that is not the case when one has the Window menu bar on top or left, or if you have an add-bar for example on top, etc ! Then, my suggestion becomes to add a comment to the testcases, as it was done for bug 47280; (and about move/resize pref. too !?) unless the testcases can be improved somehow. Changing: (S) Normal -> Minor.
Severity: normal → minor
Reporter | ||
Updated•21 years ago
|
Summary: In <win041.html> JavaScript Testcase, 'window.screenY' return value issue → In <win040.html> and <win041.html> JavaScript Testcase, 'window.screenX' and 'window.screenY' may seem to "fail", if the screen coordonates are already occupied.
Comment 4•21 years ago
|
||
Johnny, I thought I had it set - but I didn't (sigh...). Once i removed the OS X Dock from the left screenX works as well. So both testcases are wfm.
Comment 5•19 years ago
|
||
So, is this bug still present? The url is 404.
Reporter | ||
Comment 6•19 years ago
|
||
(In reply to comment #5) > So, is this bug still present? The url is 404. {{ <https://bugzilla.mozilla.org/show_bug.cgi?id=226823#c33> ------- Additional Comment #33 From David Baron 2005-03-18 12:59 PDT [reply] ------- quality/ngdriver appears to already be removed. }} Checked: this explains that. R.Fixed
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•