Documents

A section in the C++ SDK staging document ADR-001-out-of-scope-features: D-05 · Print / Pagination. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document ADR-001-out-of-scope-features: D-06: Advanced container queries. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document ADR-001-out-of-scope-features: D-07: The @scope rule. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document ADR-001-out-of-scope-features: D-08: Complex filters. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document tutorial: DOM and events. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document devtools_perf_fields: DevTools performance field contract. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document kui-editor: Diagnostics squiggles don't appear. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document kui-editor: Editor crashes the host. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document kui-editor: Editor element is empty / not rendering. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document extensions: Element appears but is invisible. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document architecture: Engineering Highlights (Roadmap Items). Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document extensions: Extension fails to load. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document extensions: Find KUI SDK. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document kui-editor: Find/replace returns 0 matches for a regex. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document kui-editor: Ghost text accept and cancel events. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document architecture: High-Level Architecture. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document components: Hot reload doesn't pick up Lua changes. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document architecture: How plugins are loaded. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document api_reference: KUI C++ API navigation. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document faq: KUI C++ SDK FAQ. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document tutorial: KUI C++ tutorial. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document css_feature_matrix: KUI CSS feature matrix. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document devtools: KUI DevTools. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document devtools_security: KUI DevTools security for local debugging. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document architecture: KUI Engine - Architecture Overview. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document extensions: KUI Extension System - In-Depth Guide. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document lua: KUI Lua Scripting - In-Depth Guide. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document components: KUI Virtual Components - In-Depth Guide. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document virtual_list: KUI Virtual Scroll Components — `VirtualList` / `ListView` / `TreeView`. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document wpt_conformance_snapshot: KUI WPT conformance snapshot. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document positioning_and_benchmark: Historical KUI positioning and comparison statement. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document known_issues: KUI known issues and written exceptions. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document faq: Is KUI a complete browser?. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document features: KUI capability boundaries. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document kui-editor: LSP server capability forwarding. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document kui-editor: LSP server starts but never initializes. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document components: Lua component methods aren't callable. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document devtools: MCP tools. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document architecture: Memory Footprint. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document kui-editor: Multi-cursor changes don't all undo with one Ctrl+Z. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document architecture: Optional Plugin DLLs. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document extensions: Optional: link third-party libs statically. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document extensions: Output to extensions/ for easy discovery. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document known_issues: P2: Conformance debt and performance, 242 snapshot entries. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document known_issues: P3: Platform and tooling work, 98 snapshot entries. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document extensions: Performance warnings. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document components: Performance: 60 FPS drops. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document architecture: Pipeline Stages. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document architecture: Plugin export convention. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document architecture: Plugin lifecycle. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document kui-editor: Q: Can I disable IME composition?. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document kui-editor: Q: Can I disable the gutter?. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document lua: Q: Can I do `el:foo()` syntax for any C++ method?. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document extensions: Q: Can I dynamically register additional tag names from one DLL?. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document extensions: Q: Can I have my extension expose a JavaScript API?. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document lua: Q: Can I mix Lua and JavaScript in the same KUI document?. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document lua: Q: Can I save Lua tables to disk?. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document kui-editor: Q: Can I theme bracket-pair colors?. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document lua: Q: Can I use Lua libraries from LuaRocks?. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document kui-editor: Q: Can I use `<kui-editor>` for a single-line input box?. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document extensions: Q: Can I write the extension in Rust / Go / Zig?. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document extensions: Q: Can my extension add new CSS properties?. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document kui-editor: Q: Can two editors share an LSP client?. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document extensions: Q: Can two extensions register the same tag?. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document lua: Q: Does Lua have access to `HttpClient`?. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document lua: Q: Does Lua have access to the 3D engine?. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document kui-editor: Q: Does the editor support virtual scrolling for million-line buffers?. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document extensions: Q: Does the host pass `Element*` directly?. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document kui-editor: Q: How do I add a new language?. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document kui-editor: Q: How do I handle "modified-but-unsaved" UI state?. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document kui-editor: Q: How do I implement IntelliSense / autocomplete UI?. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document kui-editor: Q: How do I implement vim mode?. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document extensions: Q: How do I open a separate window from my extension?. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document kui-editor: Q: How do I save the buffer to disk?. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document extensions: Q: How do I unit-test my extension?. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document lua: Q: How fast is a `document:getElementById` call from Lua?. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document extensions: Q: Is my extension portable between KUI versions?. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document extensions: Q: Where can my extension store config files?. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document kui-editor: Q: Why are some Lua methods undocumented?. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document lua: Q: Why can't I call `os.exit()` from a script?. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document lua: Q: Will my Lua scripts continue to work after a KUI minor upgrade?. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document lua: Which Lua version is used, and is LuaJIT compatibility guaranteed?. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document lua: Supported features. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document kui-editor: Syntax highlighting not working. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document components: Table of Contents. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document extensions: Table of Contents. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document kui-editor: Table of Contents. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document lua: Table of Contents. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document virtual_list: Table of Contents. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document architecture: Threading Model. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document lua: What just happened?. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document architecture: Where to Read More. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document lua: Why this works. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document kui-editor: `<kui-editor>` - Code Editor Component. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document devtools_security: The KUI_DEVTOOLS_PUBLIC_JSON build option. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document css-fonts: document.fonts: a subset of the CSS Font Loading API. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document css-fonts: `font-display`. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document css-fonts: `unicode-range`. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document devtools_perf_fields: advex_run.py around lines 316-324. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document components: attributeChangedCallback doesn't fire. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document components: connectedCallback doesn't fire. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document devtools_security: Token exposure and mitigations. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document ADR-001-out-of-scope-features: Neutral effects. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document ADR-002-style-core-extras-split: Neutral effects. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document ADR-003-rlottie-to-skottie-migration: Neutral or uncertain effects requiring observation. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document faq: Why can CMake not find Kui?. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document faq: Why is an optional component missing?. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document tutorial: Main loop. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document devtools: Main capabilities. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document ADR-001-out-of-scope-features: Metadata. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document ADR-002-style-core-extras-split: Metadata. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document ADR-003-rlottie-to-skottie-migration: Metadata. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document ADR-003-rlottie-to-skottie-migration: Implementation approach. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document kui-editor: Content change events: input. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document ADR-001-out-of-scope-features: Decision. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document ADR-002-style-core-extras-split: Decision. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document ADR-003-rlottie-to-skottie-migration: Decision. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document faq: Why is template content hidden after upgrading to 3.60.0?. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document devtools: Protocol. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document ADR-001-out-of-scope-features: References. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document ADR-002-style-core-extras-split: References. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document ADR-003-rlottie-to-skottie-migration: References. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document ADR-001-out-of-scope-features: Consequences. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document ADR-002-style-core-extras-split: Consequences. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document ADR-003-rlottie-to-skottie-migration: Consequences. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document devtools: Startup. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document ADR-001-out-of-scope-features: Alternatives. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document ADR-002-style-core-extras-split: Alternatives. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document ADR-003-rlottie-to-skottie-migration: Alternatives. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document faq: How is a Document created?. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document faq: How can an issue be reported?. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document devtools: Security. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document devtools_security: Positioning. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document ADR-002-style-core-extras-split: Implementation constraints. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document css_feature_matrix: Separate implementation status from scope. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document README: Deprecating an ADR. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document devtools_security: Recommendations. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document faq: How can a popup pause on first opening be investigated?. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document features: Current main capabilities. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document ADR-002-style-core-extras-split: Current status. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document features: Current gaps tracked as work items. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document wpt_conformance_snapshot: How to verify. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document performance: Performance features and options. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document wpt_conformance_snapshot: Total. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document extension_repaint_contract: Extension repaint contract, extension API v1.11. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document devtools: Troubleshooting. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document faq: Which platforms are supported?. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document ADR-002-style-core-extras-split: Data. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document kui-editor: Text access. Documentation must be checked against the delivered package for each release.

A section in the C++ SDK staging document README: Creating an ADR. Documentation must be checked against the delivered package for each release.