[js] Add extended and symbolic macOS/ChromeDriver key representations

[iampopovich]

User description

🔗 Related Issues

fixes #15945

💥 What does this PR do?

This pull request adds support for extended macOS/ChromeDriver keys and symbolic macOS keys in the webdriver.Key object within javascript/webdriver/key.js. These changes expand the range of key codes available for macOS-specific functionality.

Enhancements to macOS key support:

• javascript/webdriver/key.js: Added extended macOS/ChromeDriver keys (RIGHT_SHIFT, RIGHT_CONTROL, RIGHT_ALT, RIGHT_COMMAND) with their respective Unicode values.
• javascript/webdriver/key.js: Introduced symbolic macOS keys (OPTIONS, FUNCTION) with placeholder Unicode values, pending verification with the WebDriver specification.

🔧 Implementation Notes

💡 Additional Considerations

🔄 Types of changes

• New feature (non-breaking change which adds functionality)

---

PR Type

Enhancement

---

Description

• Add extended macOS/ChromeDriver key representations (RIGHT_SHIFT, RIGHT_CONTROL, RIGHT_ALT, RIGHT_COMMAND)

• Introduce symbolic macOS keys (OPTIONS, FUNCTION) with placeholder Unicode values

• Expand key code support for macOS-specific functionality

---

Changes walkthrough 📝

	Relevant files
Enhancement	key.js Extended macOS key support                                                              javascript/webdriver/key.js Added four extended macOS/ChromeDriver keys with Unicode values Introduced two symbolic macOS keys with placeholder values Fixed trailing comma formatting for existing META key +11/-1

---

Need help?

Type /help how to ... in the comments thread for any questions about Qodo Merge usage.

Check out the documentation for more information.

[qodo-merge-pro]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Duplicate Values The symbolic macOS keys OPTIONS and FUNCTION are using the same Unicode values as RIGHT_SHIFT and RIGHT_CONTROL respectively. This creates ambiguity and potential conflicts when these keys are used. RIGHT_SHIFT: '\uE050', RIGHT_CONTROL: '\uE051', RIGHT_ALT: '\uE052', RIGHT_COMMAND: '\uE053', // Symbolic macOS keys OPTIONS: '\uE050', // TODO: verify Unicode value with WebDriver spec FUNCTION: '\uE051' // TODO: symbolic only; confirm or remove in future TODO Comments The symbolic macOS keys contain TODO comments indicating uncertainty about their Unicode values and future status. This suggests incomplete implementation that may need verification before merging. OPTIONS: '\uE050', // TODO: verify Unicode value with WebDriver spec FUNCTION: '\uE051' // TODO: symbolic only; confirm or remove in future

[qodo-merge-pro]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
Possible issue	✅ Fix duplicate Unicode key mappings Suggestion Impact: The suggestion partially impacted the commit - only the OPTIONS key was changed from '\uE050' to '\uE052', while FUNCTION key remained unchanged at '\uE051' code diff: - OPTIONS: '\uE050', // TODO: verify Unicode value with WebDriver spec + OPTIONS: '\uE052', // TODO: verify Unicode value with WebDriver spec The symbolic macOS keys OPTIONS and FUNCTION are using the same Unicode values as RIGHT_SHIFT and RIGHT_CONTROL respectively. This creates duplicate key mappings that could cause conflicts when these keys are used in automation scripts. javascript/webdriver/key.js [100-102] // Symbolic macOS keys -OPTIONS: '\uE050', // TODO: verify Unicode value with WebDriver spec -FUNCTION: '\uE051' // TODO: symbolic only; confirm or remove in future +OPTIONS: '\uE054', // TODO: verify Unicode value with WebDriver spec +FUNCTION: '\uE055' // TODO: symbolic only; confirm or remove in future [Suggestion processed] Suggestion importance[1-10]: 8 __ Why: The suggestion correctly identifies that the newly added keys OPTIONS and FUNCTION use the same Unicode values as RIGHT_SHIFT and RIGHT_CONTROL, which would cause conflicts. The proposed change to unique values is a valid and important correction.	Medium
Update