kireji 0.8.2 → 0.10.0

package/src/app/kireji/issue-tracker/part.html_.js

@@ -0,0 +1,4 @@
+return kirejiIssueFilters["part.html"] + (
+ "<section class=issue-table>" + kirejiIssueTracker.scroller.wrap(kirejiIssueTracker["issues.html"]) + "</section>" +
+ `<section id=kireji-issue-modal>${kirejiIssueSections.arm["part.html"] ?? ""}</section>`
+)

package/src/app/kireji/issue-tracker/part.json

@@ -0,0 +1,9 @@
+{
+ "extends": "application",
+ "methods": {
+  "pathname-translate-canonical": [
+   "PATHNAME",
+   "HASH"
+  ]
+ }
+}

package/src/app/kireji/issue-tracker/pathname-canonical_.js

@@ -0,0 +1 @@
+return kirejiIssueTracker.sections.canonicalPathname

package/src/app/kireji/issue-tracker/pathname-translate-canonical.js

@@ -0,0 +1,39 @@
+const { model } = _
+
+debug('yes, it is translating ...')
+
+if (!("app" in model))
+ model.app = {}
+
+if (!("kireji" in model.app))
+ model.app.kireji = {}
+
+if (!("issue-tracker" in model.app.kireji))
+ model.app.kireji["issue-tracker"] = {}
+
+if (PATHNAME === "/") {
+
+ if (HASH !== "#top")
+  model.app.kireji["issue-tracker"].sections = "summary"
+
+} else {
+
+ const parts = PATHNAME.split("/").slice(1)
+
+ debug({
+  parts,
+  badSubpath: parts[0] !== "issues",
+  missingCode: !parts[1],
+  wrongLength: parts.length !== 2,
+  isNaN: isNaN(parts[1]),
+  notFound: !(parts[1] in kirejiIssueTracker.sections.issues)
+ })
+ if (parts[0] !== "issues" || !parts[1] || parts.length !== 2 || isNaN(parts[1]) || !(parts[1] in kirejiIssueTracker.sections.issues))
+  throw "Unknown Canonical Path: " + PATHNAME
+
+ model.app.kireji["issue-tracker"].sections = {
+  issues: parts[1]
+ }
+}
+
+return encodePathname(_.modelToRouteID(model))

package/src/app/kireji/issue-tracker/scroller/part.json

@@ -0,0 +1,3 @@
+{
+ "extends": "scroller"
+}

package/src/app/kireji/issue-tracker/scroller/query

@@ -0,0 +1 @@
+.issue-table

package/src/app/kireji/issue-tracker/sections/issues/1776193480/description

@@ -0,0 +1 @@
+Create an issue tracker. This moves "TODO" comments out of code without losing track of these tasks. Consider approaches such as removing completed tasks from different versions of the framework. Consider how the chosen approach impacts user-generated issues and how those will mix with the framework's issues itself.

package/src/app/kireji/issue-tracker/sections/issues/1776193480/part.json

@@ -0,0 +1,3 @@
+{
+ "extends": "issue.."
+}

package/src/app/kireji/issue-tracker/sections/issues/1776193480/status

@@ -0,0 +1 @@
+done

package/src/app/kireji/issue-tracker/sections/issues/1776193480/title

@@ -0,0 +1 @@
+Create Issue Tracker App

package/src/app/kireji/issue-tracker/sections/issues/1776193941/affects_.js

@@ -0,0 +1,3 @@
+return [
+ _.parts.abstract.part
+]

package/src/app/kireji/issue-tracker/sections/issues/1776193941/description

@@ -0,0 +1 @@
+It might be nice to implement a minimal markdown-to-hml converter. This would be useful for ensuring that certain documents are standardized and associated with content and not presentation.

package/src/app/kireji/issue-tracker/sections/issues/1776193941/part.json

@@ -0,0 +1,3 @@
+{
+ "extends": "issue.."
+}

package/src/app/kireji/issue-tracker/sections/issues/1776193941/priority

@@ -0,0 +1 @@
+C

package/src/app/kireji/issue-tracker/sections/issues/1776193941/title

