Skip to content
This repository has been archived by the owner on Mar 5, 2019. It is now read-only.

Opening address or searching in the "Address bar"(Location bar) by hitting enter key doesn't open new tab on FF 50. #115

Closed
kissglay opened this issue Nov 1, 2016 · 12 comments
Labels
Projects

Comments

@kissglay
Copy link

kissglay commented Nov 1, 2016

After upgrading to FF50, opening address or searching in the address bar and hitting enter doesn't open new tab, and instead, it opens them in the current tab. ("Open new tabs for" option is properly set)
(Using mouse to select the entry or click the arrow icon to the right of address bar works just as expected)

@kissglay kissglay changed the title Address or searching in the "Address bar"(Location bar) doesn't open new tab on FF 50. Opening address or searching in the "Address bar"(Location bar) and hitting enter key doesn't open new tab on FF 50. Nov 1, 2016
@kissglay kissglay changed the title Opening address or searching in the "Address bar"(Location bar) and hitting enter key doesn't open new tab on FF 50. Opening address or searching in the "Address bar"(Location bar) by hitting enter key doesn't open new tab on FF 50. Nov 1, 2016
@liuxb
Copy link

liuxb commented Nov 16, 2016

刚升级到50,发现有同样情况,盼修正,谢谢!

@yfdyh000 yfdyh000 added the bug label Nov 16, 2016
@Guil211
Copy link

Guil211 commented Dec 4, 2016

Any update on that one? Thanks!

@irvinm
Copy link

irvinm commented Dec 17, 2016

Same issue here. Hoping for a workaround or fix.

@seiry
Copy link

seiry commented Dec 26, 2016

作者辛苦了thank U

@Guil211
Copy link

Guil211 commented Dec 29, 2016

Thanks for the fix, I appreciate the work during this time of year. However, the issue is not fixed for me. I still get the abnormal behavior (typing in address bar, pressing Enter results in page loading in current tab instead of in a new tab). Using FF50.1.0, TU2016.12.30 (though the name of the addon is still 2016.07.31, I do see today's date in the "last updated field). As far as I can tell, the addon installed correctly (had to disable signature requirement to force FF to install), but I keep wondering. Any suggestion? Cheers,

@yfdyh000
Copy link
Owner

@Guil211 Unless you use the firefox-50.1.0.en-US.win32-add-on-devel.installer edition, otherwise you can‘t install an unsigned addon on Fx50.1.0. I guess you did not get this latest version and I confirmed it to display the correct version in Add-ons Manager - it's details.

@yfdyh000
Copy link
Owner

p.s. Queue Position: 61 of 121 on AMO review.

@Guil211
Copy link

Guil211 commented Jan 2, 2017

That explains it, thanks. I thought I had managed to force the install, but looks like not. Any timeline to have it signed then? :)

@yfdyh000
Copy link
Owner

yfdyh000 commented Jan 2, 2017

I am also waiting, because I use the Beta channel. Queue Position: 54 of 115. There is no expected time.

If you are anxious to use it, auto-signing an unlisted add-on is probably feasible on AMO, using another UUID and no auto-update.

@habmalnefrage
Copy link

habmalnefrage commented Jan 10, 2017

Waiting too for signed tabutils as on FF 50 unsigned add-ons will not install even with xpinstall.signatures.required being set to false in about::config

@habmalnefrage
Copy link

an excellent workaround for unsigned add-ons:
http://www.ghacks.net/2016/08/14/override-firefox-add-on-signing-requirement/

@Guil211
Copy link

Guil211 commented Jan 13, 2017

Rejoice! The signed version has made its way through and is available on AMO/extension update.
@habmalnefrage thanks for the link, I'll keep it in mind for next time. Thanks again @yfdyh000 for the update, and cheers!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
Fix
Has release
Development

No branches or pull requests

7 participants