Preferences Loading & Retry
Handle metadata failures without resetting or silently changing choices.
Content and code last checked 2026-10-06 by ConsentEase product documentation. This is a review of the written content and code, not a test on a live third-party platform.
Control does nothing
Check that the real embed finished loading before a JavaScript call. There is no pre-load showPreferences queue. A link may navigate to its fallback; a button cannot open a not-yet-loaded runtime.
Panel shows Retry
Inspect the category metadata request and its status/body, CSP/connect restrictions and network failures. A visible Retry means the real inventory is unavailable; existing choices remain unchanged. Do not replace it with guessed default categories or automatically accept/reject.
Accessibility and layering
Test a native button/link with keyboard activation, visibility, focus and competing overlays. Presence of data-consentease-preferences in the DOM is not sufficient. Repeated calls should focus the same panel; Escape returns focus.
Excluded route
Automatic UI/events can be suppressed intentionally, but an explicit preferences action can work once the runtime is available. Check whether your control is actually present on that route.
Keep the floating control available until the replacement has passed real-site checks. Reopening is not resetting consent.