How can i launch chrome with the flags overlay-scrollbars ENABLED
and
calculate-native-win-occlusion DISABLED?
This is what i already tried:
chrome.exe -app=https://www.google.com --disable-calculate-native-win-occlusion
chrome.exe -app=https://www.google.com --overlay-scrollbars
chrome.exe -app=https://www.google.com --enable-overlay-scrollbars
Related
How do you run playwright with already installed local firefox?
NOTE!: I need to be able to specify the executable as I'm actually developing firefox so I may have a custom build. But, step one is getting it to run with an official build.
I tried this
// test.mjs
import { firefox } from 'playwright-core';
const executablePath = "C:\\Program Files\\Mozilla Firefox\\firefox.exe";
async function main() {
const browser = await firefox.launch({
executablePath,
headless: false,
});
}
main();
but I get a bunch of errors
❯ node .\test.mjs
node:internal/process/promises:246
triggerUncaughtException(err, true /* fromPromise */);
^
browserType.launch: Browser.enable): Browser closed.
==================== Browser output: ====================
<launching> C:\Program Files\Mozilla Firefox\firefox.exe -no-remote -wait-for-browser -foreground -profile C:\Users\gregg\AppData\Local\Temp\playwright_firefoxdev_profile-SMZBOF -juggler-pipe -silent
<launched> pid=10684
[pid=10684] <process did exit: exitCode=0, signal=null>
[pid=10684] starting temporary directories cleanup
=========================== logs ===========================
<launching> C:\Program Files\Mozilla Firefox\firefox.exe -no-remote -wait-for-browser -foreground -profile C:\Users\gregg\AppData\Local\Temp\playwright_firefoxdev_profile-SMZBOF -juggler-pipe -silent
<launched> pid=10684
[pid=10684] <process did exit: exitCode=0, signal=null>
[pid=10684] starting temporary directories cleanup
============================================================
at main (file:///C:/Users/gregg/src/gpuweb/cts/test.mjs:6:33)
at file:///C:/Users/gregg/src/gpuweb/cts/test.mjs:13:1 {
name: 'Error'
}
Tried MacOS as well as Window (of course on MacOS the path is different). This process works fine with Chrome
I believe your FF doesn't match the version Playwright supports,
The latest Playwright 1.29.2 supports 107, while the current FF is 108.
https://github.com/microsoft/playwright/issues/19337#issuecomment-1342247868
I'm downloading an executable via curl and try to run it afterwards. However, the Command object responsible for running it crashes with the following message: %1 is not a valid Win32 application. (os error 193)
Here's a snippet for better context:
let link = "https://download.bell-sw.com/java/18.0.1.1+2/bellsoft-jre18.0.1.1+2-windows-amd64-full.msi";
Command::new("curl")
.args(["-O", link])
.output()
.unwrap_or_else(|err| panic!("{err}"));
let program = format!("./{}", link.split('/').last().unwrap());
Command::new(program)
.output()
.unwrap_or_else(|err| panic!("{err}"));
A .msi file is not an executable. To install it you need to run msiexec.exe /i "c:\path\to\installer.msi" /qn.
To open the file like Explorer you would have to call the ShellExecute WinApi...
I have an Xamarin Android project. Now I cannot get the app started in the emulator anymore. After building the solution the emulator starts but the app is never deployed.
The output window in Visual Studio shows this:
Starting deploy EmulatorName ...
Starting emulator EmulatorName ...
C:\Users\USERNAME\AppData\Local\Android\Sdk\tools\emulator.EXE -partition-size 512 -no-boot-anim -avd EmulatorName -prop monodroid.avdname=EmulatorName
emulator: WARNING: Crash service did not start
emulator: WARNING: encryption is off
Hax is enabled
Hax ram_size 0x40000000
HAX is working and emulator runs in fast virt mode.
Emulator EmulatorName is running.
Waiting for emulator to be ready...
Deploying EmulatorName ...
Build started.
...
Using "AndroidZipAlign" task from assembly "C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MS
PackagedResources:
obj\Debug\android\bin\packaged_resources
SDCardDirectory:
External: False
ManifestTemplate: obj\Debug\android\AndroidManifest.xml
EnableInstantRun: False
InstantRunForceUploadApk: True
AndroidSdkPath: C:\Users\username\AppData\Local\Android\Sdk
AndroidNdkPath: C:\ProgramData\Microsoft\AndroidNDK64\android-ndk-r13b
JavaSdkPath: C:\Program Files (x86)\Java\jdk1.8.0_112
Found AndroidSdk at C:\Users\username\AppData\Local\Android\Sdk
Found AndroidNdk at C:\ProgramData\Microsoft\AndroidNDK64\android-ndk-r13b
Found AndroidTools at C:\Users\username\AppData\Local\Android\Sdk\tools
DEBUG RunShellCommand emulator-5554 getprop
TASK: GetProperties getprop completed?:[dalvik.vm.dex2oat-Xms]: [64m]
[dalvik.vm.dex2oat-Xmx]: [512m]
[dalvik.vm.heapsize]: [256m]
[dalv...
I have successfully used non gecko version of Firefox driver in headless mode but it has stopped working since I started using Selenium 3.0. What I do -
Start xvfb
Set webdriver.gecko.driver to path to gecko driver
Set Firefox binary display
System.setProperty("webdriver.gecko.driver", "path to geckodriver");
String Xport = System.getProperty("lmportal.xvfb.id", ":1"); final
FirefoxBinary firefoxBinary = new FirefoxBinary();
firefoxBinary.setEnvironmentProperty("DISPLAY", Xport);
WebDriver driver = new FirefoxDriver(firefoxBinary, null);
driver.get("https://www.google.com/");
But this launches the browser on visible screen and not on headless mode. What else do I need to to do to launch Firefox on xvfb?
Check if the xPort display value is set to :10 instead of :1
If it's not, just try setting it to :10 and recheck:
firefoxBinary.setEnvironmentProperty("DISPLAY", ":10");
I code signed my Installer/Uninstaller.exe using the below code:
signtool sign /f "mycert.pfx" /p Westell1 /t http://timestamp.verisign.com/scripts/timstamp.dll "Installer.exe"
After the code sign, when I tried to run the Installer.exe on Windows Vista 32/64 bit systems, the UAC screen not displaying the application name correctly ("Installer.exe"). It displays the application name as "Insf3e3.tmp".
Thanks in advance for the help
The text that UAC displays isn't the filename, it's the FileDescription field from the version resource in your executable.
If you're building Installer.exe yourself, you need to add a suitable version resource in your .rc file:
VS_VERSION_INFO VERSIONINFO
...
VALUE "FileDescription", "My Application"
If Installer.exe comes from an install builder, you need to look up how to set that string when you build your installer. For example, with InnoSetup you would say:
[Setup]
VersionInfoDescription=My Application