New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Beardedspice (2.2.3) no longer recognizes tabs of the latest stable version of Google Chrome (68.0.3440.75) #818

Closed
ottnorml opened this Issue Jul 26, 2018 · 5 comments

Comments

Projects
None yet
3 participants
@ottnorml

ottnorml commented Jul 26, 2018

First of all I want to thank you guys for creating this awesome tool.

Sadly since updating today to the latest Chrome version BeardedSpice no longer works with it.

Is this caused by the update and can someone reproduce the problem?

VLC player gets recognized and is working.
Safari (Version 11.0.1 (12604.3.5.1.1)) has the same problem like Chrome.

@mitchell486

This comment has been minimized.

Show comment
Hide comment
@mitchell486

mitchell486 Jul 27, 2018

I have the same issue currently with Google Chrome, Version 68.0.3440.75 (64-bit).

I have BeardedSpice 2.2.3 as well.

Anything else I can provide that would help more?

mitchell486 commented Jul 27, 2018

I have the same issue currently with Google Chrome, Version 68.0.3440.75 (64-bit).

I have BeardedSpice 2.2.3 as well.

Anything else I can provide that would help more?

@nelsonjchen

This comment has been minimized.

Show comment
Hide comment
@nelsonjchen

nelsonjchen Jul 28, 2018

Contributor

Ran this AppleScript (hacked from some stackoverflow post):

tell application "Google Chrome"
	tell tab 2 of window 1 to set RemoveBtRestriction to execute javascript ¬
		"javascript:alert('hello');"
end tell

Got this error:

screen shot 2018-07-27 at 10 03 28 pm

Found this menu option:

screen shot 2018-07-27 at 10 03 13 pm

Must be new for this generation of Safari/Chrome. Maybe some new Mac malware is exploiting this and these vendors have responded identically? Someone can probably dig up the issue in the Chromium tracker where they discuss this.

I guess there's an equivalent in Safari too but for now, check the box for the menu "Allow JavaScript from Apple Events" in the image above and it'll get back to working.

screen shot 2018-07-27 at 10 13 56 pm

So, there's the workaround. But for now, it looks like there should be a feature in BeardedSpice to respond to the scripting error and suggest enabling this.

Contributor

nelsonjchen commented Jul 28, 2018

Ran this AppleScript (hacked from some stackoverflow post):

tell application "Google Chrome"
	tell tab 2 of window 1 to set RemoveBtRestriction to execute javascript ¬
		"javascript:alert('hello');"
end tell

Got this error:

screen shot 2018-07-27 at 10 03 28 pm

Found this menu option:

screen shot 2018-07-27 at 10 03 13 pm

Must be new for this generation of Safari/Chrome. Maybe some new Mac malware is exploiting this and these vendors have responded identically? Someone can probably dig up the issue in the Chromium tracker where they discuss this.

I guess there's an equivalent in Safari too but for now, check the box for the menu "Allow JavaScript from Apple Events" in the image above and it'll get back to working.

screen shot 2018-07-27 at 10 13 56 pm

So, there's the workaround. But for now, it looks like there should be a feature in BeardedSpice to respond to the scripting error and suggest enabling this.

@nelsonjchen

This comment has been minimized.

Show comment
Hide comment
@nelsonjchen

nelsonjchen Jul 28, 2018

Contributor

Actually, it turned out to be not a coincidence:

https://github.com/beardedspice/beardedspice/wiki/Wont-Work-issue-after-Safari-Update-(9.1.1-and-later)

That page was made in January of 2017 for issue #402 .

Perhaps Chrome just finally implemented this as well.

Contributor

nelsonjchen commented Jul 28, 2018

Actually, it turned out to be not a coincidence:

https://github.com/beardedspice/beardedspice/wiki/Wont-Work-issue-after-Safari-Update-(9.1.1-and-later)

That page was made in January of 2017 for issue #402 .

Perhaps Chrome just finally implemented this as well.

@nelsonjchen

This comment has been minimized.

Show comment
Hide comment
@nelsonjchen

nelsonjchen Jul 28, 2018

Contributor

They flipped the default here and put it behind some feature flags and probably landed it this stable:

https://bugs.chromium.org/p/chromium/issues/detail?id=662548

Contributor

nelsonjchen commented Jul 28, 2018

They flipped the default here and put it behind some feature flags and probably landed it this stable:

https://bugs.chromium.org/p/chromium/issues/detail?id=662548

@ottnorml

This comment has been minimized.

Show comment
Hide comment
@ottnorml

ottnorml Jul 30, 2018

@nelsonjchen Thanks for finding out this workaround. It solved the problem. 😃
@1ps0 & @Stillness-2 I have added a page the FAQ section of the wiki.
@nelsonjchen I reused your image showing the Chrome menu.

ottnorml commented Jul 30, 2018

@nelsonjchen Thanks for finding out this workaround. It solved the problem. 😃
@1ps0 & @Stillness-2 I have added a page the FAQ section of the wiki.
@nelsonjchen I reused your image showing the Chrome menu.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment