Closed
Bug 747910
Opened 12 years ago
Closed 5 years ago
Meta: Finish Multi-touch
Categories
(Tracking Graveyard :: Kilimanjaro, defect)
Tracking Graveyard
Kilimanjaro
Tracking
(blocking-kilimanjaro:+)
RESOLVED
INACTIVE
blocking-kilimanjaro | + |
People
(Reporter: dcm, Unassigned)
References
Details
(Keywords: meta, productwanted, Whiteboard: [k9o:p1:fx15])
This is a tracking bug to track the work needed to finish the work, past our first passes, at supporting multi-touch for mobile (and Win7 & 8?) In addition to the multi-touch support, gesture support should also be finished. More scope to follow in blocking bugs.
Reporter | ||
Updated•12 years ago
|
Whiteboard: [k9o:p1:fx15]
Updated•12 years ago
|
OS: Windows 2000 → All
Hardware: x86 → All
this is a duplicate of bug 548100 please close
Comment 3•12 years ago
|
||
Please make sure any blockers for this (or bug 548100) that may impact developer docs get the dev-doc-needed keyword added.
Updated•12 years ago
|
blocking-basecamp: --- → ?
Comment 4•12 years ago
|
||
Dave, there are no blocking bugs here. Can you please add the bugs for the various parts? Or: Who's the engineering lead for this work? Maybe they know? Cc'ing Olli and Felipe, who I have both had multiple touches on the multitouch code once upon a time.
Updated•12 years ago
|
blocking-kilimanjaro: --- → ?
Comment 5•12 years ago
|
||
k9o+ as this is a top level requirement called out in the product plan.
blocking-kilimanjaro: ? → +
Comment 6•12 years ago
|
||
(In reply to Lawrence Mandel [:lmandel] from comment #5) > k9o+ as this is a top level requirement called out in the product plan. Its called out but with no rationale or specific actions. Need product to outline the rational here (presumably for apps?).
Keywords: productwanted
Updated•12 years ago
|
blocking-basecamp: ? → ---
Comment 7•5 years ago
|
||
Closing inactive bugs in Tracking::Kilimanjaro
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INACTIVE
Updated•5 years ago
|
Product: Tracking → Tracking Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•