Closed Bug 84363 Opened 23 years ago Closed 11 years ago

WWW_ListWindows and WWW_GetWindowInfo DDE topics not implemented

Categories

(Toolkit :: Startup and Profile System, defect)

Product:
Toolkit
Component:
Startup and Profile System
Platform:
x86
Other
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WONTFIX

People

(Reporter: law, Unassigned)

Details

(Keywords: helpwanted) 

Per discussion in bug 25699, we need to implement these additional DDE topics
that are used by popular third-party applications that would like to integrate
functionality with Mozilla.

These aren't too hard to implement.  We can use the window mediator to enumerate
the browser windows.  We assign those arbitrary "window IDs" (e.g., some unique
per-window value).  For WWW_GetWindowInfo, we need to enumerate again, looking
for the navigator window with that unique attribute (to validate it) and then
exract the necessary information.

Examples of code that formats the response can be found in dde.cpp from Mozilla
Classic (http://lxr.mozilla.org/classic/source/cmd/winfe/dde.cpp).  The code all
goes in nsNativeAppSupportWin.cpp
(http://lxr.mozilla.org/seamonkey/source/xpfe/bootstrap/nsNativeAppSupportWin.cpp).

A great introductory Mozilla hacking project!
One word of advice: beware the wrath of Mozilla conspiracy-theorists (see bug
71270).  These topics enable any Win32 application to monitor the web pages that
are visited.
Keywords: helpwanted
Setting target milestone.  Not currently planned.
Target Milestone: --- → Future
Without this feature, ClipMate can't get the URL of a clip from the browser. 
(It can with Netscape 4.x, IE, and Opera.)  Or maybe you can suggest an
alternative method.  I'll paste in below my correspondence with ClipMate's
creator, Chris Thornton (mailto:chris@thornsoft.com).  --Don Maxwell
------------
Hello Don,

Netscape has de-supported the DDE topic that used to let me query it
to ask what URL it was looking at.  It's not present in Netscape 7.
(For reference, it's the WWW_GetWindowInfo DDE topic).

I have been hoping for a long time that they would support the "HTML
Clipboard Format" datatype, which is what I use to get the URLS from
IE.  Unfortunately, they implemented their HTML Clipboard Format
without the "Source URL" identifier.  Which makes me wonder why they
bothered at all.  It's useless without the Source URL.

So as Netscape adds things like skins, one must question where they
are really going with this.  They're removing functionality that dates
all the way back to Spyglass, and making half-hearted attempts at
interoperability.

In short, there is no way for me to determine the Source URL, and
there isn't anything that I can do about it.  If you really care about
using Netscape as a browser, I'd recommend writing to them and
encouraging them to concentrate less on "skins", and more on core
functionality.

-- 
-- Sincerely, Chris Thornton mailto:chris@thornsoft.com President, Thornsoft
Development, Inc. (Please include entire text when replying to tech support)
Saturday, November 2, 2002, 10:58:49 AM, you wrote: DM> Hm. I was hoping that
ClipMate 6 would be able to display the source DM> URLs for clips made in
Netscape and Mozilla--but nope. DM> Am I missing something? Or is it a problem
with those apps? Netscape DM> 4.xx is okay, and so are IE (which I decline to
use). DM> --Don Maxwell
QA Contact: sairuh → pmac
I've checked that with Mozilla 1.4b and NS 7.0, the WWW_GetWindowInfo
DDE topics seems be supported. But WWW_ListWindows still cann't work.
Though DDE is only partially support in the latest Mozilla/NS, this topic
(WWW_ListWindows) should also be addressed. This will make it possible
to target an URL to a specific browser window.
Product: Core → Mozilla Application Suite
Keywords: qawanted
Assignee: law → jag
QA Contact: pmac
Target Milestone: Future → ---
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
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
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
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
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
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
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
This isn't supported yet.
http://mxr.mozilla.org/mozilla-central/source/toolkit/xre/nsNativeAppSupportWin.cpp#977

We need to implement "Window ID" system first.
Status: UNCONFIRMED → NEW
mcsmurf, do we have any plans on implementing any additional DDE stuff in SeaMonkey or does this bug belong in core/toolkit?
Don't think we plan that, needs to be fixed in toolkit/ afaik (toolkit/xre/nsNativeAppSupportWin.cpp).
Assignee: jag → nobody
Component: UI Design → Startup and Profile System
Product: SeaMonkey → Toolkit
QA Contact: startup
To anyone who wants to work on this bug: Please note Bug 513742, it looks like DDE code might go away.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.