44648 - [FIX]Widgets have no ControlID (ControlID allways 0)

Status: RESOLVED WONTFIX

(Core :: XUL, defect, P1)

Description

[Roelof Berg]

When I'm looking in Spy++ for the Widget-ID's of the NS-Widgets (Classname: 
NetscapeWindowClass) there's allways the ID 0x00000000.

Because we're writing an e-commerce solution that has to communicate with the 
browser via SendMessage (support for many browsers with nearly the same code) 
we need Widget-ID's to support Netscape.

Please do us a favor and give your Widgets different, certain ID's.

Thanks

Comment 1

[Mike Pinkerton (not reading bugmail)]

cc'ing rod, danm, and hyatt. i have no idea what to do about this (not being a 
win32 weenie).

Comment 2

[rods (gone)]

This should be mine, it's a toolkit thing.

Comment 3

[rods (gone)]

Originally, this was an enhancement, but I think it is really a bug, each window 
SHOULD have its own unique ID. I am nominating this for nsbeta2 because it will 
help external tools work with mozilla. The fix is very low risk.

Comment 4

[Jay Patel [:jay]]

Putting on [nsbeta2-] radar. Not critical to beta2.  Adding "nsbeta3" keyword 
for consideration of a fix for that milestone. 

Comment 5

[Kevin McCluskey (gone)]

Marking nsbeta3-. We expect most of native widgets to go away over time. The 
correct solution is to create an API to allow external applications to get the 
information they need.

Marking WONTFIX

Comment 6

[Roelof Berg]

That's even (much) better (an API).

If you want some suggestions what API-Functions developers like us might need, 
feel free to ask.
mailto:[e-mail]

Thank you very much. (I'm very excited about BugZilla - every software vendor 
should have something similar ;-)

Comment 7

[Jonas Nagel]

Verify?