@@ -0,0 +1 @@
+Implement Markdown Support

package/src/app/kireji/issue-tracker/sections/issues/1776204452/description

@@ -0,0 +1 @@
+Consider merging the user landing model with framework's built-in landing model instead of merely replacing it. Also, consider a dynamic per-origin landing model (or even route ID) tweak. This can allow apps to "open themselves" on the server or worker before the page is rendered. Currently, there is a delay where apps that are not opened but are the current host are only opened after it is detected that they are missing from the open tabs list.

package/src/app/kireji/issue-tracker/sections/issues/1776204452/part.json

@@ -0,0 +1,3 @@
+{
+ "extends": "issue.."
+}

package/src/app/kireji/issue-tracker/sections/issues/1776204452/priority

@@ -0,0 +1 @@
+C

package/src/app/kireji/issue-tracker/sections/issues/1776204452/title

@@ -0,0 +1 @@
+Dynamic Landing Model

package/src/app/kireji/issue-tracker/sections/issues/1776204550/description

@@ -0,0 +1 @@
+Consider integrating tree-shaking pass for abstracts during the pre- or post-hydration build phase.

package/src/app/kireji/issue-tracker/sections/issues/1776204550/part.json

@@ -0,0 +1,3 @@
+{
+ "extends": "issue.."
+}

package/src/app/kireji/issue-tracker/sections/issues/1776204550/priority

@@ -0,0 +1 @@
+C

package/src/app/kireji/issue-tracker/sections/issues/1776204550/title

@@ -0,0 +1 @@
+Tree Shaking

package/src/app/kireji/issue-tracker/sections/issues/1776204640/affects_.js

@@ -0,0 +1,3 @@
+return [
+ _.parts.abstract.part
+]

package/src/app/kireji/issue-tracker/sections/issues/1776204640/description

@@ -0,0 +1,5 @@
+Implement and test source code mapping functionality to relate errors and console logs back to the source files that generated them.
+
+This task is in progress. Source mapping generation and inlining has been implemented. Currently, there are some unknown errors with linking to the correct files from chrome and some problems with getting Node.js to recognize and reflect the source maps.
+
+Consider publishing all files with a bottom link to an external source map 3 file that can easily be generated and cached server-side

package/src/app/kireji/issue-tracker/sections/issues/1776204640/part.json

@@ -0,0 +1,3 @@
+{
+ "extends": "issue.."
+}

package/src/app/kireji/issue-tracker/sections/issues/1776204640/priority

@@ -0,0 +1 @@
+B

package/src/app/kireji/issue-tracker/sections/issues/1776204640/status

@@ -0,0 +1 @@
+doing

package/src/app/kireji/issue-tracker/sections/issues/1776204640/title

@@ -0,0 +1 @@
+Source Mapping

package/src/app/kireji/issue-tracker/sections/issues/1776204869/description

@@ -0,0 +1 @@
+Make title-bar and other desktop experience css dynamic (because it can be disabled in the config). Currently, some unused desktop components may be still be present in CSS rules in the final snapshots.

package/src/app/kireji/issue-tracker/sections/issues/1776204869/part.json

@@ -0,0 +1,3 @@
+{
+ "extends": "issue.."
+}

package/src/app/kireji/issue-tracker/sections/issues/1776204869/priority

@@ -0,0 +1 @@
+C

package/src/app/kireji/issue-tracker/sections/issues/1776204869/status

@@ -0,0 +1 @@
+doing

package/src/app/kireji/issue-tracker/sections/issues/1776204869/title

@@ -0,0 +1 @@
+Dynamic Desktop CSS

package/src/app/kireji/issue-tracker/sections/issues/1776204979/affects_.js

@@ -0,0 +1,3 @@
+return [
+ _.app.kireji
+]

package/src/app/kireji/issue-tracker/sections/issues/1776204979/description

@@ -0,0 +1 @@
+Consider breaking the kireji app drag-and-drop's drop handler (which currently handles both drop and click behavior) into separate "click" and "drop" handlers.

package/src/app/kireji/issue-tracker/sections/issues/1776204979/part.json

