Skip to content

🎨 Palette: [UX κ°œμ„ ] λΉ„ν™œμ„±ν™”λœ λ‘œλ”© λ²„νŠΌμ— aria-busy 속성 μΆ”κ°€ - #1219

Merged
seonghobae merged 9 commits into
developfrom
ux-improvement-disabled-buttons-13634237694443312021
Aug 4, 2026
Merged

🎨 Palette: [UX κ°œμ„ ] λΉ„ν™œμ„±ν™”λœ λ‘œλ”© λ²„νŠΌμ— aria-busy 속성 μΆ”κ°€#1219
seonghobae merged 9 commits into
developfrom
ux-improvement-disabled-buttons-13634237694443312021

Conversation

@seonghobae

@seonghobae seonghobae commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

λ³€κ²½ 사항

  • ν”„λ‘œμ νŠΈ 후보 ν™•μ • μš”μ²­μ΄ μ§„ν–‰ 쀑일 λ•Œ λ²„νŠΌμ— aria-busy={confirmSubmitting}λ₯Ό μ μš©ν•΄ 보쑰 기술이 비동기 처리 μƒνƒœλ₯Ό μΈμ‹ν•˜λ„λ‘ ν–ˆμŠ΅λ‹ˆλ‹€.
  • λ‘œλ”© λ²„νŠΌμ˜ μ‹€μ œ disabled μƒνƒœ, aria-busy μ „ν™˜, μ§„ν–‰ 쀑 문ꡬ, μ™„λ£Œ μƒνƒœλ₯Ό κ²€μ¦ν•˜λŠ” μ „μš© Vitest νšŒκ·€ ν…ŒμŠ€νŠΈλ₯Ό μΆ”κ°€ν–ˆμŠ΅λ‹ˆλ‹€.
  • 쀑앙 ν•„μˆ˜ μ›Œν¬ν”Œλ‘œ 정책을 μœ„λ°˜ν•˜λ˜ μΌνšŒμ„± μ €μž₯μ†Œ 둜컬 리뷰 λ””μŠ€νŒ¨μ²˜λ₯Ό μ œκ±°ν–ˆμŠ΅λ‹ˆλ‹€. OpenCodeΒ·Strix·병합 μžλ™ν™”λŠ” ContextualWisdomLab/.github의 쀑앙 μ›Œν¬ν”Œλ‘œλ§Œ μ‚¬μš©ν•©λ‹ˆλ‹€.

검증 계약

  • frontend/src/components/ProjectsLayout.accessibility.test.tsx
    • μš”μ²­ μ „ aria-busy="false"
    • μš”μ²­ 쀑 disabled=true, aria-busy="true", ν™•μ • μ €μž₯ 쀑
    • 성곡 ν›„ aria-busy="false", ν”„λ‘œμ νŠΈ 후보 확정됨
  • Application CI, Dependency Review, Security Scan, Bandit, Semgrep, Docker validation을 ν˜„μž¬ headμ—μ„œ μž¬κ²€μ¦ν•©λ‹ˆλ‹€.

PR created automatically by Jules for task 13634237694443312021 started by @seonghobae

Summary by CodeRabbit

  • Accessibility

    • Confirmation buttons now communicate their loading state to assistive technologies during submission.
  • Bug Fixes

    • Improved confirmation feedback by clearly indicating when a request is processing and when it has completed.
  • Tests

    • Added coverage validating confirmation button states, messaging, and request handling.

@google-labs-jules

Copy link
Copy Markdown
Contributor

πŸ‘‹ Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a πŸ‘€ emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

@coderabbitai

coderabbitai Bot commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

Warning

Review limit reached

@seonghobae, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 55 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
βš™οΈ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 0844ffee-87b9-4f67-b624-155deece7f47

πŸ“₯ Commits

Reviewing files that changed from the base of the PR and between 4e2eb7f and 53ca2af.

πŸ“’ Files selected for processing (1)
  • frontend/src/components/ProjectsLayout.accessibility.test.tsx
πŸ“ Walkthrough

Walkthrough

The project confirmation button now exposes its submission state with aria-busy. A new accessibility test verifies the initial, pending, and completed states during the confirmation request.

Changes

Project confirmation accessibility

