Closed
Bug 46407
Opened 25 years ago
Closed 10 years ago
The current URL cannot be querried by another app
Categories
(Firefox :: Shell Integration, enhancement, P3)
Tracking
()
RESOLVED
DUPLICATE
of bug 516502
Future
People
(Reporter: scox, Assigned: samir_bugzilla)
References
(Blocks 1 open bug)
Details
(Keywords: helpwanted)
Attachments
(1 file)
556 bytes,
text/applescript
|
Details |
Mozilla does not respond to a request for the 'curl' property of the first 'cwin'. Older versions of Netscape Navigator respond by returning the current URL of the top-most window.
Adding RFE and Helpwanted keyword. Any takers?
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: helpwanted
Summary: The current URL cannot be querried by another app → [RFE] The current URL cannot be querried by another app
Comment 2•24 years ago
|
||
Since Don has left, Vishy is taking his bugs in bulk, pending reassignment. thanks, Vishy
Assignee: don → vishy
nav triage team: Won't do this for beta1, marking nsbeta1-
OS: All
Marking nsbeta1- bugs as future to get off the radar
Target Milestone: --- → Future
Comment 6•23 years ago
|
||
Reassigning to a real person.
Assignee: vishy → sgehani
QA Contact: sairuh → paw
Comment 7•22 years ago
|
||
[RFE] is deprecated in favor of severity: enhancement. They have the same meaning.
Severity: normal → enhancement
Summary: [RFE] The current URL cannot be querried by another app → The current URL cannot be querried by another app
Does the following AppleScript do what you need? tell application "Mozilla" to set SteveCox to (URL of front window) return SteveCox If so, this should be Resolved Fixed.
Updated•20 years ago
|
Product: Core → Mozilla Application Suite
![]() |
||
Comment 9•16 years ago
|
||
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 10•16 years ago
|
||
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
![]() |
||
Comment 11•16 years ago
|
||
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
![]() |
||
Comment 12•16 years ago
|
||
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
![]() |
||
Comment 13•16 years ago
|
||
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
![]() |
||
Comment 14•16 years ago
|
||
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
![]() |
||
Comment 15•16 years ago
|
||
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
Comment 16•16 years ago
|
||
I've tried several variations but can't find one that returns the URL or Title from Firefox.
Blocks: 125419
Comment 17•10 years ago
|
||
Can someone contribute a step by step instruction showing the problem in Seamonkey and showing that the problem does not exist in other Browsers? 15 Years UNCONFIRMED are a very long time ...
Comment 18•10 years ago
|
||
For what it's worth this script works tell application "Safari" to set foo to (URL of current tab of front window) return foo whereas this one tell application "Firefox" to set foo to (name of front window) return foo "46407 – The current URL cannot be querried by another app" So in the intervening 15 years 1. tabbed browsing now exists 2. the idea that a window has a URL property seems to have gone away 3. the original program is not longer valid, now one has to write a program which is tab aware 4. Someone seems to have blocked access to the URL (which is bizarrely bound to the name) in Firefox, I would guess as a security measure Where that leaves you I don't know. One could file a bug asking for Firefox to support tabs and uris similar to Firefox. But the original program report is very invalid at this point.
Comment 19•10 years ago
|
||
The word "tab" is not defined in Firefox, so any script attempting to use a tab won't even compile. I had to comment that line out. Safari successfully returns name, tab & document. Chrome successfully returns title & tab. Firefox only returns name.
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Component: UI Design → Shell Integration
OS: All → Mac OS X
Product: SeaMonkey → Firefox
Hardware: PowerPC → All
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•