Closed
Bug 946339
Opened 11 years ago
Closed 11 years ago
Tap and hold does not highlight the targeted element
Categories
(Core :: Panning and Zooming, defect)
Tracking
()
People
(Reporter: vingtetun, Assigned: vingtetun)
References
Details
Attachments
(1 file)
(deleted),
patch
|
fabrice
:
review+
|
Details | Diff | Splinter Review |
In BrowserElementPanning.js we used to highlight the element after a certain amount of time.
Assignee | ||
Comment 1•11 years ago
|
||
Dale told me he may have a chance to look at it. So I'm assigning the bug to him ;)
Assignee: nobody → dale
Assignee | ||
Comment 2•11 years ago
|
||
Similarly to bug 942856 something has fixed it or will fix it. Hope I don't see it again.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
Assignee | ||
Updated•11 years ago
|
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Assignee | ||
Comment 3•11 years ago
|
||
Attachment #8344436 -
Flags: review?(dale)
Updated•11 years ago
|
Assignee: dale → 21
Comment 4•11 years ago
|
||
Comment on attachment 8344436 [details] [diff] [review]
wip.one.highlight.for.all.patch
Clearing review as I am not familiar with this code at all, however in testing it is working for me, I find the double active state strange (I get a persistent outline first, then a background if hovering)
Attachment #8344436 -
Flags: review?(dale)
Assignee | ||
Updated•11 years ago
|
Attachment #8344436 -
Flags: review?(fabrice)
Updated•11 years ago
|
Attachment #8344436 -
Flags: review?(fabrice) → review+
Assignee | ||
Comment 5•11 years ago
|
||
Assignee | ||
Comment 6•11 years ago
|
||
blocking-b2g: --- → 1.3+
Target Milestone: --- → mozilla28
Updated•11 years ago
|
Blocks: gaia-apzc-2
Updated•11 years ago
|
No longer blocks: gaia-apzc-2
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → FIXED
Comment 8•11 years ago
|
||
status-b2g-v1.3:
--- → fixed
status-firefox27:
--- → wontfix
status-firefox28:
--- → fixed
status-firefox29:
--- → fixed
Target Milestone: mozilla28 → mozilla29
You need to log in
before you can comment on or make changes to this bug.
Description
•