fix(islands): iframe fallback for osis on web build #118
No reviewers
Labels
No labels
prio_critical
prio_low
type_bug
type_contact
type_issue
type_lead
type_question
type_story
type_task
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
lhumina_code/hero_os!118
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "development_mik_osis_iframe_fallback"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
The OSIS island only had an
island-osis-nativecfg arm inIslandContent(seeisland_content.rs:581). Defaultwebbuilds do not enable that feature, so clicking the OSIS dock icon fell through to the dynamic WASM loader, producingFailed to load island WASM 'osis': Island not found: osis (HTTP 404)(since there is nohero_archipelagos_osisbundle on disk either).Mirror the pattern already in tree for
collabandwhiteboard: iframe fallback to/hero_osis/ui/when the native island is not compiled in. The native path is unchanged.Verification
cargo fmt --check— clean.cargo clippy -p hero_os_app --target wasm32-unknown-unknown --no-default-features --features web --all-targets -- -D warnings— clean.web-nativeclippy regression noted in passing (unused import: hero_archipelagos_hero::island::HeroAppatisland_content.rs:64) is pre-existing ondevelopmentHEAD and unrelated to this change.Closes
Refs