Closed
Bug 1877
Opened 26 years ago
Closed 25 years ago
[FEATURE] Javascript window.screen implementation
Categories
(SeaMonkey :: UI Design, defect, P1)
SeaMonkey
UI Design
Tracking
(Not tracked)
RESOLVED
FIXED
M11
People
(Reporter: balu.ram, Assigned: davidm)
References
Details
(Whiteboard: Mac/GTK have garbage values until dependant bugs are fixed)
Attachments
(1 file)
|
(deleted),
text/html
|
Details |
Hi,
I have a file with the following code. When I try to load in the NGlayout (Geko)
it fails to load.
<script language=javascript>
window.open("index1.html", "Alerts",
"TOOLBAR=NO,location=no,directories=no,status=yes,menubar=no,scrollbars=no,resiz
able=no,width="+eval("screen.width - 10")+",height="+eval("screen.height -
45")+"screenX=0,screenY=0");
// close(parent);
</script>
<html>
</html>
Javascript error: Screen is not defined.
URL: file ://N:/alerts/index.html, LineNo:3
Line text: '(null)', Error text: 'null'
Thanks
|
||
Updated•26 years ago
|
Assignee: vidur → joki
|
||
Updated•26 years ago
|
Assignee: joki → rpotts
Summary: Javascript error: screen is not defined → window.screen is not fully implemented
|
|
||
Comment 1•26 years ago
|
||
I've added the screen object so as to stop causing errors. The value it
returns are still bogus, though. Rick, passing this to you as a reminder that
I need this api for screen info. Pass it back to me when you're done.
Changed platform and OS to all, and component to Apprunner.
Rick, figure out whether you or Nisheeth should implement this.
|
||
Updated•26 years ago
|
QA Contact: 3853
|
|
||
Comment 5•26 years ago
|
||
per leger, assigning QA contacts to all open bugs without QA contacts according
to list at http://bugzilla.mozilla.org/describecomponents.cgi?product=Browser
Setting QA Contact to rpotts since eng will have to verify this code fix.
Re-assigned to davidm@netscape.com and changed target milestone to M5.
Is implementing js objects really an XPApp task? I don't mind doing it if someone
points me in the right direction but I would like to know how many of these
objects there are so I can fix them before they make it to the bug list.
|
Assignee | |
Comment 10•26 years ago
|
||
so I don't get spammed
|
||
Comment 11•26 years ago
|
||
Changed milestone to M6.
|
|
Assignee | |
Comment 12•26 years ago
|
||
*** Bug 5463 has been marked as a duplicate of this bug. ***
|
|
Assignee | |
Comment 13•25 years ago
|
||
m7
|
|
Assignee | |
Comment 14•25 years ago
|
||
Filed bugs against layout for not implimenting
nsDeviceContextMac::GetDeviceSurfaceDimensions. Still have to figure out how to
determine which chrome is on a screen when given a window
Summary: window.screen is not fully implemented → [FEATURE] Javascript window.screen implementation
|
|
Assignee | |
Comment 15•25 years ago
|
||
|
|
Assignee | |
Comment 16•25 years ago
|
||
Checked in code. The avail functions currently return default values ( 0 for the
offsets or the hieght/width). On Mac/GTK the values will be garabage until the
dependant bugs are fixed. Still have to work out a strategy for calculating
window chrome location and size. Moving off to m9. I have attached my sample test
file
|
|
Assignee | |
Comment 17•25 years ago
|
||
*** Bug 8763 has been marked as a duplicate of this bug. ***
|
|
Assignee | |
Comment 18•25 years ago
|
||
added dependency
|
||
Comment 19•25 years ago
|
||
*** Bug 9731 has been marked as a duplicate of this bug. ***
|
|
Assignee | |
Comment 20•25 years ago
|
||
Not going to happen for m9 lets try ,11
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
|
|
Assignee | |
Comment 21•25 years ago
|
||
Fix checked in an verified on the mac.
|
||
Updated•20 years ago
|
Product: Core → Mozilla Application Suite
You need to log in
before you can comment on or make changes to this bug.
Description
•