794135 - StartUI and autocomplete tiles should support right-click and long-tap context menus

Status: RESOLVED WONTFIX

(Firefox for Metro Graveyard :: General, defect)

Comment 1

[Matt Brubeck (:mbrubeck)]

Long-term, I wonder if we should implement the start UI as an HTML page that we actually load into the browser.  We might need to change how it interacts with the urlbar autocomplete code, but we'd get things like scrolling, right-clicking, and other interactions for free.

Comment 2

[Jim Mathies [:jimm]]

(In reply to Matt Brubeck (:mbrubeck) from comment #1)
> Long-term, I wonder if we should implement the start UI as an HTML page that
> we actually load into the browser.  We might need to change how it interacts
> with the urlbar autocomplete code, but we'd get things like scrolling,
> right-clicking, and other interactions for free.

I like the idea of html assuming we make a final decision on e10s and we decide to go in-process.

If we decide to go out-of-process, I think everything we display in content should be in an out-of-process tab so we can remove all the special case code for dealing with in-process "chrome" content in html. In which case we may want the start screen in chrome for performance reasons.

Comment 3

[Matt Brubeck (:mbrubeck)]

It sounds like we are going to use the appbar for context commands on tiles (bug 800996), rather than a more traditional context menu.  For example, see the wireframes attached to bug 808770.