Open Bug 1463422 Opened 6 years ago Updated 1 year ago

Should URL.createObjectURL(MediaSource) implement auto-revoke?

Categories

(Core :: DOM: Core & HTML, enhancement, P3)

58 Branch
enhancement

Tracking

()

People

(Reporter: baku, Unassigned)

References

Details

Rather than copying another implementation's bugs, I think the best thing for
the future of the web would be to support srcObject and lobby for deprecation
of createObjectURL(MediaSource).

https://bugzilla.mozilla.org/show_bug.cgi?id=886194
https://bugs.chromium.org/p/chromium/issues/detail?id=506273
https://bugs.chromium.org/p/chromium/issues/detail?id=254744

Copying the leak may hinder progress towards srcObject, because it may lead to
https://github.com/w3c/media-source/issues/156 being resolved without any
change.

The fact the implementations differed was a factor in the decision to
deprecate createObjectURL(MediaStream).

https://github.com/w3c/mediacapture-main/issues/404#issuecomment-250484426

The reasons for not wanting a leaky createObjectURL(MediaSource) are the
same reasons as for not wanting a leaky createObjectURL(MediaStream).

https://github.com/w3c/mediacapture-main/issues/404#issuecomment-255182322
https://github.com/w3c/mediacapture-main/issues/404#issuecomment-255227837
Priority: -- → P3
Component: DOM → DOM: Core & HTML
Severity: normal → S3
See Also: → 1116382
See Also: → 1808998
Duplicate of this bug: 1808998
See Also: 1808998
You need to log in before you can comment on or make changes to this bug.