You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 27, 2022. It is now read-only.
beaker:// cannot access any of the usual chromium-based-browser chrome:// urls, not even chrome://version which seems to run on anything even say Etcher which is electron based.
I would like to be able to access chrome://flags, chrome://gpu, chrome://memory, and chrome://version for instance. I know that beaker is not built off of full chromium source code, just electron which is blink + node.js, so is that to blame? Will this be implemented later? I have seen other electron based browsers that had all or some of these implemented. It would especially be useful for debugging when graphics doesn't work, I.E. beaker is fine on alot of my machines, but fails to render WebGL on an AMD 6450 that runs WebGL fine on other browsers.
beaker:// cannot access any of the usual chromium-based-browser chrome:// urls, not even chrome://version which seems to run on anything even say Etcher which is electron based.
I would like to be able to access chrome://flags, chrome://gpu, chrome://memory, and chrome://version for instance. I know that beaker is not built off of full chromium source code, just electron which is blink + node.js, so is that to blame? Will this be implemented later? I have seen other electron based browsers that had all or some of these implemented. It would especially be useful for debugging when graphics doesn't work, I.E. beaker is fine on alot of my machines, but fails to render WebGL on an AMD 6450 that runs WebGL fine on other browsers.