- From: Anne van Kesteren <annevk@annevk.nl>
- Date: Tue, 8 May 2012 07:36:54 +0200
On Fri, 04 May 2012 01:59:15 +0200, Evan Jones <evanj at csail.mit.edu> wrote: > I would be interested in trying to help with this, but again I would > certainly need some guidance from people who know more about the > vagaries of how the various browsers encode their form parameters / > uploaded file names, and why things got that way. It probably would not > be helpful for me to try to draft an update to the spec without getting > the right implementers on board. The best way to start with defining a legacy feature is figuring out what the various implementations do. The next step is evaluating that against what is most compatible and desirable and try to come up with a proposal. Along with talking to / filing bugs on various implementations to see if they can be converged. And then after a few iterations (and sometimes quite a bit of time; e.g. the HTML parser took about six years) you have standardized some legacy behavior and made it fully interoperable. Additional benefit is that it's now easier to extend, easier for new implementations, and easier for existing implementations to rewrite their code if necessary. PS: Apologies for potentially breaking threading by sending this email. I'm switching email addresses. -- Anne van Kesteren http://annevankesteren.nl/
Received on Monday, 7 May 2012 22:36:54 UTC