@junie-agent

Your Task

1. Download the Pull Request diff using:
   gh pr diff ${{ github.event.pull_request.head.ref }}

2. Review only:

• the code changed in the diff
• code that is directly or closely connected to the changed code
  Do not explore other parts of the repository.

3. Perform the review according to the criteria below.
4. Write GitHub comment for every issue you found.
5. Do not write any summary about the pull request. Only the issues you found.

You MUST NOT:

• run the code
• build the project
• execute tests
• explore the repository beyond the files included in the diff.
• make any changes in the code review
• commit anything into the code review branch
• write code review summary

Review Scope

1. Comments

Use professional and polite language.

• Add a comment if you are absolutely sure about an issue you have found in the code; otherwise, skip it.
• Do not write comments if you are unsure about an issue in the code.
• Do not write a summary of the code review. Only write comments on specific issues if they are identified.
• Only write about issues that you have found. Don't write anything else.
• If issues found, write comments using the flolwing output format:

⚠️ 2 issues found

1. [full path to the issue file] : [line number]
   [short comment for the issue 1]

2. [full path to the issue file] : [line number]
   [short comment for the issue 2]

• If no issues found, write only this line and nothing else:

✅ No issues found

2. Check criteria

• Verify that the code changes corresponding the PR title and description.
• Verify any grammar mistakes in the diff. Don't highlight grammar mistakes outside the pull request's diff.
• Use deep knowledge about algorithms and data structures to find potential issues in the code.
• Deeply analyze logic of algorithms that are changed in the PR and find inconsistencies between the implementation and expected behaviour.
• Check for common typos in the code logic, like == vs !=.
• Any other issues that crucial for the code review.

Junie successfully finished!

Result: Review Web Clipboard Events Fix in SelectionContainer

⚠️ 2 issues found

1. compose/ui/ui/src/webMain/kotlin/androidx/compose/ui/window/ComposeWindowInternal.web.kt : 351
   On macOS, including isCtrlPressed in the shortcut check can cause focus to be permanently lost to the hidden textarea, as browsers typically don't dispatch clipboard events for Ctrl+C/V/X on Mac. It is recommended to only use isMetaPressed for macOS clipboard shortcuts.

2. compose/ui/ui/src/webMain/kotlin/androidx/compose/ui/window/ComposeWindowInternal.web.kt : 677
   Grammar mistake in comment: "to canvas" should be "to the canvas". Additionally, "let a browser" (lines 357, 676) should be "let the browser".