Closed Bug 11830 Opened 25 years ago Closed 25 years ago

[FEATURE] sched: clipboard interface for seeing if anything is on clipboard

Categories

(Core :: XUL, defect, P3)

Product:
Core
Component:
XUL
Platform:
All
Linux
Type:
defect

Tracking

()

Status:
VERIFIED DUPLICATE of bug 13161

People

(Reporter: mikepinkerton, Assigned: pavlov)

References

Details

(Whiteboard: mac/win32 work done. waiting on gtk) 

sfraser needs a way to determine if there is anything on the clipboard so that we
can disable the Paste command if there isn't. This API needs to be added to
nsIClipboard, and probably there will need to be some FE-specific work done in
order to check the native clipboard w/out doing horrendous data copying.

cc'ing saari and danm because they both do win32 stuff. we can find an owner for
the win32 part later.
Status: NEW → ASSIGNED
Target Milestone: M10
m10 assigned.
Blocks: 9673
Whiteboard: ?? days
need estimated remaining duration in status whiteboard field
Whiteboard: ?? days → 2 days total with FE work
Blocks: 12669
Depends on: 13161
Depends on: 13162
Whiteboard: 2 days total with FE work → mac work done. waiting on gtk/win32.
mac work is done. waiting on gtk/win32.
Target Milestone: M10 → M11
subordinate bugs are M11, so this one is being moved to M11.
No longer blocks: 9673
Assignee: pinkerton → pavlov
Status: ASSIGNED → NEW
Whiteboard: mac work done. waiting on gtk/win32. → mac/win32 work done. waiting on gtk
firing over to pav since only gtk is left.
mass-moving most m11 bugs to m12
Mass-moving non-PDT+ bugs to M13
dividing up phillips qa contact bugs, he no longer works here
OS: All → Linux
Summary: sched: clipboard interface for seeing if anything is on clipboard → [FEATURE] sched: clipboard interface for seeing if anything is on clipboard
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
*** This bug has been marked as a duplicate of 13161 ***
Status: RESOLVED → VERIFIED
Developer [FEATURE] bug; rubber-stamping as Verified/DUPLICATE without
inspection.
Blocks: 23975
You need to log in before you can comment on or make changes to this bug.