api framexml
Use for any selected combination of Retail, Forever, and Classic progression. First resolve the target and pinned source with wow-client-targets.
Target-specific decisions
For visible UI changes, use the mock-up choice and UIForever workflow before production implementation and during visual testing.
Use visual fidelity to preserve accepted artwork, layout and styling with verified templates/custom media, and compare the actual render rather than assuming a native template matches.
Trace the owning Blizzard addon and its TOC/XML includes to the selected game type before using a mixin, pool, helper, or global. Verify load-on-demand dependencies and method signatures.
Read the relevant row in compatibility guidance. Verify only the APIs needed for this task, using commit-pinned definitions and loaded client code. Missing evidence means unknown, not supported or removed. When offline, disclose the snapshot version/date and unresolved behavior.
Detailed lookup material
Start with current loaded UI sources for pinned TOCs, mixins/pools, callback ownership, secure templates and the boundary between Lua helpers and native methods.
The historical Retail baseline retains the original API listings and examples. It is a research aid, not current or cross-client verification. Open only relevant supporting references:
- CHATFRAME CONTAINERS
- FRAMEXML GAME UTILS
- MIXINS AND POOLS
- SHAREDXML DATA UTILS
- SHAREDXML UI UTILS
- UIPARENT
For implementation and release validation, use wow-addon-development.


