🚧 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

Feature Support Fallbacks

Created: 1776209268 Priority: B Status: to-do Description: Currently, browsers without any support for service worker or gpu (such as search engine indexing bots) will successfully fetch the page snapshot. However, users who don't have service worker support will find the page non-responsive. The page doesn't need to be responsive for these users, but rather a message can indicate as much. Hopefully, it can be done in such a way that doesn't impact SEO. Otherwise, skip it (almost all clients support service worker). For clients that don't support GPU (including search engine bots), there is currently an error that appears during gpu facet installation before the client hydration occurs: `TypeError: Cannot read properties of null (reading 'requestDevice') at Object.value (eval at )` This will lock the system for those users. Consider approaches to resolve this. Affected Parts: None Linked Issues: None