🚧 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

Rework the Kireji URL Format

Created: 1776205544 Priority: A Status: to-do Description: Reconfigure the URL to make canonical paths a dominant, present aspect at all times and reconsider the treatment of the hash for canonical links. The motivation behind this feature is two fold. 1. It supports bookmarked, stateful URLs after their version has been removed from the server. This is critical because, currently, versioned URLs which have been removed from the server tell the server nothing about the page the user was on so such bookmarks simply go to a 404 page. Furthermore, it is not possible to quickly have the user bookmark the canonical version of the URL even though it is easy to link to and index (SEO) these URLs. This change will give the server something besides a 404 page to return (such as a "That version is no longer available... but here is the page you requested") so that bookmarked tools (such as the timestamp tool) are robustly available. 2. It makes it immediately obvious to the user what page they are on by looking at a URL or what page a bookmarked or shared URL will travel to. Having the state stored as a query parameter is more familiar to most users and is more in line with the intent and use of URL's pathname and query for this kind of stateful URL. Affected Parts: None Linked Issues: None