Stay organized with collections
Save and categorize content based on your preferences.
blockly > ShortcutRegistry > KeyboardShortcut > allowCollision
ShortcutRegistry.KeyboardShortcut.allowCollision property
Value of allowCollision to pass to addKeyMapping when binding this shortcut's .keyCodes (if any).
N.B.: this is only used for binding keycodes at the time this shortcut is initially registered, not for any subsequent addKeyMapping calls that happen to reference this shortcut's name.
Signature:
allowCollision?: boolean;
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-05-16 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-05-16 UTC."],[],["The `allowCollision` property, part of the `KeyboardShortcut` interface within the `ShortcutRegistry`, is a boolean value. It determines whether or not a keyboard shortcut is allowed to collide with another existing shortcut. The property is optional within the interface definition, as indicated by the question mark in its signature (`allowCollision?: boolean;`).\n"]]
