Nw.js: Still stuck on "Right-click to run Adobe Flash Player"

Created on 29 Apr 2017  ·  5Comments  ·  Source: nwjs/nw.js

Same issue as #5224, except that it only occurs for SWFs embedded in a website embedded in an iframe.

My setup:

  • Windows 10 x64
  • NW.js SDK v0.22.0
  • Adobe Flash Player 25

package.json:

{
    "name": "Test App",
    "main": "index.html"
}

index.html:

<!DOCTYPE html>
<html>
<head>
    <meta charset="utf-8" />
    <title>Test App</title>
</head>
<body>
    <iframe src="http://www.notdoppler.com/strikeforceheroes2.php" nwdisable nwfaketop width="800" height="600"></iframe>
</body>
</html>

In previous versions of NW.js, you could select "Always allowed to run" in chrome://plugins to bypass this, but this is no longer possible, as the Chrome team has removed chrome://plugins.

P2 bug triaged

Most helpful comment

Workaround:

chrome.contentSettings.plugins.set({
    primaryPattern: "<all_urls>",
    resourceIdentifier: { id: "adobe-flash-player" },
    setting: "allow"
});

Nevertheless, the bug should be fixed.

All 5 comments

I try on Windows 8/Linux with nwjs-sdk-v0.22.0. Flash works well. But it doesn't work on Windows 10, the result is same as the reporter.

I should mention that this is a regression. It worked fine (with a workaround) on v0.20.0

I encounter the same problem . I user " Window.open(url, [options], [callback])" replace "iframe".
when opened ther window,I found flash work well.
Ofcourse , It's not work with nwjs-sdk-v0.21.5.

Workaround:

chrome.contentSettings.plugins.set({
    primaryPattern: "<all_urls>",
    resourceIdentifier: { id: "adobe-flash-player" },
    setting: "allow"
});

Nevertheless, the bug should be fixed.

解决方法:

铬。contentSettings 。插件。集合({ 
  primaryPattern:“<all_urls>” ,
  resourceIdentifier:{  ID:“土坯-Flash播放器”  } ,
  设置:“允许” 
} );

尽管如此,该错误应已修复。

放在哪执行呢

Was this page helpful?
0 / 5 - 0 ratings