Closed Bug 1296863 Opened 8 years ago Closed 8 years ago

Stop disabling the "New Tab" command in popups

Categories

(Firefox :: Tabbed Browser, defect, P3)

defect

Tracking

()

RESOLVED FIXED
Firefox 51
Tracking Status
firefox51 --- fixed

People

(Reporter: dao, Assigned: dao)

References

Details

Attachments

(1 file)

Attached patch patchSplinter Review
This was disabled in bug 470051 because it broke the popup window. Since then, we've fixed BrowserOpenTab and openUILinkIn to do the right thing here. This way we can also simplify the code from bug 528005 by letting <key id="key_newNavigatorTab"> call BrowserOpenTab directly but without the event.
Attachment #8783198 - Flags: review?(gijskruitbosch+bugs)
Attachment #8783198 - Flags: review?(gijskruitbosch+bugs) → review+
Pushed by dgottwald@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/d35635870180 Stop disabling the "New Tab" command in popups. r=gijs
Pushed by gijskruitbosch@gmail.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/2beb0d486fc6 followup: don't break reserved-ness of accel-t to open tabs, rs=bustage
I pushed a followup to fix a breaking test that checked that accel-t was still "reserved" by the browser, which is controlled by the <command> rather than the <key> (which I don't really follow, but OK...) so I added a second <command> that the key handler invokes and made that reserved=true (too). Let me know if this makes sense (thinking about it, maybe we can remove the reserved keyword off the original command element? Really, these attributes should be on the keys rather than the commands, IMO...).
Flags: needinfo?(dao+bmo)
Followup does appear to have fixed the failures I was seeing, thanks Gijs :)
(In reply to :Gijs Kruitbosch from comment #3) > I pushed a followup to fix a breaking test that checked that accel-t was > still "reserved" by the browser, which is controlled by the <command> rather > than the <key> (which I don't really follow, but OK...) so I added a second > <command> that the key handler invokes and made that reserved=true (too). Thanks. > Let me know if this makes sense (thinking about it, maybe we can remove the > reserved keyword off the original command element? Really, these attributes > should be on the keys rather than the commands, IMO...). Yes, we should move them to the key elements.
Flags: needinfo?(dao+bmo)
Depends on: 1297342
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 51
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: