2012-02-22 20:13, Cameron Jones wrote:
It [the <output> element]
> does provide a greater degree of integration with the browser though.
Is this a requirement, or just assumed features of implementation? Which of the assumed benefits could not be achieved by adding a new value for the type attribute (<input type=output>), or a new parameter (<input output>), or otherwise retaining the use of <input> (which would degrade well)?
This results in a less scripting being required and allows for inline scripting to be more concise which aids readability and keeps things together.
This would need to be illustrated by real examples, and you would still have the question why this could not be achieved using libraries, without making pages break on old browsers.
It's also possible for it to be styled using a different interface instead of elements targeted at capturing information. The 'disabled' state doesn't provide this for <input>
If you wish to show results of calculation visibly _and_ pass them along with the form data, you can use _both_ a normal element like <div>, <p>, or <span> _and_ an <input type=hidden>. The resulting duplication is irrelevant; you have the result in a variable, or should have, and just put it into two places.
Yucca