@@ -0,0 +1,3 @@
+{
+ "extends": "issue.."
+}

package/src/app/kireji/issue-tracker/sections/issues/1776204979/priority

@@ -0,0 +1 @@
+C

package/src/app/kireji/issue-tracker/sections/issues/1776204979/title

@@ -0,0 +1 @@
+Split Kireji App Drag-and-Drop Handlers

package/src/app/kireji/issue-tracker/sections/issues/1776205152/affects_.js

@@ -0,0 +1,4 @@
+return [
+ _.app.kireji.editor.tabGroup,
+ _.parts.abstract.permutation
+]

package/src/app/kireji/issue-tracker/sections/issues/1776205152/description

@@ -0,0 +1,30 @@
+Implement dynamic part instancing. The final implementation should be able to act as the prototype for both a combination abstract and a permutation abstract. It should be possible to nest these abstracts. These new abstracts will then replace the kireji app tab group and the redundant functionality for the existing permutation abstract (and, by extension, windows.desktop.parts). Window stacking will then be implemented as a nested permutation inside of the outer open windows (open task list) permutation.
+
+During this process, investigate the most performant method of scanning and updating individual instances when comparing the rendered state to the newly set state. The current approach (seen in tab group and legacvy permutation parts) is a dead-simple approach and more performant approaches likely exist. Consider whether this should occur in the parent of a dynamic part during distribute view update or just view update.
+
+Suggestions and considerations:
+1. Instantiate a concrete instance of an abstract part per collection item. Offload all per-item logic there.
+   - Such a part will have optional subparts 'instance' and 'meta'
+   - "instance" corresponds to each instance part's statically-sized data model
+     - which also receives its specific subject assignment from the outside (not part of it's route ID)
+   - "meta" (name pending) corresponds to a non-instance-specific part whose cardinality is dependant upon the number of instances.
+     - get its implementation details by generalizing the active and preview tab data in the tab group. 
+     - At build time, the parent permutation will need to be able to query this part to get its cardinality once for every instance up to the max count.
+     - This part can support mixes, matches, etc. and might even be the ideal place to place a sub-permutation.
+2. Convert the tab group to use this abstract type.
+
+- How do we inspect the states of existing tab instances in `kireji.app`?
+  - Files will be easy: they are part of the abstract.
+  - Perhaps the state space box depicts an array of instance space states instead of the single state? Perhaps that is all that is needed?
+  - Then, how do we depict the states of subparts of the parent part? Do we simply have an array for the entire instance part's tree?
+  - We might need "push", "pop", "insert", "splice" and/or similar array methods to make it easier to modify the instance set on the fly.
+
+- What is the arithmetic of the taskbar and the windows?
+  + Outside of the per-window state, we have the following permutation data:
+    1. The data of which tasks are open, without considering order
+       (this is a simple subset of the available applications).
+    2. The data of the order of the given subset on the task bar
+    3. The data of the stacking order of the given subset on the desktop
+       - Special considerations need to be taken with regards to stacking of windows which are considered full-screened and those considered maximized. How can (and why should) full-screened applications have a window order when they always hide one another? Is it merely to keep their place when they depart from full screen?
+
+- The equation generation (mathML() method) will need to factor in all aspects when deciding how to expand to different depths.

package/src/app/kireji/issue-tracker/sections/issues/1776205152/part.json

@@ -0,0 +1,3 @@
+{
+ "extends": "issue.."
+}

package/src/app/kireji/issue-tracker/sections/issues/1776205152/priority

@@ -0,0 +1 @@
+C

package/src/app/kireji/issue-tracker/sections/issues/1776205152/status

@@ -0,0 +1 @@
+doing

package/src/app/kireji/issue-tracker/sections/issues/1776205152/title

@@ -0,0 +1 @@
+Add Dynamic Parts

package/src/app/kireji/issue-tracker/sections/issues/1776205544/description

@@ -0,0 +1,5 @@
+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.

package/src/app/kireji/issue-tracker/sections/issues/1776205544/links_.js

@@ -0,0 +1 @@
+return [kirejiIssues[1776208669]]

package/src/app/kireji/issue-tracker/sections/issues/1776205544/part.json

@@ -0,0 +1,3 @@
+{
+ "extends": "issue.."
+}

package/src/app/kireji/issue-tracker/sections/issues/1776205544/title

@@ -0,0 +1 @@
+Rework the Kireji URL Format

package/src/app/kireji/issue-tracker/sections/issues/1776205973/affects_.js

@@ -0,0 +1,3 @@
+return [
+ _.parts.abstract.mesh
+]

package/src/app/kireji/issue-tracker/sections/issues/1776205973/description

@@ -0,0 +1,6 @@
+There are four potential improvements that can be used to refine mesh raycasting to improve edge sliding and potentially performance (if necessary).
+
+1. When the angle of the line through the opposing neighbors appears exactly straight, consider searching in a wider radius for asymmetry in the mesh boundary. This can help prevent dead stops when the force vector is exactly perpendicular to a straight portion of a very gently angled edge.
+2. Consider memoizing triangle neighbors and offering a NEIGHBORS_ONLY argument into the function that determines which triangle a given point falls on. This might improve raytracing performance but it might also introduce edge cases (for example, for meshes with tris that are very thin slivers).
+3. For accurate "friction", we should reduce the speed of the vector-to-nearest-boundary-neighbor proportionally to how far that vector deviates from true force vector.
+4. When the ray casting time limit does not provide enough time to make a full diagonal move, consider moving to one of the two 4-point neighbors that sits between the current ray position and the target diagonal neighbor.

package/src/app/kireji/issue-tracker/sections/issues/1776205973/part.json

@@ -0,0 +1,3 @@
+{
+ "extends": "issue.."
+}

package/src/app/kireji/issue-tracker/sections/issues/1776205973/priority

@@ -0,0 +1 @@
+C

package/src/app/kireji/issue-tracker/sections/issues/1776205973/title

@@ -0,0 +1 @@
+Refine Mesh Ray Casting

package/src/app/kireji/issue-tracker/sections/issues/1776206413/affects_.js

@@ -0,0 +1,3 @@
+return [
+ _.parts.abstract.mesh
+]

package/src/app/kireji/issue-tracker/sections/issues/1776206413/description

@@ -0,0 +1 @@
+For the affected parts, validate the incoming MODEL and handle out-of-range data.

package/src/app/kireji/issue-tracker/sections/issues/1776206413/part.json

@@ -0,0 +1,3 @@
+{
+ "extends": "issue.."
+}

package/src/app/kireji/issue-tracker/sections/issues/1776206413/priority

@@ -0,0 +1 @@
+C

package/src/app/kireji/issue-tracker/sections/issues/1776206413/title

@@ -0,0 +1 @@
+Validate ModelToRouteID Inputs

package/src/app/kireji/issue-tracker/sections/issues/1776206609/affects_.js

@@ -0,0 +1,3 @@
+return [
+ _.parts.abstract.partOutliner
+]

package/src/app/kireji/issue-tracker/sections/issues/1776206609/description

@@ -0,0 +1 @@
+The children of collapsed outliner items should not be rendered into the snapshot HTML as it bloats the fetch size for invisible items. Instead, they can be rendered during hydration. Furthermore, this can help prevent icons from being inlined in server-rendered snapshot CSS.

package/src/app/kireji/issue-tracker/sections/issues/1776206609/part.json

@@ -0,0 +1,3 @@
+{
+ "extends": "issue.."
+}

package/src/app/kireji/issue-tracker/sections/issues/1776206609/priority

@@ -0,0 +1 @@
+B

package/src/app/kireji/issue-tracker/sections/issues/1776206609/title

@@ -0,0 +1 @@
+Optimize Outliner Snapshot

package/src/app/kireji/issue-tracker/sections/issues/1776206848/affects_.js

@@ -0,0 +1,3 @@
+return [
+ _.parts.abstract.part
+]

package/src/app/kireji/issue-tracker/sections/issues/1776206848/description

@@ -0,0 +1 @@
+Add a post-build validation stage that iterates over every instance and runs each part's own validation step. This allows each part to stop the build if the build process did not run correctly. A good example for the root part: validating that there was a non-zero and non-negative bigint assigned to its cardinality property. Like the build step, this validation step would be run from the prototype up towards the final concrete part. Check for all parts (such as the scroller) which can throw an error during their build stage and determine if that check can wait until post-build.

package/src/app/kireji/issue-tracker/sections/issues/1776206848/part.json

@@ -0,0 +1,3 @@
+{
+ "extends": "issue.."
+}

package/src/app/kireji/issue-tracker/sections/issues/1776206848/priority

@@ -0,0 +1 @@
+B

package/src/app/kireji/issue-tracker/sections/issues/1776206848/title

@@ -0,0 +1 @@
+Post-Build Validation

package/src/app/kireji/issue-tracker/sections/issues/1776207072/description

@@ -0,0 +1 @@
+Whether the browser is using the bfcache, going across origins, etc. there should always be a perfectly reliable forward and back behavior. Currently, this is partially implemented but there are occasionally unexpected bugs where a view goes out of sync with state during forward or backward navigation. These bugs need to be found and fixed. Furthermore, make sure that undo immediately after an upgrade no longer leads to soft lock (reported some time ago).

package/src/app/kireji/issue-tracker/sections/issues/1776207072/part.json

@@ -0,0 +1,3 @@
+{
+ "extends": "issue.."
+}

package/src/app/kireji/issue-tracker/sections/issues/1776207072/status

@@ -0,0 +1 @@
+doing

package/src/app/kireji/issue-tracker/sections/issues/1776207072/title

@@ -0,0 +1 @@
+Seamless Forward/Back Navigation

package/src/app/kireji/issue-tracker/sections/issues/1776207212/description

@@ -0,0 +1 @@
+Finish the security setup on the server. This includes creating headers like 'Content-Security-Policy' and 'Permissions-Policy'. Applications should get an A grade when scanned by most third-part vulnerability scanners. This improves the reputation and safety of kireji apps.

package/src/app/kireji/issue-tracker/sections/issues/1776207212/part.json

@@ -0,0 +1,3 @@
+{
+ "extends": "issue.."
+}

package/src/app/kireji/issue-tracker/sections/issues/1776207212/status

@@ -0,0 +1 @@
+doing

package/src/app/kireji/issue-tracker/sections/issues/1776207212/title

@@ -0,0 +1 @@
+Secure Against Cross-Site Scripting

package/src/app/kireji/issue-tracker/sections/issues/1776207331/affects_.js

@@ -0,0 +1,5 @@
+return [
+ _.parts.desktop.taskBar.tray,
+ _.parts.desktop.taskBar.tray.share,
+ _.parts.desktop.taskBar.tray.fullscreen
+]

package/src/app/kireji/issue-tracker/sections/issues/1776207331/description

@@ -0,0 +1 @@
+Check if features like native share and full screen truly exist and are supported on the user agent. If not, hide the tray button for those features. Currently, tray buttons for those features are all currently hidden.

package/src/app/kireji/issue-tracker/sections/issues/1776207331/part.json

@@ -0,0 +1,3 @@
+{
+ "extends": "issue.."
+}

package/src/app/kireji/issue-tracker/sections/issues/1776207331/status

@@ -0,0 +1 @@
+doing

package/src/app/kireji/issue-tracker/sections/issues/1776207331/title

@@ -0,0 +1 @@
+Dynamic Task Bar Tray Icons

package/src/app/kireji/issue-tracker/sections/issues/1776207644/description

@@ -0,0 +1 @@
+Implement reliable cross-origin behavior for PWAs and apps that are using the javascript fullscreen API. By default, state is lost when moving from one origin to another inside of installed PWA. This could be implemented, for example, by detecting that the application is in fullscreen or is in a PWA and using "soft-switching" to give the illusion of going cross origin while actually remaining within the starting origin itself. It could also include methods such as implementing a visual clue that indicates that the current application is a preview of another, embedded within the first, along with an option to navigate to said app in another tab/PWA window. For PWAs, investige cross-PWA linking and see what the best user experience is for this. Currently, PWA capability are fullscreen via the API are disabled until this is resolved. Furthermore, PWAs install with a static name - we should use the static, short, menu-compatable title of the app as its PWA title and not its dynamic page title. Installed PWAs reset to the starting state when closing and opening again. This should be fixed - they should probably start in the last place they left off. Hopefully, a local storage API and a "dummy" starting state can resolve this.

package/src/app/kireji/issue-tracker/sections/issues/1776207644/links_.js

@@ -0,0 +1 @@
+return [kirejiIssues[1776211364]]

package/src/app/kireji/issue-tracker/sections/issues/1776207644/part.json

@@ -0,0 +1,3 @@
+{
+ "extends": "issue.."
+}

package/src/app/kireji/issue-tracker/sections/issues/1776207644/priority

@@ -0,0 +1 @@
+B

package/src/app/kireji/issue-tracker/sections/issues/1776207644/status

@@ -0,0 +1 @@
+doing

package/src/app/kireji/issue-tracker/sections/issues/1776207644/title

@@ -0,0 +1 @@
+Cross-Origin PWA

package/src/app/kireji/issue-tracker/sections/issues/1776208336/affects_.js

@@ -0,0 +1,3 @@
+return [
+ _.parts.abstract.part
+]

package/src/app/kireji/issue-tracker/sections/issues/1776208336/description

@@ -0,0 +1 @@
+Make the applications interactive when using Edge on Xbox One. Investigate and implement support for other consoles.

package/src/app/kireji/issue-tracker/sections/issues/1776208336/part.json

@@ -0,0 +1,3 @@
+{
+ "extends": "issue.."
+}

package/src/app/kireji/issue-tracker/sections/issues/1776208336/priority

@@ -0,0 +1 @@
+C

package/src/app/kireji/issue-tracker/sections/issues/1776208336/title

@@ -0,0 +1 @@
+Console Support

package/src/app/kireji/issue-tracker/sections/issues/1776208669/description

@@ -0,0 +1 @@
+Figure out if there's any way to fix this error on google: "Points to the domain's root URL (the homepage), instead of an equivalent page of content" (this appears for the home page, "/" path). Currently, we are including link rel=canonical for all redirected pages, determining the canonical link for each page, implementing meta description and using clean, meaningful titles on all apps and pages. Explore Open Graph data for each canonical link https://ogp.me/. We should remove noindex where not needed - for example, explore how this relates to the upcoming URL scheme. Google warns of long load times because of the main thread blocking caused by the booting of build.js script. Reduce this if at all possible. Perform https://pagespeed.web.dev/analysis/ for all apps and pages.

package/src/app/kireji/issue-tracker/sections/issues/1776208669/links_.js

@@ -0,0 +1 @@
+return [kirejiIssues[1776205544]]

package/src/app/kireji/issue-tracker/sections/issues/1776208669/part.json

@@ -0,0 +1,3 @@
+{
+ "extends": "issue.."
+}

package/src/app/kireji/issue-tracker/sections/issues/1776208669/status

@@ -0,0 +1 @@
+doing

package/src/app/kireji/issue-tracker/sections/issues/1776208669/title

@@ -0,0 +1 @@
+Search Engine Optimization

package/src/app/kireji/issue-tracker/sections/issues/1776208910/affects_.js

@@ -0,0 +1,3 @@
+return [
+ _.parts.abstract.part
+]

package/src/app/kireji/issue-tracker/sections/issues/1776208910/description

@@ -0,0 +1 @@
+Add alt attributes for all images. Allow deep zoom for low-vision users. Headings shouldn't skip levels (for example, an h4 appearing after an h1 with no h2 or h3 in-between).

package/src/app/kireji/issue-tracker/sections/issues/1776208910/part.json

@@ -0,0 +1,3 @@
+{
+ "extends": "issue.."
+}

package/src/app/kireji/issue-tracker/sections/issues/1776208910/title

@@ -0,0 +1 @@
+Improve Accessability

package/src/app/kireji/issue-tracker/sections/issues/1776209115/affects_.js

@@ -0,0 +1,3 @@
+return [
+ _.parts.desktop.taskBar.menu
+]

package/src/app/kireji/issue-tracker/sections/issues/1776209115/description

@@ -0,0 +1 @@
+The task menu can often be longer than the available space on mobile devices and short client windows. Add arrows indicating scrollability in the task menu. Add scroller to the task menu.

package/src/app/kireji/issue-tracker/sections/issues/1776209115/links_.js

@@ -0,0 +1,3 @@
+return [
+ kirejiIssues[1776263309],
+]

package/src/app/kireji/issue-tracker/sections/issues/1776209115/part.json

@@ -0,0 +1,3 @@
+{
+ "extends": "issue.."
+}

package/src/app/kireji/issue-tracker/sections/issues/1776209115/title

@@ -0,0 +1 @@
+Mobile-Friendly Task Menu

package/src/app/kireji/issue-tracker/sections/issues/1776209268/description

@@ -0,0 +1,5 @@
+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 <anonymous>)`
+
+This will lock the system for those users. Consider approaches to resolve this.

package/src/app/kireji/issue-tracker/sections/issues/1776209268/part.json

@@ -0,0 +1,3 @@
+{
+ "extends": "issue.."
+}

package/src/app/kireji/issue-tracker/sections/issues/1776209268/priority

@@ -0,0 +1 @@
+B

package/src/app/kireji/issue-tracker/sections/issues/1776209268/title

@@ -0,0 +1 @@
+Feature Support Fallbacks

package/src/app/kireji/issue-tracker/sections/issues/1776211364/affects_.js

@@ -0,0 +1,6 @@
+return [
+ _,
+ _.parts.desktop,
+ _.parts.desktop.taskBar,
+ _.parts.desktop.windows
+]

package/src/app/kireji/issue-tracker/sections/issues/1776211364/description

@@ -0,0 +1 @@
+After the implementation of dynamic instancing, but before cross-origin PWA, implement restored windows on desktop.parts. Consider having other hosts in the Demo Ecosystem forward back to desktop.parts. Restored windows have their own subpermutation over the pinned (task bar) apps permutation. Note: an open app is actually just an app which is pinned to the task bar, but only those pinned apps can be viewed. These pinned tasks should be able to be reordered by dragging and dropping. Title bars should have a restore button. The desktop application should become an abstract which can be extended to create a desktop at any address so that framework users can implement all of their apps in a single domain if they want. Consider a "maximized on open" setting (or, conversely, a default window state) so that apps which are not currently pinned are opened into the given configuration as they are pinned. Forwarding all domains to the desktop (while pinning the apps that were just visited, especially if pinned maximized) would eliminate cross-origin full-screen and PWA problems. Consider if full-screened apps should have taskbar and titlebar visible. The presentation of sites on first visit should be considered - users won't know that it is an overall desktop they are visiting or this could distract them from the specific domain's intended content. Canonical links and SEO per-domain must still be handled correctly. Consider if an unopened task can be dragged from the menu and/or desktop in order to open it (pin and view it). Restored windows should be movable and resizable.

package/src/app/kireji/issue-tracker/sections/issues/1776211364/links_.js

@@ -0,0 +1,5 @@
+return [
+ kirejiIssues[1776262432],
+ kirejiIssues[1776207644],
+ kirejiIssues[1776205152],
+]

package/src/app/kireji/issue-tracker/sections/issues/1776211364/part.json

@@ -0,0 +1,3 @@
+{
+ "extends": "issue.."
+}

package/src/app/kireji/issue-tracker/sections/issues/1776211364/priority

@@ -0,0 +1 @@
+B

package/src/app/kireji/issue-tracker/sections/issues/1776211364/status

@@ -0,0 +1 @@
+doing

package/src/app/kireji/issue-tracker/sections/issues/1776211364/title

@@ -0,0 +1 @@
+Full Desktop Window Support

package/src/app/kireji/issue-tracker/sections/issues/1776212048/affects_.js

@@ -0,0 +1,3 @@
+return [
+ _.parts.desktop
+]

package/src/app/kireji/issue-tracker/sections/issues/1776212048/description

@@ -0,0 +1 @@
+Add a welcome app (perhaps, welcome.desktop.parts) which provides tips that the user can walk through.