Closed
Bug 1152908
Opened 10 years ago
Closed 10 years ago
Middle-clicking on a reading list item should open it in a new tab
Categories
(Firefox Graveyard :: Reading List, defect, P2)
Tracking
(firefox40 verified)
VERIFIED
FIXED
Firefox 40
Tracking | Status | |
---|---|---|
firefox40 | --- | verified |
People
(Reporter: jaws, Assigned: florian)
References
(Blocks 1 open bug)
Details
(Whiteboard: [reader-ui])
Attachments
(1 file)
(deleted),
patch
|
Gijs
:
review+
|
Details | Diff | Splinter Review |
STR:
Add a page to the reading list
Middle click on the item
ER:
The page opens in a new tab
AR:
A focus rect is shown on the item, but nothing else happens.
Reporter | ||
Updated•10 years ago
|
Priority: -- → P2
Updated•10 years ago
|
Flags: firefox-backlog+
Updated•10 years ago
|
Assignee: nobody → florian
Status: NEW → ASSIGNED
Iteration: --- → 40.2 - 27 Apr
Points: --- → 3
Flags: qe-verify?
Assignee | ||
Updated•10 years ago
|
Flags: qe-verify? → qe-verify+
Assignee | ||
Comment 1•10 years ago
|
||
Here is where I found the explanation of why this was not working:
(John Keiser (jkeiser) from bug 184051 comment #0)
> We are not supposed to fire the onclick event at content for middle click or
> right click, but we still need the document to receive the event so that our
> normal handlers can deal with it. So we hack the event by setting the flag
> NS_EVENT_FLAG_NO_CONTENT_DISPATCH, and not dispatching the event to content.
Attachment #8592889 -
Flags: review?(gijskruitbosch+bugs)
Updated•10 years ago
|
Attachment #8592889 -
Flags: review?(gijskruitbosch+bugs) → review+
Assignee | ||
Comment 2•10 years ago
|
||
Comment 3•10 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 40
Updated•10 years ago
|
QA Contact: andrei.vaida
Comment 4•10 years ago
|
||
Verified fixed on Nightly 40.0a1 (2015-04-24) using Windows 7 (x64), Ubuntu 14.04 (x64) and Mac OS X 10.9.5.
Status: RESOLVED → VERIFIED
Updated•9 years ago
|
Product: Firefox → Firefox Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•