Closed
Bug 164968
Opened 22 years ago
Closed 15 years ago
Mozilla returns error on position property of window object via AppleScript
Categories
(SeaMonkey :: UI Design, defect)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: wjshack, Assigned: samir_bugzilla)
References
(Depends on 1 open bug)
Details
Mozilla can't get (or set) the position property of a window. All other window
properties (bounds, index, name, etc) work, but
tell application "Mozilla"
set winName to the name of the front window
get the position of window winName
end tell
produces an error message can't get data of type. also occurs in OS X.
Confirmed using Mac/2002082503/9.2.2. position is in the AS dict, but doesn't work,
generating the execution error, "Mozilla got an error: Can't make some data into the expected
type." Reassigning to XP Apps.
Assignee: asa → sgehani
Status: UNCONFIRMED → NEW
Component: Browser-General → XP Apps
Depends on: 125419
Ever confirmed: true
QA Contact: asa → paw
Summary: Missing property value Applescript window object → Mozilla returns error on position property of window object via AppleScript
Comment 2•21 years ago
|
||
This bug is targeted at a Mac classic platform/OS, which is no longer supported
by mozilla.org. Please re-target it to another platform/OS if this bug applies
there as well or resolve this bug.
I will resolve this bug as WONTFIX in four weeks if no action has been taken.
To filter this and similar messages out, please filter for "mac_cla_reorg".
Updated•20 years ago
|
Product: Core → Mozilla Application Suite
Comment 4•15 years ago
|
||
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.
If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.
Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
Comment 5•15 years ago
|
||
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.
Because of this, we're resolving the bug as EXPIRED.
If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.
Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•