i want to use opera for a web based application that needs to run in kiosk mode and i tried chrome but some features like npapi plugin is disabled in chome that's why i need to run my web-based app on opera but i am finding difficult to run opera in kiosk mode,i tried /kioskmode, -kioskmode, /k in shortcut of opera("C:\Program Files (x86)\Opera\launcher.exe" /KioskMode) but it's not working for me.Am i doing something wrong? According to their link http://help.opera.com/Windows/12.10/en/kiosk.html This should work right?
You can use nwjs. Near nwjs.exe create package.json with next options:
{
"main": "<web app url>",
"name": "kiosk example",
"description": "kiosk example",
"version": "0.0.1",
"window": {
"toolbar": false,
"frame": false,
"resizable": false,
"show": true,
"kiosk": true,
"title": "kiosk example"
},
"webkit": {
"plugin": true
},
"chromium-args": "--force-gpu-rasterization"
}
Also, I recommend you to create kiosk user and set nwjs.exe as shell for this user. Windows 7 and early:
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Winlogon]
"Shell"="C:\\full\\path\\to\\nwjs.exe>"
Windows 8 and later:
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\System]
"Shell"="C:\\full\\path\\to\\nwjs.exe>"
Related
I have a legacy Google Chrome installable Apps packaged with NWJS as a standalone app.
I were using NWJS version 0.37.3 but now had to upgrade to last 0.56.0 because of Big Sur compatibility problems.
Now the problem is that the app generated with last NWJS sdk don't mantain old Google chrome app ID but got a new ID (testable in console with chrome.runtime.id).
So upgrading installed apps I were loosing old local data (local files, database, settings etc).
In manifest.json I have a "key" field with the app key that in old 0.37.3 was responsible to maintain chrome.runtime.id.
How I can keep using the same chrome.runtime.id with new NWJS SDK or any workaround to not loose existing local data?
My current manifest.json
{
"key": "MIGfM....B",
"name": "MyApp",
"description": "my app",
"version": "309",
"manifest_version": 2,
"default_locale": "en",
"nodejs": true,
"permissions": [
"<all_urls>",
"storage",
"browser",
"unlimitedStorage",
{
"fileSystem": ["write", "retainEntries", "directory"]
},
"videoCapture",
"nativeMessaging",
"webview"
],
"icons": {
"16": "images/favicon/favicon-16x16.png",
"128": "images/favicon/apple-icon-128x128.png"
},
"app": {
"background": {
"scripts": [
...
]
}
},
"chromium-args": "--ignore-certificate-errors",
"build": {
"appId": "my.app",
"nwFlavor": "sdk",
"output": "../package/",
"nwVersion": "0.56.0",
"outputPattern": "${NAME}-${VERSION}-${PLATFORM}-${ARCH}",
"targets": ["zip"],
"win": {
"icon": "images/favicon/win-app.ico",
"copyright": "..."
},
"mac": {
"icon": "images/favicon/mac/icon.icns",
"copyright": "..."
},
"nsis": {
"icon": "images/favicon/win-app.ico"
},
"excludes": ["**/bower_components", "**/bower_components/**/*"]
}
}
I'm not familiar with this, but seems like something that should be documented. I've created an open spreadsheet (anyone with link can edit), that documents all the versions of NW.js and their details. The data comes from the official versions list. And I've manually added the chrome.runtime.id's for some versions I had locally. I think some scripting will be needed to flesh out the rest of the versions, but at least there is now a public place for the info to go to.
https://docs.google.com/spreadsheets/d/16Y-mH5GzFL8BXLXCwzkvKQ7Vg4t4c2Jt6WgZaAAZPwc/edit?usp=sharing
I'm trying to launch chrome browser on emulator but not able to do so. I tried with below capabilities but its going in hung state.
{
"deviceName": "Pixel 2 API 28",
"udid": "emulator-5554",
"platformName": "Android",
"platformVersion": "9.0",
"automationName": "UiAutomator1",
"androidPackage": "com.android.chrome",
"browserName": "Chrome",
"unicodeKeyboard": true,
"resetKeyboard": true
}
I'm trying to trigger chrome mini-infobar for my PWA
I have checked that the page meets the add to home screen criteria, it also successfully passes
PWA audit in chrome devtools:
The web app is not already installed (not installed)
Meets a user engagement heuristic (currently, the user has interacted with the domain for at least 30 seconds) (nothing happens after 30s)
Includes a web app manifest that includes:
short_name or name icons must include a 192px and a 512px sized icons
start_url display must be one of fullscreen, standalone, or minimal-ui (yes)
Served over HTTPS (required for service workers) (yes)
Has registered a service worker with a fetch event handler (yes)
The most strange thing is that mini-infobar IS shown to the user when testing from local machine (using remote devices port forwarding). But it stops working after I upload it to the web.
My manifest:
{
"name": "Dota 2 counterpick",
"short_name": "Counterpick",
"start_url": "/?utm_source=homescreen",
"icons": [{
"src": "/android-chrome-192x192.png",
"sizes": "192x192",
"type": "image/png"
}, {
"src": "/android-chrome-512x512.png",
"sizes": "512x512",
"type": "image/png"
}],
"theme_color": "#ffffff",
"background_color": "#ffffff",
"display": "standalone"
}
Service worker
self.addEventListener('fetch', function(event) {
event.respondWith(
caches.match(event.request).then(function(response) {
return response || fetch(event.request);
})
);
});
I tried unregistering service worker, resetting site data, relaunching chrome but no luck. I'm using Chrome 71 on Android 8.1
PWA url: https://counterpick.herokuapp.com
Since my chrome update, I cannot make any nightwatch tests work on Windows 10.
At first the system simply couldn't set values. So I updated to the latest nightwatch, then updated to latest chromedriver.exe and latest selenium jar.
Now the test simply shows data: in the url of the driven browser instead of loading the page. There is also a "disable developer mode extensions" popup and a warning that "--ignore-certificate-errors" is no longer supported.
Any ideas what I'm supposed to have done?
Chromedriver.exe version: 2.38
Selenium Standalone Server: selenium-server-standalone-3.9.1.jar
Nightwatch version: nightwatch#0.9.21
Thanks for any help. Here's my config:
{
"src_folders": ["tests"],
"output_folder": "reports",
"custom_commands_path": "",
"custom_assertions_path": "",
"page_objects_path": "pages",
"globals_path": "globals",
"selenium": {
"start_process": true,
"server_path": "./lib/selenium-server-standalone-3.9.1.jar",
"log_path": "./reports",
"host": "127.0.0.1",
"port": 4444,
"cli_args": {
"webdriver.chrome.driver": "./lib/chromedriver.exe"
}
},
"test_settings": {
"default": {
"launch_url": "https://modaquote.com",
"selenium_port": 4444,
"selenium_host": "localhost",
"silent": true,
"desiredCapabilities": {
"browserName": "chrome",
"javascriptEnabled": true,
"acceptSslCerts": true
}
}
}
}
You have to update Chromedriver to match your new version of Chrome. It should fix there issues.
I followed the online tutorial for constructing a bot in Visual Studio and deploying it Azure, and so far that seems to have worked. Now I want to add this bot to Microsoft Teams via the "Sideload a bot or tab" method. The online tutorial has NO explanation for what I need to do so I need some help. Here is the manifest.json I was currently trying to upload in a zip folder. Please help, I don't know how this process works.
{
"$schema": "https://statics.teams.microsoft.com/sdk/v1.0/manifest/MicrosoftTeams.schema.json",
"manifestVersion": "1.0",
"version": "1.0.0",
"id": "a5db14e6-8adf-445b-a0aa-daadc5e155eb",
"packageName": "com.testbot20170525114049",
"developer": {
"name": "Megan",
"websiteUrl": "https://website.com/",
"privacyUrl": "https://website.com/privacy",
"termsOfUseUrl": "https://website.com/app-tos"
},
"name": {
"short": "Botty"
}
"description": {
"short": "A sample bot to test the bot upload process"
}
"bots": [
{
"botId": "a5db14e6-8adf-445b-a0aa-daadc5e155eb",
"needsChannelSelector": "true",
"scopes": [ "team", "personal" ]
}
]
}
Enable Public Developer Preview. The v1.0 manifest is fully supported in that mode, and while it may work in the public version, for now I'd switch to developer preview mode.
Make sure your manifest follows the v1.0 format. While your schema is close, there are a few required fields missing:
description.full
icons.outline
icons.color (note currently there is a 2k limit on file size)
accentColor
Zip the manifest and icons into a sideloadable package. Make sure the manifest.json is at the top level.
Follow the sideload instructions.