Closed Bug 943417 Opened 11 years ago Closed 6 years ago

Get MetroInput/TabParent working with remote content

Categories

(Core Graveyard :: Widget: WinRT, defect)

Product:
Core Graveyard
Component:
Widget: WinRT
Platform:
x86_64
Windows 8.1
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: jimm, Unassigned)

References

Details

(Whiteboard: [feature] p=8) 

Looks like we're in pretty good shape here, except that there are issues with the MetroInput logic we currently use. TabParent always returns nsEventStatus_eConsumeNoDefault from dom touch events, so MetroInput mistakenly thinks content is always consuming and cancels apzc operations. Updating the apzc state is handled by TabParent as well, so MetroInput doesn't need to worry about it.

Not sure yet what the best way is to fix this, maybe we could return some information from the MozMouseHittest event we send to detect chrome indicating the event targets remote content, at which point MetroInput can change up it's logic and act appropriately.
Blocks: metrobacklog
Whiteboard: [feature] p=0
Component: Pan and Zoom → Widget: WinRT
Product: Firefox for Metro → Core
Whiteboard: [feature] p=0 → [feature] p=8
Summary: Get MetroInput working with remote content → Get MetroInput/TabParent working with remote content
We never shipped the metro support, closing!
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.