"Delete from History" and "Dismiss" buttons from context menu are wrongly positioned

VERIFIED FIXED

Status

()

Firefox
Activity Streams: General
VERIFIED FIXED
2 years ago
2 years ago

People

(Reporter: VladB, Unassigned)

Tracking

Trunk
x86_64
All
Points:
---

Firefox Tracking Flags

(firefox50 affected)

Details

Attachments

(1 attachment)

(Reporter)

Description

2 years ago
Created attachment 8761943 [details]
different context menus

[Affected versions]:
- Firefox 45.0 and up
- Activity Stream 1.0.19-dev

[Affected Platforms]:
- All Windows
- All Linux
- All Mac OS

[Prerequisites]:
- Latest Activity Stream add-on version (1.0.19) was previously installed on a profile.
- Have two profiles: profile A has a Firefox account, profile B doesn't have a Firefox account.
- Have enough history so that the "Top Sites", "Highlights", "History" areas are populated with visited websites.

[Steps to reproduce]:
1. Open the browser with the profile A from prerequisites.
2. Open a New Tab so the Activity Stream New Tab page is displayed.
3. Move the mouse cursor over a visited item.
4. Click on "..." button.
5. Observe the context menu.
6. Open the browser with the profile B from prerequisites.
7. Open a New Tab so the Activity Stream New Tab page is displayed.
8. Move the mouse cursor over a visited item.
9. Click on "..." button.
10. Observe the context menu.

[Expected result]:
- "Delete from History" and "Dismiss" buttons are displayed under the second separator line.

[Actual result]:
- For the profile with the Firefox account, "Delete from History" and "Dismiss" buttons are displayed above the second separator line.
(Reporter)

Updated

2 years ago
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → FIXED
(Reporter)

Comment 2

2 years ago
This issue has been tested on latest Firefox release v47.0 and latest Nightly 50.0a1 (Build ID: 20160616163918 ) using Activity Stream v1.1.0 and it is no longer reproducible.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.