chromium-args not apply

[icode]

"chromium-args" : "--enable-webgl --ignore-gpu-blacklist"

not support , mast use nw . --enable-webgl --ignore-gpu-blacklist

node-webkit-v0.7.1-linux-x64

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

[Mithgol]

Please mention your node-webkit's version, and operating system version, and paste your entire package.json here.

[icode]

node-webkit-v0.7.1-linux-x64

{ "name" : "brokermark", "main" : "views/signin.html", "user-agent" : "Mozilla/5.0 (Linux; Windows; Mac) AppleWebKit/535.19 (KHTML, like Gecko) BrokerMarkPcClient/1.0", "chromium-args" : "--enable-webgl --ignore-gpu-blacklist", "window" : { "transparent": true, "position" : "center", "show" : false }, "single-instance": true, "node-remote" : "http://report.xxxxxx.cn", "server" : { "url": "http://report.xxxxx.cn" }, "repository" : { "type": "svn", "url" : "http://192.168.1.164:9880/kmsvn/xn_web_yjbg/trunk/BrokerMarkPC" } }

thanks!

and node-webkt can be transparent?

[Mithgol]

Your package.json looks fine, the engine's version is relatively recent, and thus I have no idea of what's gone wrong.

Node-webkit cannot be transparent. (Such a feature was under construction in #132 though.)

[xavi]

I'm "implicitly" using node-webkit through Light Table. In its package.json, Light Table uses "chromium-args" : "--enable-webgl --ignore-gpu-blacklist", but I also found that these options don't seem to be honored.

I would be happy if this could be fixed (so that I can continue doing WebGL development without upgrading my hardware). Thanks!

[icode]

yes,"chromium-args" --enable-webgl --ignore-gpu-blacklist not applay command , i think it's bug ,i'm try 0.7 and 0.6 version,but not apply command. command defaults --disable-webgl,but --enable-webgl can't repleace

[vlados]

I agree! On a 100% NW does not apply this feauture

[Ivshti]

+1. NW 0.6.3 ignores it too

[mgcrea]

Just tested it against v0.9.2 and "chromium-args" : "--ignore-gpu-blacklist" does not work. @Mithgol any idea what file we should look/patch? Trying to make a HD5000 properly work.

[Mithgol]

I don't have an idea really. More than a hundred of GPU-blacklist-related issues are present in Chromium.

[denji]

Command line --args http://src.chromium.org/svn/trunk/src/content/public/common/content_switches.cc

[chriddyp]

Some other command line args: https://chromium.googlesource.com/chromium/src/+/38.0.2125.104/ui/gl/gl_switches.cc (reference: #3035 )

[sanemat]

"chromium-args": "--file-descriptor-limit=2000" does not work on nwjs-v0.12.2-osx-x64. $ nwjs target/ --file-descriptor-limit=2000 works well.

[vzr314]

Proxy server bypass also won't work with nwjs-v0.12.2. Seems like there is no chromium argument that actually works with nw.js

"chromium-args" : "--no-proxy-server"

[lapsio]

I also have issues with --no-proxy-server As I'm using i2p which takes like 5 min to load any website and I need to bypass proxy in 90% of apps i use, it makes nwjs pretty useless. I've managed to force set proxy from the inside of nwjs programmatically but it's more complex and annoying than cmd switch

[rafaelCMoura]

"chromium-args": "--disable-web-security" also won't work for nwjs 0.20.0.

{
  "name": "nwapp",
  "main": "index.html",
  "window": {
    "title": "nwapp",
    "icon": "favicon.ico",
    "toolbar": true,
    "frame": true,
    "width": 1100,
    "height": 800,
    "position": "center",
    "min_width": 700,
    "min_height": 600
  },
  "chromium-args": "--disable-web-security"
}

[humiston]

"chromium-args": "--url=http://nwjs.io" doesn't seem to work either, which is a 1-for-1 code sample from the NWjs documentation.

{
  "name": "nwjs_basic",
  "version": "1.0.0",
  "description": "",
  "main": "main.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1",
    "start": "./nwjs-sdk/nwjs.app/Contents/MacOS/nwjs ."
  },
  "author": "",
  "license": "ISC",
  "webkit": {
    "plugin": true
  },
  "chromium-args": "--url=http://nwjs.io"
}

[well0nez]

any news?

[Christywl]

The original issue is too old. If you meet any problem for some argument with the latest nwjs build, please file a new issue for it.

[07c0ff3a590b]

I'm building a Discord Client using NW.js and can't include the discord web page with iframe due to Same-origin policy. "chromium-args": "--disable-web-security" <- this thing still hasn't been fixed, and this issue was first reported in 2013.

Edit 1: I got it working by adding nwdisable nwfaketop attributes to the iframe. Now it works fine but you should still look into that chromium-args property.