Layer / File(s) Summary
Confirmation button loading state and coverage
frontend/src/components/ProjectsLayout.tsx, frontend/src/components/ProjectsLayout.accessibility.test.tsx
The confirmation button sets aria-busy during submission. The test verifies the button state, text, endpoint call, and completed confirmation state.

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related PRs

Suggested reviewers: opencode-agent

πŸš₯ Pre-merge checks | βœ… 4
βœ… Passed checks (4 passed)
Check name Status Explanation
Description Check βœ… Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check βœ… Passed The title clearly describes the main change: adding the aria-busy attribute to the loading confirmation button.
Linked Issues check βœ… Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check βœ… Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
πŸ“ Generate docstrings
  • Create stacked PR
  • Commit on current branch
πŸ§ͺ Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch ux-improvement-disabled-buttons-13634237694443312021

Comment @coderabbitai help to get the list of available commands.

Copy link
Copy Markdown
Contributor Author

@coderabbitai review

@coderabbitai

coderabbitai Bot commented Aug 3, 2026

Copy link
Copy Markdown
Contributor
βœ… Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

@seonghobae
seonghobae force-pushed the ux-improvement-disabled-buttons-13634237694443312021 branch from 0861a94 to 15f79be Compare August 3, 2026 02:52
@github-actions

github-actions Bot commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

PR governance metadata gate update for 53ca2afac7a7311f895674e2d7a988ac1853d200: no current blocking failures remain.

PR governance metadata gate is ready; all current-head requirements passed.

Copy link
Copy Markdown
Contributor Author

@coderabbitai review

Please review current head 15f79be31a60a468637c579ebdd54dc2981263ee, including the loading-button accessibility contract and removal of the repository-local review dispatcher.

@coderabbitai

coderabbitai Bot commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

@seonghobae I will review commit 15f79be31a60a468637c579ebdd54dc2981263ee. I will check the loading-button accessibility contract and the removal of the repository-local review dispatcher.

βœ… Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

@seonghobae seonghobae left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Current-head accessibility review completed: the project confirmation control now exposes aria-busy during the async request and a focused jsdom regression test verifies idle, pending, disabled, and completed states. Scope is limited to the component and its test; refresh central review evidence after checks complete.

@google-labs-jules

Copy link
Copy Markdown
Contributor

@coderabbitai review

Please review current head 15f79be31a60a468637c579ebdd54dc2981263ee, including the loading-button accessibility contract and removal of the repository-local review dispatcher.

ν•΄λ‹Ή 였λ₯˜λŠ” λ‚΄κ°€ λ§ˆμ§€λ§‰μœΌλ‘œ μž‘μ„±ν•œ 컀밋 이후 μΆ”κ°€μ μœΌλ‘œ λ§Œλ“€μ–΄μ§„ μ»€λ°‹λ“€μ—μ„œ λΉ„λ‘―λœ 좩돌/λ¬Έμ œμ˜€μŠ΅λ‹ˆλ‹€. μ§€κΈˆ 확인해본 κ²°κ³Ό CI 체크λ₯Ό 톡과할 수 μžˆλ„λ‘ 파일과 λ³€κ²½ 사항듀이 λͺ¨λ‘ 이미 μ‚­μ œ/μˆ˜μ •λœ κ²ƒμœΌλ‘œ λ³΄μž…λ‹ˆλ‹€. λ‹€λ₯Έ 도움이 ν•„μš”ν•˜λ‹€λ©΄ μ•Œλ €μ£Όμ„Έμš”.

@seonghobae seonghobae left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Current head 82ef7a904a5f43df41b7e87f9888dcd64a0e649e is scoped to the production component and its dedicated accessibility regression test. Application CI, security, dependency, Bandit, and Semgrep checks are successful; Docker validation is still completing. Re-triggering current-head OpenCode/merge scheduling.

@seonghobae
seonghobae marked this pull request as draft August 3, 2026 05:08
@seonghobae
seonghobae marked this pull request as ready for review August 3, 2026 05:08

@seonghobae seonghobae left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Commercialization-loop current-head revalidation: 82ef7a904a5f43df41b7e87f9888dcd64a0e649e has zero review threads and all six repository-local workflows, including Docker validation, are successful. Re-triggering the central independent-review and guarded merge scheduler for this exact head.

Copy link
Copy Markdown
Contributor Author

@coderabbitai review

