Open
Bug 134582
Opened 23 years ago
Updated 5 months ago
unsupported X selection targets (supported by NS4)
Categories
(Core :: DOM: Selection, defect)
Tracking
()
NEW
People
(Reporter: jwz, Unassigned)
Details
(I'm sure I picked the wrong component, but I don't
know which component means "X Front End".)
There are a number of selection targets that were
supported by previous versions of Navigator that
are now unsupported by Mozilla.
The most important one is FILE_NAME -- I have scripts
that want to grab the selection, and the URL or file that
it came from. Mozilla no longer provides this info.
Here's a table comparing the two.
Selection: Netscape 4.78: Mozilla 0.9.9:
These are correct:
TEXT "PM" "PM"
STRING "PM" "PM"
COMPOUND_TEXT "PM" "PM"
These are wrong in Mozilla 0.9.9:
LENGTH 2 (none)
TIMESTAMP 0xEF2CBCF1 (jan 1961??) 0
FILE_NAME "http://..." (none)
OWNER_OS "Linux" (none)
HOST_NAME "grendel.jwz.org" (none)
PROCESS 20237 (pid) (none)
USER "jwz" (none)
CLASS "Netscape" (none)
NAME "netscape-navigator" (none)
CLIENT_WINDOW 0x0140050B (X window id) (none)
And (for completeness) these are new to Mozilla:
UTF8_STRING (none) "PM" (as 16-bit characters)
text/unicode (none) "PM" (as 16-bit characters)
text/html (none) "<font" ...etc...
(as 16-bit characters)
text/_moz_htmlcontext (none) "<html" ...etc..
(as 16-bit characters)
text/_moz_htmlinfo (none) "0,0" (as 16-bit characters)
To test this stuff, go to an XEmacs *scratch* buffer and type
(x-get-selection-internal 'PRIMARY 'TARGETS) and so on, while
the selection is owned by another app.
Comment 1•23 years ago
|
||
This sounds like a blizzard bug.
/be
Assignee: joki → blizzard
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 2•23 years ago
|
||
I've never hacked on selection, that's all been pavlov. I don't mind hanging on
to the bug but I'm not going to get to it any time soon.
Component: Event Handling → XP Toolkit/Widgets
Updated•23 years ago
|
Summary: unsupported X selection targets: regression from NS4 → unsupported X selection targets (supported by NS4)
Reporter | ||
Comment 3•23 years ago
|
||
See also bug 136776, wherein it is noted that the only *other* way to get the
browser to tell you what page it's looking at is *also* no longer implemented.
Updated•16 years ago
|
QA Contact: madhur → xptoolkit.widgets
Comment 4•3 years ago
|
||
The bug assignee didn't login in Bugzilla in the last 7 months.
:enndeakin, could you have a look please?
For more information, please visit auto_nag documentation.
Assignee: blizzard → nobody
Flags: needinfo?(enndeakin)
Comment 5•3 years ago
|
||
I presume this is no longer relevant but let's just move over to a slightly more better component. I think it is referring to the data available in the selection buffer.
Component: XUL → DOM: Selection
Flags: needinfo?(enndeakin)
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•