🚧 App in Alpha. Features subject to change/break without notice. Issue Tracker

Filters

Filter controls will go here

Add Issue Tracker AppAdone Implement Markdown SupportCto-do Dynamic Landing ModelCto-do Tree ShakingCto-do Source MappingBdoing Dynamic Desktop CSSCdoing Split Kireji App Drag-and-Drop HandlersCto-do Add Dynamic PartsCdoing Rework the Kireji URL FormatAto-do Refine Mesh Ray CastingCto-do Validate ModelToRouteID InputsCto-do Optimize Outliner SnapshotBto-do Post-Build ValidationBto-do Seamless Forward/Back NavigationAdoing Secure Against Cross-Site ScriptingAdoing Dynamic Task Bar Tray IconsAdoing Cross-Origin PWABdoing Console SupportCto-do Search Engine OptimizationAdoing Improve AccessabilityAto-do Mobile-Friendly Task MenuAto-do Feature Support FallbacksBto-do Full Desktop Window SupportBdoing Welcome AppBto-do Properties AppBto-do User-Managed Desktop IconsCto-do Part ExplorerBto-do Context MenuCto-do CLI InitalizationBto-do

Context Menu

Created: 1776212811 Priority: C Status: to-do Description: A context menu will allow users to right click parts and files. All parts and files can have a standard context menu. The desktop, taskbar and title bar can each have its own specific context menu. Thus, there must be a way to define the context menu specific to the parts, files and regions where it is brought up. Tap-and-hold on mobile, right-click on desktop are the likely mechanisms. Investigate using the native context menu event handling. A console-specific solution will likely need to be implemented. Consider the need to re-enable standard context menu (browser and OS native) on desktop so that users can still use their native context menu. Perhaps a setting or tray button can be used to toggle between native and custom context menus. Affected Parts: None Linked Issues: None