Context
This follow-up task was identified during the review of PR #292.
Source PR: #292
Suggested by: @claude[bot]
Task Description
The old Close() respected d.Persistent — it was a no-op if the drawer was persistent. ForceClose() bypassed this. Both methods are now removed. The inline onclick handler preserves the persistent check for the close button and overlay, but there is no replacement for ForceClose() for application code that needs to programmatically force-close a persistent drawer from a server-side action handler.
Fix: Document the deprecation path, or provide a mechanism (e.g., a server-controlled class or attribute) for programmatic force-close of persistent drawers.
This issue was automatically created from PR #292 review comments.
Context
This follow-up task was identified during the review of PR #292.
Source PR: #292
Suggested by: @claude[bot]
Task Description
The old
Close()respectedd.Persistent— it was a no-op if the drawer was persistent.ForceClose()bypassed this. Both methods are now removed. The inlineonclickhandler preserves the persistent check for the close button and overlay, but there is no replacement forForceClose()for application code that needs to programmatically force-close a persistent drawer from a server-side action handler.Fix: Document the deprecation path, or provide a mechanism (e.g., a server-controlled class or attribute) for programmatic force-close of persistent drawers.
This issue was automatically created from PR #292 review comments.