Closed Bug 962815 Opened 6 years ago Closed 6 years ago

Dismissing pin site popup makes the pin button stay highlighted.

Categories

(Firefox for Metro Graveyard :: App Bar, defect, P2)

x86_64
Windows 8.1
defect

Tracking

(firefox28 verified, firefox29 verified)

VERIFIED FIXED
Firefox 29
Tracking Status
firefox28 --- verified
firefox29 --- verified

People

(Reporter: rsilveira, Assigned: emtwo)

References

Details

(Whiteboard: [release28] [defect] p=1)

Attachments

(1 file)

STR:
1. Navigate to a site and click "pin to start" on nav bar
2. Dismiss the popup by clicking somewhere in content outside the popup

Expected:
Pin button goes back to initial 'unselected' state.

Actual:
Pin button is in 'selected' state giving the impression that the tile was created, even though it wasn't. It only creates when you click 'pin to start' on the popup. Clicking on it unselects.
Whiteboard: [triage] [defect] p=0
Whiteboard: [triage] [defect] p=0 → [release28] [defect] p=0
Whiteboard: [release28] [defect] p=0 → [release28] [defect] p=1
Assignee: nobody → msamuel
Blocks: metrov1it23
No longer blocks: metrov1backlog
Status: NEW → ASSIGNED
Priority: -- → P2
QA Contact: jbecerra
Comment on attachment 8366671 [details] [diff] [review]
v1: Update pin button after pin decision is made

Review of attachment 8366671 [details] [diff] [review]:
-----------------------------------------------------------------

Looks good and works fine.
Attachment #8366671 - Flags: review?(rsilveira) → review+
https://hg.mozilla.org/integration/fx-team/rev/a24ad25815b9
Whiteboard: [release28] [defect] p=1 → [release28] [defect] [fixed-in-fx-team] p=1
https://hg.mozilla.org/mozilla-central/rev/a24ad25815b9
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Whiteboard: [release28] [defect] [fixed-in-fx-team] p=1 → [release28] [defect] p=1
Target Milestone: --- → Firefox 29
Verified as fixed on latest Aurora and latest Nightly with the STR from comment 0 using a Surface Pro 2 device.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.