"Pin to start" flyout should be positioned on top of the command

RESOLVED INCOMPLETE

Status

defect
RESOLVED INCOMPLETE
6 years ago
2 years ago

People

(Reporter: ywang, Unassigned)

Tracking

Trunk
x86
Windows 8.1

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [defect] p=0)

Currently the position of "Pin to start" is in the center of the screen(most of the time), sometimes the flyout appears in random location.

We need to make the flyout appear in context. It should be centered above the "Pin to start" command. 

It probably makes better sense to fix this after the combined app bar lands. 


"Flyouts should never be positioned in non-contextual places such as the center of the screen" - MSDN guidelines
Component: App Bar → Flyouts
Assignee: nobody → netzen
Whiteboard: p=1
Blocks: metrov1defect&change
No longer blocks: metrov1triage
Summary: "Pin to start" flyout should be positioned on top of the command → Change - "Pin to start" flyout should be positioned on top of the command
Whiteboard: p=1 → feature=change c=tbd u=tbd p=1
Priority: -- → P5
Whiteboard: feature=change c=tbd u=tbd p=1 → feature=change c=tbd u=tbd p=0
For future consideration.  Points = 1.
Priority: P5 → --
Assignee: netzen → nobody
No longer blocks: metrov2defect&change
Summary: Change - "Pin to start" flyout should be positioned on top of the command → "Pin to start" flyout should be positioned on top of the command
Whiteboard: feature=change c=tbd u=tbd p=0 → [feature] p=0
Summary: "Pin to start" flyout should be positioned on top of the command → Defect - "Pin to start" flyout should be positioned on top of the command
Whiteboard: [feature] p=0 → [defect] p=0
Duplicate of this bug: 951033
Summary: Defect - "Pin to start" flyout should be positioned on top of the command → "Pin to start" flyout should be positioned on top of the command
OS: Windows 8 Metro → Windows 8.1
Mass close of bugs in obsolete product https://bugzilla.mozilla.org/show_bug.cgi?id=1350354
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.