Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

web: Improve error when WASM extensions are unsupported but only the module which uses them is available #18838

Conversation

danielhjacobs
Copy link
Contributor

@danielhjacobs danielhjacobs commented Dec 2, 2024

This is somewhat the antithesis of #18528. That PR keeps Ruffle running on browsers without reference types support. This shows a better error on browsers without reference-types support when only the with-extensions WASM module is available for use.

Merging #18399 will break Ruffle on Safari versions below 15 and Pale Moon. We can keep Ruffle working on those browsers, or we can officially designate them to be unsupported.

@danielhjacobs danielhjacobs force-pushed the throw-direct-error-when-reference-types-unsupported branch from c5b9550 to fec7b36 Compare December 2, 2024 20:56
@danielhjacobs danielhjacobs added A-web Area: Web & Extensions T-fix Type: Bug fix (in something that's supposed to work already) labels Dec 2, 2024
@danielhjacobs danielhjacobs force-pushed the throw-direct-error-when-reference-types-unsupported branch from fec7b36 to fede393 Compare December 2, 2024 22:54
@danielhjacobs danielhjacobs changed the title web: Throw an error when reference types are unsupported web: Show a more specific error when reference types are unsupported Jan 3, 2025
@torokati44 torokati44 force-pushed the throw-direct-error-when-reference-types-unsupported branch from 370f815 to f1da32d Compare January 8, 2025 00:11
@torokati44
Copy link
Member

Even though this will (allegedly) probably not be necessary once we go ahead with #18528, I guess it won't hurt to have it in there either.

@torokati44 torokati44 force-pushed the throw-direct-error-when-reference-types-unsupported branch from f1da32d to 7af4d6b Compare January 10, 2025 17:30
@danielhjacobs
Copy link
Contributor Author

danielhjacobs commented Jan 10, 2025

Note: This error should now only appear when using Ruffle on the aforementioned browsers after npm run build is done without dual-wasm, building only the with-extensions module.

@danielhjacobs danielhjacobs changed the title web: Show a more specific error when reference types are unsupported web: Show a more specific error when WASM extensions are unsupported but only the module which uses them is available Jan 10, 2025
@danielhjacobs danielhjacobs changed the title web: Show a more specific error when WASM extensions are unsupported but only the module which uses them is available web: Improve error when WASM extensions are unsupported but only the module which uses them is available Jan 10, 2025
@torokati44
Copy link
Member

Yes. Anyway, it should be harmless, and trivial to revert.

@torokati44 torokati44 merged commit 8bb90c0 into ruffle-rs:master Jan 10, 2025
20 checks passed
@danielhjacobs danielhjacobs deleted the throw-direct-error-when-reference-types-unsupported branch January 10, 2025 18:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-web Area: Web & Extensions T-fix Type: Bug fix (in something that's supposed to work already)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants