Re: [w3c/FileAPI] Readonly attributes without setters? (#126)

If we'd redesign this API from scratch, yeah, we'd possibly name things differently. At this point there really ins't much we can do about that. There is way too much usage out there of the existing names, so renaming isn't an option. We could add an alias or something with a different name, but that would just cause even more confusion, as now there are two names for the same thing. It is unfortunate that "historical" APIs name squat names that arguably could be used better for other concepts, but there isn't much we can do about that at this point.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/FileAPI/issues/126#issuecomment-480940624

Received on Monday, 8 April 2019 18:06:20 UTC