Skip to content

[Word/Excel] (keyboard shortcuts) Document backward compatibility support in the unified manifest #5244

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

samantharamon
Copy link
Contributor

Documents how to create custom shortcut and localization files for backward compatibility in the unified manifest.

Copy link
Contributor

Learn Build status updates of commit 6be62c8:

✅ Validation status: passed

File Status Preview URL Details
docs/design/keyboard-shortcuts.md ✅Succeeded View

For more details, please refer to the build report.

@samantharamon samantharamon requested a review from Copilot June 20, 2025 23:25
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR updates the documentation for custom keyboard shortcuts in Office Add-ins to detail the backward compatibility support in the unified manifest.

  • The metadata date has been updated.
  • The examples have been updated to remove add-in specific text in display names and include improved JSON examples for shortcuts and localization.
  • New sections and note blocks have been added to explain how to support backward compatibility when publishing to AppSource.

Copy link
Contributor

Learn Build status updates of commit da029e3:

✅ Validation status: passed

File Status Preview URL Details
docs/design/keyboard-shortcuts.md ✅Succeeded View

For more details, please refer to the build report.

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