- From: Sean Hogan <shogun70@westnet.com.au>
- Date: Thu, 28 May 2009 08:34:34 +1000
- To: Anne van Kesteren <annevk@opera.com>
- CC: Simon Pieters <simonp@opera.com>, public-html@w3.org, Ian Hickson <ian@hixie.ch>, "Hallvord R. M. Steen" <hallvord@opera.com>, Laurens Holst <lholst@students.cs.uu.nl>
Anne van Kesteren wrote: > On Wed, 27 May 2009 14:18:59 +0200, Sean Hogan <shogun70@westnet.com.au> wrote: > >> If I didn't know HTML5 Forms and was looking for a bug in code someone >> else wrote and saw button.formAction I would assume it was meant to be >> button.form.action. If I saw button.submitAction then I would google it. >> > > formAction seems far more intiutive though. And if you debug to see if it returns something unexpected you would learn its function. > > > I hope the spec writers aren't presuming to tell the rest of the world what is intuitive. As for debugging, a real-world debugging scenario could be: There's a problem in form-submission! Look at the relevant code... Why is button.formAction used? I'll just change that to button.form.action and see what happens... That seems to fix the reported problem, commit the change. ... Later ... The fix for form-submission has broken something else! Hmmm, what did I change? Can't remember... look at the code... looks alright... Hmmm, what is supposed to happen? Oh, there's a formaction attribute on that submit-button... Ahhh, the button.formAction property must mirror that attribute. I'll just revert the last change and see what happens... That seems to fix the latest problem, I'll just commit the change and go back to the first issue tomorrow.
Received on Wednesday, 27 May 2009 22:35:25 UTC