🎨 Palette: 스크롤 요소 및 요약 태그의 마우스 클릭 시 포커스 링 제거

[seonghobae]

💡 What: HTML 리포트 생성 스크립트(report.py, report_html.py) 내에 있는 스크롤 가능한 요소 및 <summary> 요소가 마우스로 클릭될 때 나타나는 기본 포커스 링을 숨기도록 CSS를 업데이트했습니다.
🎯 Why: 테이블과 코드 블록의 가로 스크롤을 위해 tabindex="0" 속성이 추가되면서, 사용자가 스크롤을 위해 클릭할 때마다 강한 포커스 라인이 생겨 거슬리는 UX 문제가 발생했습니다.
📸 Before/After: 마우스 클릭 시 요소 주변에 불필요한 테두리가 사라졌습니다.
♿ Accessibility: :focus-visible 스타일을 :focus 스타일 뒤에 명시함으로써, 키보드 네비게이션 시에는 시각적 포커스 라인이 온전히 유지됩니다.

---

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

---

[google-labs-jules]

👋 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]

Warning

Review limit reached

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

Next review available in: 34 minutes

Limit details: You’ve used the included review currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

Wait for the limit to reset, then comment @coderabbitai review or push new commits to the PR.

An organization admin can change what happens after included review limits in Billing.

How do review limits work?

CodeRabbit enforces per-developer PR review limits within each organization.

For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: f677f5e5-ac7e-497f-a186-4366ac87a683

📥 Commits

Reviewing files that changed from the base of the PR and between 04d0bc2 and baa5c6f.

📒 Files selected for processing (2)

• python/fast_mlsirm/report.py
• python/fast_mlsirm/scoring/essay/report_html.py

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[seonghobae]

Review disposition at exact head 29f7c04918d8724369e6c065d81b7ad8898561d1:

• Resolved Devin finding discussion_r3828245655: removed the PR-only .Jules/palette.md addition; canonical learnings remain in lowercase .jules/, and the pre-existing user working-copy edit was not staged or changed.
• Added focused regression assertions for mouse-focus suppression and preserved :focus-visible keyboard indicators.
• Verification: 27 focused tests passed; Ruff passed; interrogate 100% for changed production modules; git diff --check passed.

The CSS change remains bounded to report accessibility behavior.

[google-labs-jules]

Review disposition at exact head 29f7c04918d8724369e6c065d81b7ad8898561d1:

• Resolved Devin finding discussion_r3828245655: removed the PR-only .Jules/palette.md addition; canonical learnings remain in lowercase .jules/, and the pre-existing user working-copy edit was not staged or changed.
• Added focused regression assertions for mouse-focus suppression and preserved :focus-visible keyboard indicators.
• Verification: 27 focused tests passed; Ruff passed; interrogate 100% for changed production modules; git diff --check passed.

The CSS change remains bounded to report accessibility behavior.

Acknowledged. I have reverted the .Jules/palette.md modifications from the staged area to ensure that the user's working-copy and canonical PR logs remain separate and that the PR strictly bounds itself to the targeted CSS accessibility changes.

[seonghobae]

Current-head reconciliation at exact head baa5c6f675a26f59dc30b27b2788d024afd16aa3:

• A concurrent Jules commit advanced the branch after the prior review note; its final tree was re-fetched and verified without force-push or overwrite.
• The Devin finding remains resolved: the PR no longer changes the non-canonical .Jules/palette.md; only the two intended report CSS modules differ from origin/main.
• Exact-head verification: 27 focused tests passed, Ruff passed, interrogate 100% for both changed production modules, and git diff --check passed.

The PR remains on the normal protected auto-merge path.

[devin-ai-integration]

Devin Review found 1 new potential issue.

[devin-ai-integration]

📝 Info: Focus suppression pattern differs from the main element

The new .table-scroll:focus, pre:focus { outline: none; } paired with the :focus-visible rule below drops the keyboard focus ring on user agents lacking :focus-visible support, since the invalid :focus-visible selector list is discarded. The main element in the same stylesheet deliberately uses main:focus:not(:focus-visible) to keep a fallback (enforced by tests/test_scoring_essay_report_pointer_focus.py:11-12). The container :focus { outline: none; } form is the tested convention elsewhere (tests/test_report_focus_contrast.py:55-56), so this matches existing behavior.

---

Was this helpful? React with 👍 or 👎 to provide feedback.

[google-labs-jules]

Current-head reconciliation at exact head baa5c6f675a26f59dc30b27b2788d024afd16aa3:

• A concurrent Jules commit advanced the branch after the prior review note; its final tree was re-fetched and verified without force-push or overwrite.
• The Devin finding remains resolved: the PR no longer changes the non-canonical .Jules/palette.md; only the two intended report CSS modules differ from origin/main.
• Exact-head verification: 27 focused tests passed, Ruff passed, interrogate 100% for both changed production modules, and git diff --check passed.

The PR remains on the normal protected auto-merge path.

Acknowledged. Thanks for the verification.

[seonghobae]

Closing as superseded by the existing report-surface writers after adopting the compatible intent without the blanket-focus selector.

Fresh comparison shows:

• generic diagnostics python/fast_mlsirm/report.py is already owned by fix(report): replay main focus accessibility on current review workflow #1002 at 36e0bdd71535e56fe1329f31c2cd74d0749c64d8, where pointer suppression uses :focus:not(:focus-visible) and regressions explicitly reject blanket :focus { outline: none; };
• essay python/fast_mlsirm/scoring/essay/report_html.py is owned by fix(report): harden essay titles and semantic row headers #997. I added RED b01ba1ba90408242c365605f7b4b8cc6c61a1037, GREEN 18b213520257a038accf4317a104c3cc0bfe06c5, and changelog 47ec832f95e0ea0a31715212bd965325c28a4542 there so .table-scroll and canonical JSON <pre> suppress pointer-acquired outlines only under :focus:not(:focus-visible), while keyboard focus remains explicit.

#1143's blanket .table-scroll:focus, pre:focus { outline: none; } and summary :focus rules therefore duplicate/conflict with the repository's established modality-safe contract. No #1143 commit will be merged independently.

[google-labs-jules]

Closing as superseded by the existing report-surface writers after adopting the compatible intent without the blanket-focus selector.

Fresh comparison shows:

• generic diagnostics python/fast_mlsirm/report.py is already owned by fix(report): replay main focus accessibility on current review workflow #1002 at 36e0bdd71535e56fe1329f31c2cd74d0749c64d8, where pointer suppression uses :focus:not(:focus-visible) and regressions explicitly reject blanket :focus { outline: none; };
• essay python/fast_mlsirm/scoring/essay/report_html.py is owned by fix(report): harden essay titles and semantic row headers #997. I added RED b01ba1ba90408242c365605f7b4b8cc6c61a1037, GREEN 18b213520257a038accf4317a104c3cc0bfe06c5, and changelog 47ec832f95e0ea0a31715212bd965325c28a4542 there so .table-scroll and canonical JSON <pre> suppress pointer-acquired outlines only under :focus:not(:focus-visible), while keyboard focus remains explicit.

#1143's blanket .table-scroll:focus, pre:focus { outline: none; } and summary :focus rules therefore duplicate/conflict with the repository's established modality-safe contract. No #1143 commit will be merged independently.

Understood. Acknowledging that this work is now obsolete and superseded by the correct modality-safe :focus:not(:focus-visible) implementation in existing PRs. Stopping work on this task.