Summary
Firefox currently has two major browser-specific regressions:
- Folder-based project save/load is broken.
- The Native Helper takes far too long to reconnect after a page refresh.
These both make Firefox substantially less usable than Chromium-based browsers for normal project workflows.
Environment
- Browser: Firefox
- App: MasterSelects web app
- Date observed: 2026-03-17
Problem 1: Folder save/load is broken in Firefox
Actual behavior
Saving to a project folder and/or loading an existing project folder does not work reliably in Firefox.
Expected behavior
Folder-based project save/load should work the same way it does in Chromium-based browsers.
Impact
This blocks normal project persistence workflows in Firefox.
Problem 2: Native Helper reconnect is extremely slow after refresh in Firefox
Actual behavior
After refreshing the page in Firefox, the Native Helper needs far too long to reconnect.
Expected behavior
After refresh, the Native Helper should reconnect quickly so project and media workflows are usable again without a long wait.
Impact
Refreshing the app in Firefox leaves the user in a degraded state for too long and makes iteration/debugging much slower.
Reproduction
- Open MasterSelects in Firefox.
- Try a folder-based save/load workflow.
- Refresh the page.
- Observe that Native Helper reconnection is much slower than expected.
Notes
- This appears Firefox-specific.
- Chromium-based browsers do not show the same severity for these workflows.
- It is worth checking File System Access / project folder handling differences and Firefox-specific reconnect timing around Native Helper boot/handshake after reload.
Summary
Firefox currently has two major browser-specific regressions:
These both make Firefox substantially less usable than Chromium-based browsers for normal project workflows.
Environment
Problem 1: Folder save/load is broken in Firefox
Actual behavior
Saving to a project folder and/or loading an existing project folder does not work reliably in Firefox.
Expected behavior
Folder-based project save/load should work the same way it does in Chromium-based browsers.
Impact
This blocks normal project persistence workflows in Firefox.
Problem 2: Native Helper reconnect is extremely slow after refresh in Firefox
Actual behavior
After refreshing the page in Firefox, the Native Helper needs far too long to reconnect.
Expected behavior
After refresh, the Native Helper should reconnect quickly so project and media workflows are usable again without a long wait.
Impact
Refreshing the app in Firefox leaves the user in a degraded state for too long and makes iteration/debugging much slower.
Reproduction
Notes