Bugzilla

One thing that would be great to have here is a list of impacted public web platform APIs and then for each of those APIs detail:

1. What the respective specification says a fatal I/O error should mean for this API. (If it doesn't say anything, let's file an issue to discuss with others and link that instead.)
2. What our implementation will do. (It might take a while for the specification to be updated and it seems useful to capture what we do in the interim or in case we decide not to prioritize aligment.)

(One example we discussed (unsure if theoretical) is that the `window.indexedDB` getter might have to handle a fatal I/O error in a special way whereby it still returns an object, but operations on that object end up failing. As the getter itself ought not to throw per the specification and always return the same object, but if an implementation lazily creates that object it might erroneously decide to surface a fatal I/O error during creation.)

One thing that would be great to have here is a list of impacted public web platform APIs and then for each of those APIs detail:

1. What the respective specification says a fatal I/O error should mean for this API. (If it doesn't say anything, let's file an issue to discuss with others and link that instead.)
2. What our implementation will do. (It might take a while for the specification to be updated and it seems useful to capture what we do in the interim or in case we decide not to prioritize aligment.)

(One example that came up (unsure if theoretical) is that the `window.indexedDB` getter might have to handle a fatal I/O error in a special way whereby it still returns an object, but operations on that object end up failing. As the getter itself ought not to throw per the specification and always return the same object, but if an implementation lazily creates that object it might erroneously decide to surface a fatal I/O error during creation.)