- From: <bugzilla@jessica.w3.org>
- Date: Wed, 17 Apr 2013 21:48:26 +0000
- To: public-media-capture@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=19594 --- Comment #8 from Arun <arun@mozilla.com> --- (In reply to comment #7) > I'm worried about shipping applications that would break it, but I don't > know of any concrete examples. > > I'm not enthusiastic enough about this change to volunteer Firefox to be the > first browser to try to change. If another browser vendor wants to try the > compatibility experiment, that's fine. Well, the spec shouldn't coerce implementations to do things they are reluctant to do :( One of the reasons we put in autoRevoke=true by default was to minimize leaked strings (Blob URLs that persisted past their use), and to minimize forcing developers to couple a create* call with a revoke* call. Do you think that's needlessly cautious? -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
Received on Wednesday, 17 April 2013 21:48:27 UTC