electron

I need to build an app where the user can open PDF files within the app -- i.e. not by opening a new browser window. I would need to implement a back button and possibly some overlays over the PDF. Does anyone know if there's a good way to do this in Electron? If you're OK with UI provided by chrome PDF extension you can use it from electron. See this question const {app, BrowserWindow} = require('electron') app.once('ready', () => { let win = new BrowserWindow({ webPreferences: { plugins: true } }) win.loadURL(__dirname + '/test.pdf') }) Note, that electron's native PDF support is available

I am using Electron module mdns and I am getting this error A JavaScript error occurred in the main process Uncaught Exception: Error: Module version mismatch. Expected 49, got 48. at Error (native) at process.module.(anonymous function) [as dlopen] (ELECTRON_ASAR.js:167:20) at Object.Module._extensions..node (module.js:568:18) at Object.module.(anonymous function) [as .node] (ELECTRON_ASAR.js:167:20) at Module.load (module.js:458:32) at tryModuleLoad (module.js:417:12) at Function.Module._load (module.js:409:3) at Module.require (module.js:468:17) at require (internal/module.js:20:19) at

In Electron, I have my main process opening a BrowserWindow. The BrowserWindow loads one html page and then the same window eventually loads another html page. main.js var mainWindow; global.mainState = { settings: {} } mainWindow = createWindow('main', { width: 1000, height: 800, }); if (curState == 'load') { mainWindow.loadURL(`file://${__dirname}/interface/load.html`, {}) } if (curState == 'login') { mainWindow.loadURL(`file://${__dirname}/interface/login.html`, {}) } load.html const remote = require('electron').remote; var testGlobal = remote.getGlobal('mainState') testGlobal.settings =

I'm trying to print a generated HTML document to PDF. The document itself can hold multiple pages. Every page is built up like this: <!-- Header --> <!-- Content --> <!-- Footer --> All three look fine on every page. The only problem is that the footer won't stick at the bottom... The footer will always catch up with the last element of the page. As long as the page is filled with enough content the footer will be at the bottom as you would expect it to be. Here is my CSS: .docFooter{ display: -webkit-box; display: -ms-flexbox; display: flex; -webkit-box-pack: justify; -ms-flex-pack: justify;

I am creating an electron app that accesses a url. And when navigated to the URL the user clicks on a button and are redirected to a URL that displays this pop up in Chrome. How can I enable/show this popup in electron? It doesn't seem to enable it by default. What you see on the picture is that Chrome opens a popup for handle authentication event. However, Electron doesn't make such popup by default, as it stated in the documentation of 'login' event The default behavior is to cancel all authentications, to override this you should prevent the default behavior with event.preventDefault() and

I have an image file in the same directory as my login.vue component (which is where the following code is located). But, when I try this code, the image will not load: <div background="benjamin-child-17946.jpg" class="login" style="height:100%;"> I'm getting this error: Failed to load resource: the server responded with a status of 404 (Not Found) This is strange, because I can see in my terminal that my image is in the same directory as login.vue. I am using webpack to compile. What might be causing this? Your primary issue is that single file components are compiled and the compiled script

We're using electron-packager to bundle up and distribute the front-end of our web application. We need to be able to pass in the host and port of the server to the electron front-end for connecting. When we launch via electron main.js --host blah --port 8080 it works. Once it's packaged, we run via ./MyApp --host blah --port 8080 and it doesn't work. This is bad because we don't want customers to need to install electron/npm itself. Also worth noting is that this happens whether we package the app in an asar archive or not. Any ideas on things we could try, or if we're trying to go about this