Nexus
The page is blank or partly missing
Check page scripts, resource paths, and component status to diagnose blank pages and missing sections.
Distinguish a blank page from a blank component
A completely blank page often indicates entry-resource or initialization failure. If only a dialog, chart, or image is empty, check its resources and dimensions first. Record the first error rather than hiding load-order issues through repeated refreshes.
Follow resource loading order
- Confirm the loaded HTML is the current build output, not an old page or source template.
- HTML script, style, and image paths are relative to HTML; CSS URLs are relative to CSS. Check each after moving directories.
- Third-party helpers must be readable from the page. Being available in a browser does not mean they are packaged with the add-on.
- Network fonts, scripts, and images may be unavailable offline. Bundle redistributable dependencies for offline delivery and preserve licenses.
For packaging and relative paths, see Local pages and resource paths and Package and deliver your add-on.
Local pages prohibit inline scripts
Trusted local pages prohibit inline script, inline handlers such as onclick, and eval-style execution. Put scripts in external files, load them with src, and bind events there. Do not loosen policy to hide incorrect page code.
Initialization errors, incorrect load order, or mixed helper versions can stop rendering. Fix the original error instead of treating every request failure as a need to reinstall runtime components.
Inspect the component's own state
| Observation | Diagnosis and response |
|---|---|
| Blank only when first expanded | Check whether initialization happened at zero size. Use the library's supported public update mechanism, not guessed private refresh methods. |
| Blank model or image area | Check resource retrieval before decoding or rendering errors. See Diagnose resource reads. |
| Local service data failed to load | Check service availability and system permissions. The failure may be network-related rather than layout-related. Follow actual errors; do not disable all security settings. |
| Ordinary browser reports no bridge | This is the capability difference between preview and hosted pages. Test application behavior in a trusted local Blender page. |
Verify the originally blank area
- Content appears on the first opening without a second refresh.
- The formerly blank dialog, list, or chart displays real content when expanded.
- Check a data-dependent function and meaningful failure feedback.
Static-resource fixes do not require rebuilding runtime components. Correct page display does not prove Blender communication works.
If unresolved, follow Provide useful diagnostic information to prepare a minimal reproduction and original messages for the add-on author.