search

oxicuze / chrome-toolbox

Automatically exported from code.google.com/p/chrome-toolbox
0 stars 0 forks source link

When pressing enter in address bar with a URL in it, open the URL in a new tab seems to be broken #193

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Type a new URL in the address bar
2. Hit enter

What is the expected output? What do you see instead?
New tab is supposed to open. Tab opens in same window.

What version of the product are you using? On what operating system?
1.0.32. Chrome 29.0.1547.57 m Windows 7 Home Premium 64-bit

Original issue reported on code.google.com by m7c...@gmail.com on 23 Aug 2013 at 8:42

GoogleCodeExporter commented 9 years ago 
I am having the same problem. Chrome version 29.0.1547.57. Tried deleting and 
reinstalling Chrome Toolbox with no help. Windows 7 Pro 64 bit.

Original comment by kmackenz...@gmail.com on 24 Aug 2013 at 5:49

GoogleCodeExporter commented 9 years ago 
same problem, reported it here:
https://code.google.com/p/chrome-toolbox/issues/detail?id=194&q=dasjenige

tried reinstalling - no  use. seems that something is not working between 
google chrome engine and this extension.

Original comment by dasjen...@gmail.com on 27 Aug 2013 at 9:40

GoogleCodeExporter commented 9 years ago 
Are there any other extensions that will so the same thing?  I don't think 
anyone is supporting this extension anymore.

Original comment by gquir...@gmail.com on 28 Aug 2013 at 3:42

GoogleCodeExporter commented 9 years ago 
no, I think the support of this extension is still ongoing, there are threads 
in this forum with relatively new replies from the developers.
as for other extensions, here's the most interesting part: previously (before 
this issue started) I've tested 4 or 5 of them and kept them installed, but 
switched off. once this problem appeared, I tried switching each one of them on 
at a time - neither one worked! which makes me wonder if something's changed in 
google chrome itself and now prevents according scripts from working...

Original comment by dasjen...@gmail.com on 28 Aug 2013 at 2:37

GoogleCodeExporter commented 9 years ago 
That's the issue, it was written with older API's and Chrome depreciated the 
API's it's using from what I read.  So it sounds like they would have some 
major work to get it updated to the new API calls.

Original comment by gquir...@gmail.com on 28 Aug 2013 at 7:49

GoogleCodeExporter commented 9 years ago 
http://blog.chromium.org/2013/09/saying-goodbye-to-our-old-friend-npapi.html

Original comment by dbr...@gmail.com on 24 Sep 2013 at 1:02