Closed Bug 9679 Opened 26 years ago Closed 25 years ago

[feature] Toolbox D&D: Process drop

Categories

(Core :: XUL, enhancement, P3)

Product:
Core
Component:
XUL
Type:
enhancement

Tracking

()

Status:
RESOLVED WONTFIX
Milestone:
Future

People

(Reporter: trudelle, Assigned: mikepinkerton)

References

Details

(Keywords: helpwanted, qawanted, Whiteboard: 2 days)

Process drop 2 days pinkerton 0%
Mass changing all XPToolkit M11 feature 'bugs' to target as p3 enhancement for M11
Blocks: 9685
accepting bugs in bulk.
moving toolbox work to m12 to fit tree d&d in.
Whiteboard: 2 days
added estimated remaining duration in status whiteboard field
Blocks: 12666
No longer blocks: 9685
dividing up phillips qa contact bugs, he no longer works here
Blocks: 15774
Summary: sched: Toolbox D&D: Process drop → [feature] Toolbox D&D: Process drop
Target Milestone: M15 → M18
Not enough time left to do this, resolving as later, putting on help wanted radar.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Keywords: helpwanted
Resolution: --- → LATER
Rubber-stamping as Verified/Later. Will re-open bugs for reconsideration if evidence exists that feature omission is significant.
Status: RESOLVED → VERIFIED
reopening all latered bugs
Status: VERIFIED → REOPENED
Resolution: LATER → ---
Moving all latered bugs to M20 as ordered by project manager. Although these bugs are now open, assigned and targetted, XPToolkit has no plans to fix/implement them in the current release cycle, if ever.
Target Milestone: M18 → M20
Mass move of all M20 bugs to M30.
Mass moving M20 bugs to M30
Target Milestone: M20 → M30
Mass-moving all M20-M30 XPToolkit bugs to Future
Target Milestone: M30 → Future
`Process drop'? This is when you drop a document on an application's icon (or on its button in the Application switcher) and it opens, right? [Ping: This bug needs a new QA contact]
Keywords: qawanted
qa->jrgm
QA Contact: elig → jrgm
dropped feature
Status: REOPENED → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.