Fix comments section UX regressions and HTMX reply/Turnstile behavior #49
Reference in New Issue
Block a user
Delete Branch "fix/comments-standardize-htmx-turnstile"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
This PR fixes the current comment-section regressions and aligns the experience with a more standard, cohesive modern comment UI.
Closes #48.
What changed
#replies-for-<comment_id>).#comments-empty-state).static/js/comments.jsto:Tests
docker compose run --rm web pytest -o addopts='' apps/comments/tests apps/blog/tests/test_views.py -qNotes
pytestis unavailable in this workspace, so tests were executed in the project Docker environment.Re-reviewed with strict QA focus. Previous comments UX/HTMX regressions appear resolved:\n- Stable reply OOB target now uses #replies-for-.\n- Reply partial rendering/context path is consistent.\n- Reply form values are preserved on HTMX validation errors.\n- Comment empty-state handling and Turnstile re-init client script are wired into the page.\n\nVerification run (Docker):\n- pytest -o addopts='' apps/comments/tests apps/blog/tests/test_views.py -q\n- python manage.py check\n\nNo blocking issues found in this PR.