Please perform a complete review of the current head 807967e61fc6d0c263eb5693e1a6fd64dce465b1. The branch is refreshed onto current develop, has zero review threads, and changes only ProjectsLayout.tsx plus its dedicated async accessibility regression test.

@coderabbitai

coderabbitai Bot commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

@seonghobae I will perform a complete review of commit 807967e61fc6d0c263eb5693e1a6fd64dce465b1. I will review ProjectsLayout.tsx and the async accessibility regression test.

βœ… Action performed

Full review finished.


Your included review limit is currently reached under our Fair Usage Limits Policy. This review may still proceed through usage-based billing if eligible. Your next included review will be available in 4 minutes.

Copy link
Copy Markdown
Contributor Author

@coderabbitai review

The included-review cooldown has elapsed. Please perform the complete current-head review for 807967e61fc6d0c263eb5693e1a6fd64dce465b1 and submit it against that exact commit.

@coderabbitai

coderabbitai Bot commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

@seonghobae I will perform a complete review for commit 807967e61fc6d0c263eb5693e1a6fd64dce465b1. I will review the loading-button accessibility contract and the dedicated async regression test.

βœ… Action performed

Full review finished.


Your included review limit is currently reached under our Fair Usage Limits Policy. This review may still proceed through usage-based billing if eligible. Your next included review will be available in 44 seconds.

Copy link
Copy Markdown
Contributor Author

@coderabbitai review

The included-review cooldown is clear now. Please perform the complete review for current head 807967e61fc6d0c263eb5693e1a6fd64dce465b1 and submit the review against that exact commit.

@coderabbitai

coderabbitai Bot commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

@seonghobae I will perform a complete review for commit 807967e61fc6d0c263eb5693e1a6fd64dce465b1 and submit it against that commit.

βœ… Action performed

Full review finished.


Your included review limit is currently reached under our Fair Usage Limits Policy. This review may still proceed through usage-based billing if eligible. Your next included review will be available in 41 minutes.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

πŸ€– Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@frontend/src/components/ProjectsLayout.accessibility.test.tsx`:
- Around line 108-130: Update the confirmation test around the existing
confirmButton assertions to verify disabled is false before clicking, remains
true while confirmation is pending, and is false or true after completion
according to the component’s disabled={confirmSubmitting || candidateConfirmed}
contractβ€”specifically assert the completed confirmed state is disabled. Keep the
existing aria-busy, text, and API-call assertions unchanged.
πŸͺ„ Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
βš™οΈ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: c00e6f87-affd-4161-8c72-132254b86e33

πŸ“₯ Commits

Reviewing files that changed from the base of the PR and between 0729be5 and 4e2eb7f.

πŸ“’ Files selected for processing (2)
  • frontend/src/components/ProjectsLayout.accessibility.test.tsx
  • frontend/src/components/ProjectsLayout.tsx

Comment thread frontend/src/components/ProjectsLayout.accessibility.test.tsx

Copy link
Copy Markdown
Contributor Author

Addressed the current review finding in 53ca2afac7a7311f895674e2d7a988ac1853d200: the accessibility regression now asserts the confirmation button is initially enabled, disabled during the pending request, and still disabled after the candidate is confirmed, while retaining all existing aria-busy, message, and API-call checks. Revalidating this exact head before resolving/merging.

@google-labs-jules

Copy link
Copy Markdown
Contributor

Addressed the current review finding in 53ca2afac7a7311f895674e2d7a988ac1853d200: the accessibility regression now asserts the confirmation button is initially enabled, disabled during the pending request, and still disabled after the candidate is confirmed, while retaining all existing aria-busy, message, and API-call checks. Revalidating this exact head before resolving/merging.

ν™•μΈν–ˆμŠ΅λ‹ˆλ‹€. ν…ŒμŠ€νŠΈ λ³€κ²½ 사항이 μ„±κ³΅μ μœΌλ‘œ 반영된 것을 ν™•μΈν–ˆμŠ΅λ‹ˆλ‹€. λ‹€λ₯Έ μΆ”κ°€ μž‘μ—…μ΄ ν•„μš”ν•˜λ©΄ μ•Œλ €μ£Όμ„Έμš”.

@seonghobae
seonghobae merged commit c8ef416 into develop Aug 4, 2026
45 checks passed
@seonghobae
seonghobae deleted the ux-improvement-disabled-buttons-13634237694443312021 branch August 4, 2026 00:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant