Firefox actually works now — the manifest declared background.service_worker, which Firefox doesn't support at all, and relied on chrome.offscreen, an API Firefox has never implemented. The extension would install but do nothing. This is fixed:

• Manifest now declares both background.scripts and background.service_worker — Chrome uses one, Firefox uses the other, each ignores what it doesn't recognize.
• Added a browser_specific_settings.gecko block (extension id, minimum version, and the data_collection_permissions field Mozilla now requires for submissions — please double check the "none" value I set is acink does, that's your call to confirm, not mine).
• The Ancestry legacy-page eval fallback (used to chrome.offscreen) now branches to a Firefox-compatible path instead. - Along the way, testing this live as a temporary Firefox add--only bugs that were separately breaking things: anunconditional navigator.serviceWorker call in popup.js that doesn't exist in Firefox's popup context (this one was nasty — it threw uncaught and silently killed every single collection's ability to register)ers that were mismatched about whether they'd send an asyncresponse, which Firefox flags as an error and Chrome just quietly tolerates. - Verified against Mozilla's own web-ext lint: 0 errors.
• Verified live: logged in, parsed pages, and submitted data successfully in Firefox, side-by-side with Chrome behaving identically.

MyHeritage's redesigned pages are now supported
MyHeritage rolled out a new profile page design a while back (profile-<site>-<id> URLs), and it's been silently falling through to "This website is not yet supported by SmartCopy" ever since. Added as a new, separaew.js) rather than touching the existing one, so nothing about the old MyHeritage support changed.

This includes something we hadn't been able to solve before: full family linking — spouse, children, parents, and siblings, all correctly pulled with
real profile IDs. The new page design doesn't expose parent/sis HTML at all (the click handler reads the link out of a Reactcomponent's internal state, never rendered to the page) — solved by reading the live, rendered page and walking React's own internal data structures to
recover it. Also grabs marriage date/place, which turned out tted even in the old MyHeritage collection.

A cluster of real, previously-silent bugs fixed

• WikiTree: birth date was never being parsed at all (an off-bped it entirely). Also fixed placeholder text like [uncertain]and edit-mode UI text leaking directly into people's names.
• Ancestry works again!: migrated to Ancestry's current page structure (#petors predated this and had been silently returning blank nameson every single

Fixed SmartMatch gender

Fixed Ancestry spouse bug

Fix for FindAGrave

Fixed bug in consistency checks

Update based on API changes at Geni.com

Bug fixes

Fixes issues with Ancestry and MyHeritage

Fix for Ancestry changes