Solution
This article addresses some Frequently Asked Questions (FAQs) about the LabVIEW WebBrowser Control introduced in LabVIEW 2026 Q1.
What framework is the WebBrowser Control built on?
The Web Browser Control is built on Chromium Embedded Framework (CEF).
As of February 2026, the version is 142.0.17 and has the same features as Chromium 142. The version will be updated in the future, as needed, to keep up with security patches.
The following Chromium options are disabled (either explicitly or automatically by using CEF):
- Extensions
- Component updates
- Metrics and telemetry
- Breakpad crash reporting
- Notifications API
- Web Apps / PWAs
- First-run UI
- Default browser checks
Is the WebBrowser Control fully HTML 5 compliant?
The Web Browser Control has the same HTML 5 compliance as Chromium 142, including CSS3, ES2023 JavaScript, WebGL and Web Assembly, and CORS enforcement.
Does the WebBrowser Control cache data, and if so, where is it located for different operating systems?
Yes, the Control caches using the default CEF caching support, with hosting app-provided paths. Cache paths are under LabVIEW's LabVIEW Data directory, and are versioned based on LabVIEW version.
Example paths for LabVIEW 2026 64-bit include:
- Windows: %USERPROFILE%\Documents\LabVIEW Data\2026(64-bit)
- Linux: ~/natinst/LabVIEW Data/2026(64-bit)/CEF
- Mac: ~/Documents/LabVIEW Data/2026(64-bit)/CEF
What plugin does the WebBrowser Control use to display PDF files?
PDF rendering uses Chromium’s built-in PDF engine based on PDFium.
How does Cross-Origin Resource Sharing (CORS) behave with the WebBrowser Control?
CORS behaves exactly as in Chromium 142. --disable-web-security is not used, and same-origin policy is enforced.
Is it possible to access web page components programmatically with the WebBrowser Control?
The Execute JavaScript method can be used to programmatically access web page components.
NI do not offer technical support for debugging JavaScript code, and do not advise on how to author JavaScript code.