Upstream — what we're waiting on
An index, not a record. The issues on the owning repo are the record: the
context, the workaround and the suggestion live there, self-contained for
someone who has never seen this repo. Keeping a second copy here would drift —
the issue gets refined in discussion while the local copy quietly ages into a
description of a problem that has moved (practices/cross-project.md).
So each row is a link and one line. Mark ✅ RESOLVED (fixed in pkg@version)
when it lands, and close the issue.
Status lives on the virta board (since 2026-10-01): each row was imported
as a card, tagged waiting-upstream while the issue is open and
fixed-upstream while a workaround here still has to go. A row below can be
older than its card; when they disagree, the card wins.
tosijs-3d
| Finding | Issue | |
|---|---|---|
| 1 | No way to touch a mesh. Accepted and BUILT on main as <tosi-b3d-interactive>, shipping in 0.7.3 — adopt it and port our world rules onto it |
#36 |
| 2 | ✅ RESOLVED (tosijs-3d@0.7.4–0.7.5) — vector3d/euler3d, ui.fieldGroup, a summonable on-screen keyboard, select3d menus, iconGrid3d, and popups that escape their panel. Panels size to content, which retires every hand-tuned height |
#37 |
| 3 | No manipulator, and b3d-panel's coloured axes look exactly like one |
#38 |
| 4 | ✅ RESOLVED (tosijs-3d@0.7.2) — destroyable="off" landed, credited to this project |
#39 |
| 5 | b3d-turret/b3d-launcher take no library, so a turret cannot have its own mesh |
#34 |
| 6 | b3d-spawner is player-relative — no way to spawn at an authored place |
#40 |
| 7 | A scene-owned clock: effect timing can be scaled, craft motion cannot | #41 |
| 9 | ✅ RESOLVED (tosijs-3d@0.7.4) — getManifest(), getInfo(name) without instantiating, and getNames() narrows to declared items. Measured upstream at 559 raw nodes vs 131 declared |
#45 |
| 10 | ✅ RESOLVED (tosijs-3d@0.7.4) — the normal map is generated procedurally, so there is no file and no path; an explicit normalMap that fails now logs instead of silently checkerboarding |
#46 |
| 11 | ✅ RESOLVED (tosijs-3d@0.8.1), workaround retired: a uniform scale is the element's scale; a per-axis one still goes on the node, kept through the element's re-renders (#105) — b3d-destroyable cannot scale a library-backed piece at all — size is the placeholder cube's edge and is ignored once library is set. Measured: width identical at scale 1, 2 and 4 |
#47 |
| 12 | ✅ RESOLVED (tosijs-3d@0.8.1), workaround retired: rotation is the element's rx/ry/rz alone — b3d-destroyable drops rx/ry/rz — instantiate is called with position only, so a library-backed piece cannot be rotated at all. Measured: authored rot: [0,45,0] left the footprint identical |
#48 |
| 13 | b3d-destroyable removed before its lib.ready.then instantiate resolves ORPHANS the node — nothing disposes it, ever. Measured: 4 rapid edits left 4 copies and 210 meshes where there were 81, and it never recovered |
#49 |
| 14 | ✅ RESOLVED (tosijs-3d@0.7.4) — numeric fields scrub and type; slider3d's step always quantised and is now documented. Our snap cyclers STAY: they carry a 0 sentinel plus a doubling series, which is a cycler's job, not a slider's |
#50 |
| 15 | <tosi-ensemble> in a plain <tosi-b3d> renders perfectly, and the editor with hideChrome renders perfectly, while the full editor beside them renders dark. The editor CHROME breaks the scene. The GL evidence (gl.isProgram false, glError 1282) was real; my explanation of it — a shared SkyMaterial program deleted by material churn — was not, and reducing to one SkyMaterial did not fix it |
#51 |
| 19 | ✅ RESOLVED (tosijs-3d@0.8.1), workaround retired; tests/still-sky.pw.ts takes five cold loads with a 1 am control — A STILL sky updates once and never recovers. b3d-skybox re-runs updateSky from its frame observer only when timeOfDay !== _lastSkyTime, and updateSky writes sunPosition/rayleigh/turbidity only inside if (sunEl?.light != null). The sun is a separate element whose light appears on its own schedule, so a first call that lands too early leaves the SkyMaterial at its defaults — a dark sky that reads as night. The default realtimeScale: 10 hides this by drifting the clock so the gate reopens every tick; set it to 0 for a reproducible scene and four loads in five come up dark. Ask: re-run when the INPUTS change (or when a sun appears), not only when the clock does |
#55 |
| 25 | ✅ RESOLVED (tosijs-3d@0.8.0) — slider3d gained scale: 'log' | 'log2', snap and zeroStop, and skyboxSchema() ships realtimeScale as x-scale: log + x-zero-stop. ADOPTED — schema-panel reads x-zero-stop and the cycler is gone |
#62 |
| 26 | ✅ RESOLVED (tosijs-3d@0.8.0) — tosijs-3d/scene-schemas ships JSON Schema for all nine primitives plus the hemispheric light, headless (verified importing it under Node here), with an extra override argument and SCENE_OMITTED naming the positional attributes a feature panel should drop. ADOPTED — pick() in features-scene.ts takes the shape of all ten from upstream, and runtime/scene-schemas.test.ts fails if we restate a range, unit, enum or scale. It found four more silent-nothing controls on the way in (underwaterFog typed boolean, preset: birds, where: air, mode: none), all four now migrated in existing files |
#63 |
| 24 | ✅ RESOLVED; RECEIVING END READY, NO CALLER YET (tosijs-3d@0.8.0) — plain-JSON curves, normalizeCurve, and evaluateCurve(points, t) with no DOM (verified under Node here), plus curveProgram3d / curveMarkers with handleCommit(value, describe). schema-panel dispatches x-widget: 'curve' and 'light-program' and both are pinned by test — but nothing in this repo declares a curve: the lamp hands its whole settings to lightEditor3d. The natural first caller is provinceClimateSchema(), whose three channels are curves; upstream shipped it deliberately without a consumer, because the province REGISTRY has to exist first and that is written down as their step 1. Nothing to build here, and nothing to file |
#61 |
| 23 | ✅ RESOLVED and ADOPTED (tosijs-3d@0.8.0) — spinner3d runs in the insert palette while the shelf mounts. Measured with cache-busted kit URLs: "loading 4 kits…" up from 1.0s to 2.0s, then gone. Indeterminate rather than progress3d, because mountLibraries resolves once for the whole shelf and faking a fraction is worse than admitting there is none |
#60 |
| 27 | ✅ RESOLVED, PARTLY ADOPTED (tosijs-3d@0.8.0) — kind: 'button' + menu(row) is adopted: the piece list has per-row Enable/Disable, Duplicate and Delete. kind: 'icon' deliberately NOT adopted — an icon column reads its value as an iconGlyph NAME, and our feature icons are EMOJI by the registry's contract (registerFeature({ icon: '☀️' })), which is what lets a consumer's own feature appear with a glyph the editor never knew. Names would make every consumer register an SVG too, to gain nothing an author sees. So the missing scene vocabulary is moot for us |
#64 |
| 28 | 🟡 HALF (tosijs-3d@0.8.0) — ADOPTED for the schema — terrainSchema() retired the invented units and the unbounded reach; our floor on tileSize stays, because it is the PRODUCT of two sliders that kills the tab and a schema cannot say that. No terrain EDITOR yet, and regenerate-on-change is still ours |
#66 |
| 29 | ✅ RESOLVED and ADOPTED (tosijs-3d@0.8.0) — the piece list is a table per group with one filter field driving setFilter on the LIVE tables, so scroll, selection and focus survive typing. Measured here: filtering out the selected flagship left it selected and it came back when the filter cleared |
#67 |
| 30 | ✅ RESOLVED (tosijs-3d@0.8.0) — source specifiers carry .js, and a test asserts it of the SOURCE so it fails at authoring time rather than after a publish. Deep package subpaths too. Verified here: import 'tosijs-3d/scene-schemas' and 'tosijs-3d/curve' both resolve under Node |
#69 |
| 28 | ✅ RESOLVED (tosijs-3d@0.8.0) — lightEditor3d's teaching copy is opt-in now, so an embedded widget no longer ships demo prose into a consumer's panel |
#65 |
| 22 | ✅ RESOLVED and ADOPTED (tosijs-3d@0.8.0) — scene.whenDisposed(cb) exists and returns an unsubscribe. We had already written against it; with the peer floor at 0.8.0 the call is no longer optional-chained, so a missing method would be loud rather than silently never observing disposal |
#58 |
| 21 | 🟡 FIXED UPSTREAM, UNVERIFIED HERE (tosijs-3d@0.8.0, #58) — "a move no longer costs a scene, and a genuine removal disposes the engine". Our deferred mount and lazy kit shelf are MITIGATIONS for this and #56 and stay until ~20 SPA round trips say otherwise. n=4 cannot tell "fixed" from "rarer" | #58 |
| 20 | A popup on the DOM layer cannot be moved. The move/close glyphs are picking-driven and scene-only, so nothing renders in the flat presentation — measured, zero data-presentation nodes in the layer. A keyboard summoned from a right-hand panel opens at x 1471, 360 wide, in a 1719 viewport: 112px off-screen with no way to recover it. Asked for drag on the DOM layer, or a viewport clamp |
#57 |
| 19 | ✅ RESOLVED (tosijs-3d@0.8.1), workaround retired; tests/still-sky.pw.ts takes five cold loads with a 1 am control — Constructing a b3d scene inside another component's rAF render pass corrupts materials — dark sky, WHITE meshes, empty scene, half-loaded scene, ~70% of loads, all one cause. Isolated by side-by-side comparison in one page. We defer our mount to a macrotask and it goes to zero; filed informationally in case b3d should defer its own engine creation, or the rule should be documented |
#56 |
| 17 | ✅ RESOLVED in 0.7.6 — b3d-shadows no longer writes receiveShadows on instanced meshes. The write was already a no-op, so nothing that received shadows stops. Verified here: a full editor load now logs zero of them, where it was ~10,000 |
#53 |
| 18 | ✅ RESOLVED in 0.7.6 — the icon LANGUAGE works on the texture path, so mirrored names resolve everywhere and no iconFlipX on IconGridItem is needed. Root cause was a trailing space in icon-data making a redirect unparseable as a name. Undo is a real ↰ again. ⚠️ iconExists() was added for exactly this check but is NOT re-exported from the barrel, so a consumer still cannot reach it |
#54 |
| 16 | Touch camera: two-finger drag zooms instead of panning, and ⌃drag does not exist on touch — so a tablet cannot pan at all | #52 |
| 8 | ✅ RESOLVED in part (tosijs-3d@0.7.2) — exports is a map now, but it names ./demo-utils explicitly rather than a ./* pattern, so an arbitrary subpath is still unreachable. Closed upstream; we are not reopening, because the case that motivated it (a published, importable subpath) works |
#42 |
| 31 | No colour control, while scene-schemas declares eight format: 'color' properties — four on the sky alone. FieldType has no color, and lightEditor3d sidesteps it with a hue slider. Anyone doing what #63 invites lands here at once. We use a hex inputField meanwhile: no swatch, no preview, and #eeeff is accepted and silently wrong |
#72 |
| 32 | ✅ RESOLVED and ADOPTED (tosijs-3d@0.8.4) — slider3d({ useful }) shades a band on the track and the handle still reaches both ends. schema-panel passes x-useful through; schema-readout.pw.ts asserts the band is on screen and narrower than the track, and fails without the one line |
#83 |
| 33 | ✅ RESOLVED (tosijs-3d@0.8.4, documented) — hover, press and drag over the caption all work, and peek now shows the value BESIDE the caption, deliberately. Our readout test had pinned the old behaviour and was rewritten to read the hovered slider's own visible text |
#84 |
| 34 | ✅ RESOLVED (tosijs-3d@0.8.4) — upstream says x-unit everywhere, with a test rejecting a bare unit. Our translation in pick() is gone; the drift test failed the moment it became unnecessary, which is how we knew |
#85 |
| 35 | ✅ RESOLVED (tosijs-3d@0.8.4) — azimuth is out of skyboxSchema() and documented as ignored. It was already off our panel; a file that sets it now gets unknown-feature-key, a warning, which is true |
#86 |
| 36 | ✅ RESOLVED and ADOPTED (tosijs-3d@0.8.4) — cloudDeckSchema() is in sceneSchemas and our hand-written block is a pick(). Retiring it found drift: our altitude stopped at 5 km, upstream's runs to 12 |
#87 |
| 37 | ✅ RESOLVED and ADOPTED (tosijs-3d@0.8.4) — starfield attributes rebuild the starfield when they change. Our re-mount is deleted, and land-and-sky.pw.ts still sees all six pinned faces arrive, 4/4 runs |
#88 |
| 38 | 🟡 MOSTLY RESOLVED (tosijs-3d@0.8.4) — atmosphere, dust, zenithTint/horizonTint/tintStrength, and <tosi-b3d-moon> (up to four, phase from the real sun), plus an Atmosphere group in the demo. Not yet: several suns. Not yet adopted here: see TODO |
#89 |
| 39 | ✅ RESOLVED and ADOPTED (tosijs-3d@0.8.4) — /sky/0.8.3/… and /sky/0.8.4/…, each with a manifest.json. land-and-sky.json pins 0.8.4 and states starfieldDataSize. (The versioned files are still served max-age=600; harmless for correctness, only a missed caching win) |
#90 |
| 40 | ✅ RESOLVED and ADOPTED (tosijs-3d@0.8.4) — fetched fields carry format: 'uri-reference' (+ x-keywords). Scene features stamp x-fetched from the FULL upstream schema, and validate holds every one to the library https rule |
#91 |
| 41 | ✅ RESOLVED (tosijs-3d@0.8.9), adopted — No moonSchema() — <tosi-b3d-moon> (0.8.4) is the one primitive we describe by hand again; two of its five ranges are ours |
#93 |
| 42 | A key is delivered twice when a handler re-renders its fieldGroup mid-keystroke — since the #82 fix. Our rename field doubled every character; deferred past the event, 3/3 single |
#94 |
| 43 | ✅ RESOLVED (tosijs-3d@0.8.9) for inputField; the editor's other two routes were #100 and our own field group — inputField leaks itself and its host. Each field adds its keyboard-glyph repaint closure to a module-level Set (autoKeyboardListeners, keyboard.js) that is never pruned, so every editor visit retains ~3,970 nodes and its disposed scene and engine. Found by the re-parent lane slowing 5 s → 40 s per trip; located with a heap-snapshot retainer path. Present since at least 0.8.4. Our re-parent lane is red until it lands |
#96 |
| 44 | ✅ RESOLVED (tosijs-3d@0.8.9); features not yet written — No schema for the weather and decoration elements — weather cell, lightning, light shafts, decorator, trail. We expose a primitive only through its schema, so none of 0.8.5/0.8.6's weather is offered to an ensemble author | #97 |
| 45 | ✅ RESOLVED (tosijs-3d@0.8.9, x-sections), adopted — No schema-driven panel, and the sections live in the demo. Land and Sky hand-writes 43 rows (in step with the schemas today, by hand); our schema-panel.ts is 586 lines of form generator for tosijs-3d's schemas. Asks for schemaPanel3d and x-section |
#98 |
| 46 | ✅ RESOLVED (tosijs-3d@0.8.8, foldSections), adopted — Collapsible sections fold only in <tosi-b3d>'s scene panel. The fold is private (_foldSections); panel3d ignores a row's section, so in our docked panels a 0.8.7 section header is a chevron that does nothing |
#99 |
| 47 | ✅ RESOLVED (tosijs-3d@0.10.8); _tracked/boxTracker removed, the editor disposes the panels it drops — boundValue never unsubscribes, so every widget bound to a tosijs box leaks its panel and its host through tosijs's listener list (+125 listeners per ten rebuilds, flat with binding off). Worked around by _tracked in the editor; suggested fix uses OBSERVER_SHOULD_BE_REMOVED |
#100 |
| 48 | ✅ RESOLVED (tosijs-3d@0.8.13, b3dSchema()), adopted for AO — No schema for <tosi-b3d>'s own attributes: ssaoStrength/ssaoRadius (our AO recommendations need ranges to edit) and windSpeed/windBearingDeg (drifting weather cells, board #3110) |
#101 |
| 49 | ✅ RESOLVED (tosijs-3d@0.10.8); detachLibraryMaterials removed, rapid-edits still checks colour — disposeMeshTree disposes a library's materials when the last instance goes: library source meshes are not in scene.meshes, so the guard misses them and every later instance renders white. Worked around in place-mesh.ts (detachLibraryMaterials) |
#102 |
| 50 | ✅ RESOLVED (tosijs-3d@0.10.8) for the schema and the pin (planetSchema() with x-preset-written, terrain lat/lon); and the links in 0.10.9 (planet.terrain, terrain.planet, selectors; ours name pieces) — For building worlds from their planet (board #3317): no planetSchema(); terrain's schema lacks worldU/worldV (asked for lat/lon attributes); the globe-from-ground link is code |
#103 |
| 51 | ✅ RESOLVED (tosijs-3d@0.10.10); DisposablePanel is an alias of Panel3d — panel3d's declared return type has no dispose(), though 0.10.8 adds one and its CHANGELOG says to call it. Worked around by a local DisposablePanel type |
#104 |
| 52 | ✅ RESOLVED (tosijs-3d@0.10.12): stretch per axis; a built [2, 1, 3] measures 18.108 with our wrapper gone — b3d-destroyable resets the instance's scaling to its uniform scale on every render, so a per-axis scale cannot be kept; a stretched piece lost its stretch on its first move or turn. Worked around by scaleElement re-applying it after each render |
#105 |
| 53 | ✅ RESOLVED (tosijs-3d@0.10.10) — system-bar panels for an app's main chrome: several open, a declared first spot, open at start; typed keys reach a field in one | #106 |
| 54 | ✅ RESOLVED (tosijs-3d@0.10.10) — projected AO missed library (container) materials, so kit pieces were never occluded; our pixel test now asserts it | #107 |
| 55 | ✅ RESOLVED (tosijs-3d@0.10.11): selectionMarker: 'row' — table cannot highlight a selected row without its radio/checkbox marker |
#109 |
| 56 | ✅ RESOLVED (tosijs-3d@0.10.11): panel.reveal(table, table.rowBox(id)) — panel3d has no readable scroll position or reveal(widget) |
#110 |
| 57 | No way to locate a panel's content NODE on screen (contentToClient maps points only); tests/panel-locate.ts measures nodes by attaching the content SVG off-screen |
#117 |
| 58 | <tosi-b3d-effect>'s attributes have no schema (preset, activity, scale, ground): effectRecipeSchema() covers a recipe, not the element, so an effect feature here would have to type its ranges by hand. Shipped in 0.10.17 as effectSchema() |
#118 |
| 59 | Landform options have no schema (volcano, impactCrater, pad, gulley, cover): a volcano province piece (with its own vent effect) cannot be authored without inventing ranges |
#119 |
| 60 | effectRecipeSchema() does not mark its fetched fields (particle texture, sound url), so the effect feature cannot accept a recipe under the https rule |
#120 |
| 61 | slider3d cannot show labelled stops (x-stops: an effect's dormant / semi-active / erupting) |
#121 |
| 62 | tosijs-ui's doc-system button.test-widget is fixed over page content and takes clicks: a click on the Scene list's last row hit it 3 runs in 4; fixed in 1.16.29 (the widget is in the header bar), workaround removed, 4/4 |
tosijs-ui#233 |
| 63 | rig-tool and effect-tool are not embeddable: each makes its own scene, has no change event, and owns its files. Shipped in 0.10.19; the effect tool is hosted on an effect piece | #122 |
| 64 | No element applies a rig recipe at runtime (a character loaded, recipe applied, clip playing): ensemble's figure piece needs one, with figureSchema(), rather than owning skeleton loading itself |
#123 |
| 65 | 0.10.19 regression: an SVG effect picture's onload throws on a texture released before it loaded (clearRect of null): tests/effect.pw.ts "a clean recipe plays" failed 3/3; fixed in 0.10.20 (6/6 after) |
#124 |
| 66 | tosijs-ui: a [[wikilink]] to a missing page builds silently, and titles are slugified rather than resolved (9 dead links here, fixed); fixed in 1.16.29 (titles resolve, the build names a dangling one) |
tosijs-ui#234 |
| 67 | foldSections drops a folded section's rows without disposing them: rows are built (and bound) before folding, so every repaint leaked the folded rows' subscriptions. Worked around by foldDisposing (#3262) |
#127 |
| 68 | timeScale does not slow Babylon animation groups: nothing sets scene.animationTimeScale, so in slow motion a rig kept its full tempo (measured 62.9 frames/s at 1, 74.4 at 0.25). Shipped in 0.11.5; the workaround (AnimationTransport multiplying speedRatio by timeScale) was dropped on adopting 0.12.0, before it could compound |
#128 |
Stopgaps we own, and what retires them
Each of these is local complexity we carry because of a row above. When the issue lands, the workaround goes — a stopgap that outlives its reason is a fork nobody declared. One has already been collected: see the struck-through row.
| Ours | Retired by |
|---|---|
destroyable registers body: true |
✅ #39 |
launchpad is registered editorOnly — authorable, and honestly marked as something the runtime will not build |
#40 |
numberField + DOM key routing + our own active-field trackingvector3d/euler3d put a coordinate on ONE row and ui.fieldGroup owns exclusivity, commit-on-leave and key routing |
✅ #37 (items 1, 7) |
handles-view.ts, and the drag maths in handles.ts |
#38 |
ctx.simTime() defaulting to wall-clock |
#41 |
presets/world's own interactive (reach, activation, refusal) |
🔜 #36 in 0.7.3 |
| The family-cycler + separate list standing in for a hierarchical palette | #37 (list virtualisation still open) |
height: 'fit' is the default and maxHeight scrolls; three separate clipping bugs came from guessing this number |
✅ #37 |
| Deriving palette categories from NAME PREFIXES, when the library now declares real ones | #45 |
waterbump.png |
✅ #46 |
runtime/node-transform.ts — writing rotation AND scale past the element onto the instance root, plus whenMeshed's retryrx/ry/rz (0.8.1) and applies scale/stretch (0.10.12); scaleElement remains |
tosijs-3d #47, #48 |
✅ RESOLVED (tosijs-3d@0.8.4) — a field outside an attached group no longer loses its keys, and fieldGroup.add(field) lets a late field join. Our construction-order fix stays: it is correct, and add makes it a choice rather than a trap |
tosijs-3d #82 |
✅ RESOLVED (tosijs-ui@1.16.0) — the doc site loaded its ESM entry twice (hydrate.js?v=<hash> from the page, ../hydrate.js from the chunks), which is what we had mis-filed as tosijs-3d#78. The entry is hydrate-<hash>.js now; our filter is gone, and a load measures 0 errors and 0 shader failures where it measured 10 and 2 |
tosijs-ui #191 |
place-mesh.ts's reapOrphan — watching for an instance that arrives after its element was removed, and disposing it |
tosijs-3d #49 |
realtimeScale spelled as an enum so it renders as a cyclerx-scale: log + x-zero-stop is a slider that spans decades and still reaches Off. The TOOL snap cyclers stay: a doubling series with a 0 sentinel is a cycler's job, not a slider's |
tosijs-3d #50 |
1.14 removed the DOC SYSTEM from the barrel, not only the doc browser. import 'tosijs-ui' no longer registers <tosi-doc-system>, and nothing says so — the site keeps its nav and layout, so it reads as working, while every html/js fence renders as inert <pre> and the doc-test corpus never appears. Measured on the published site: customElements.get('tosi-doc-system') === false. Fixed here by importing tosijs-ui/doc-system/doc-system.js explicitly; 3d.tosijs.net has the same symptom |
tosijs-ui #159, #158 |
editor.md's toc block in a shape Prettier undoesrequirePragma), so editor.md is back in the format check |
tosijs-ui #165 |
editor.md's calc(100dvh - 4rem), a hand-tuned navbar offset |
tosijs-ui #115 |
Nulling the camera input's private _pointA/_pointB on re-attach |
Babylon (third-party; no upstream row) |
tests/schema-readout.pw.ts finding the slider TRACK by geometry to hover it (tosijs-3d#84). Hover over the caption works on 0.8.3 (measured); kept until #84 closes, since drag was not re-checked |
| — gone in 0.8.4 (tosijs-3d#85)
| pick() translating unit → x-unitThe cloud deck's hand-written ranges — gone in 0.8.4; a pick() now (tosijs-3d#87)
| Re-mounting the skybox when a starfield key changes — gone in 0.8.4 (tosijs-3d#88)
| The moon feature's hand-written ranges (tosijs-3d#93)
| Deferring the piece rename past the keystroke — renameLater (tosijs-3d#94)
| foldDisposing (editor/schema-panel.ts) — disposing the rows foldSections drops; delete it when tosijs-3d#127 ships, checking the two do not dispose a row twice (tosijs-3d#127)
tosijs
| Finding | Issue | |
|---|---|---|
| E | ✅ RESOLVED (tosijs@1.9.2) — a held boxed proxy is a live view of its path. .value used to resolve for SCALAR proxies and return the captured target for OBJECT ones, so one API disagreed with itself and it presents as a failed WRITE. Cost an afternoon here. Our test asserted the bug and is what failed on upgrade |
#35 |
| F | ✅ RESOLVED (tosijs@1.10.0) — Component's [key: string]: any index signature is gone, so tsc finally checks our components. It found this.seabed, an attribute whose declare line was never written and which therefore typed as any for as long as it has existed |
#36 |
| H | An unknown prop is assigned as a PROPERTY, so a props object built from untrusted data can set innerHTML and execute script — confirmed in real Chromium. elements.ts opens by promising construction without innerHTML, and tosijs#26 states the opposite runtime model outright ("an unknown prop is silently dropped"), which is the reading we built on. Half of it was genuinely ours (updateAttrs is element[key] = value) and is fixed here by declaredConfig; the library half protects every other consumer who turns document data into props |
#43 |
| G | ✅ RESOLVED (tosijs@1.10.x); both components use withAttributes() again and bun run build emits — withAttributes() breaks our .d.ts emit — its return type is not nameable from 'tosijs', so tsc -p tsconfig.build.json fails TS2742 and bun run build refuses. It is the shape tosijs's own migration note recommends, and we cannot take it. Using the documented ComponentAttrs alternative meanwhile; fixed upstream and unpublished, so switch when it lands |
#38 |
haltija
| Finding | Issue | |
|---|---|---|
| D | An agent driving a BACKGROUND tab cannot verify rendered output — rAF is throttled, a self-pausing scene stops, and hand-driving the frame loop changed the semantics enough to produce two false diagnoses in one session. Asks for a leased, reusable foreground instance |
#41 |
tosijs-ui
| Finding | Issue | |
|---|---|---|
| E | The documented import 'tosijs-ui/doc-browser' is a no-op, so 1.14 silently removed our doc-test corpus. That module has no top-level side effect, so the bare import is dropped; measured on a clean build, tosi-tests-done/pagesWithTests/createDocBrowser are all absent while live-example's strings are present. The site renders perfectly and window.__docTestResults never appears — our gate went from 5s to a 30s timeout, and without it the corpus would just have stopped existing |
#158 |
| A | Dev-server auth sessions live in new Map(), so every restart invalidates every issued edit link while the 30-day cookie stays valid — it presents as Safari eating cookies |
#114 |
| B | A full-screen page that is ONE element: markdown wraps it in a <p> and nothing in the chain has a definite height, so height: 100% collapses. Suggested fix is raw .html doc pages |
#115 |
| C | The dev server answers a missing asset with the SPA shell — HTML at 200 — so a 404 presents as a silently wrong render | #116 |
| D | describeHolder() with no holder returns a rendered "pid undefined" warning rather than saying there is none — the reader added by #118 tells a caller the opposite of the truth |
#123 |
| F | doc-browser runs the whole test corpus on every localhost page visit (hidden WebGL scenes behind every Playwright test that opens a doc page), and the dev server keeps only the last /report, unattributed. Our helper records every post with its test and page (board #3172) |
#229 |
Not filed, deliberately
prefab means three things. tosijs-3d exports prefab for a registered
(ctx) => Element[] factory (wrecks, debris, spawns); Unity means a serialized
scene object with code; Manta's prefab.ts meant our format's ancestor. Not a
request — nobody should rename anything over it — but a reader coming from Unity
meets a second meaning in the same dependency graph, and it is worth knowing
that is why this project's word is ensemble.