[java] Deduplicate Unicode PUA mappings in Keys; make OPTION an alias of ALT and deprecate FN

[seethinajayadileep]

💥 What does this PR do?

Removes duplicate Unicode Private Use Area (PUA) mappings in org.openqa.selenium.Keys.

• Updates OPTION to be an alias of ALT using OPTION(Keys.ALT) instead of duplicating RIGHT_ALT (\uE052).
• Converts FN into a deprecated alias of RIGHT_CONTROL using FN(Keys.RIGHT_CONTROL) instead of directly mapping \uE051.
• Updates Javadoc to reflect the change.

---

🔧 Implementation Notes

Keys.getKeyFromUnicode() returns the first matching enum value. When multiple enum constants share the same Unicode PUA value:

• The lookup becomes ambiguous.
• One constant becomes unreachable.
• Behavior becomes order-dependent.

This change ensures that each Unicode PUA value maps to a single canonical key.

OPTION remains a platform-friendly alias without introducing a duplicate Unicode value.

FN is retained for backward compatibility but deprecated. It now delegates to RIGHT_CONTROL instead of defining its own duplicate Unicode value.

---

💡 Additional Considerations

• No breaking API changes.
• No duplicate Unicode values remain.
• Backward compatibility preserved.

---

🔄 Types of changes

• Bug fix (backwards compatible)

[qodo-code-review]

PR Type

Bug fix

---

Description

• Removes duplicate Unicode PUA mapping for FN key

• Aliases OPTION to ALT instead of duplicating RIGHT_ALT

• Updates Javadoc to clarify key specifications and aliases

• Ensures each Unicode PUA value maps to single canonical key

---

File Walkthrough

Relevant files

Bug fix

Keys.java Remove FN key and alias OPTION to ALT                                        java/src/org/openqa/selenium/Keys.java Removed FN key enum constant that duplicated RIGHT_CONTROL (\uE051) Changed OPTION from duplicate RIGHT_ALT (\uE052) to alias of ALT using Keys.ALT Updated Javadoc to clarify that OPTION is a symbolic alias and FN is no longer supported Added explanatory comment noting FN removal rationale (not W3C spec compliant) +7/-5

---

[qodo-code-review]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
Update

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[qodo-code-review]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
Possible issue	Prevent alias from overriding mapping In the reverse lookup map initialization, use putIfAbsent instead of put to prevent the OPTION alias from overwriting the ALT key's mapping. java/src/org/openqa/selenium/Keys.java [205-207] for (Keys key : values()) { - keyMap.put(key.keyCode, key); + keyMap.putIfAbsent(key.keyCode, key); } [To ensure code accuracy, apply this suggestion manually] Suggestion importance[1-10]: 8 __ Why: The suggestion correctly identifies a bug where the new OPTION alias would overwrite the original ALT in the reverse lookup map, and proposes a correct fix using putIfAbsent.	Medium
Update

[asolntsev]

Good for me.

@seethinajayadileep
Isn't there a risk that somebody is already using constant Keys.FN?
What would be a workaround for them?

[seethinajayadileep]

Good for me.

@seethinajayadileep Isn't there a risk that somebody is already using constant Keys.FN? What would be a workaround for them?

You’re right — removing Keys.FN would be a source-breaking change for anyone already referencing it.

Even though FN is not part of the W3C WebDriver specification and doesn’t have reliable driver support, existing code may still compile against it.

A safer approach would be to keep FN for backward compatibility and mark it as @deprecated, documenting that it is symbolic only and not part of the standardized key set.

That way existing users are not broken, but future usage is discouraged. I can update the PR accordingly.