[Bug 9602] Autofocus attribute.

http://www.w3.org/Bugs/Public/show_bug.cgi?id=9602





--- Comment #16 from Skyphire <sasha@scarletred.nl>  2010-08-05 15:38:00 ---
My main point was to remind i.e. summarize the reasons for separation of
declarative and procedural structures in HTML, meaning that HTML should not be
able to control a document. I remain convinced that JavaScript -being able to
perform such procedures- was designed for this task. While I understand the
nuances of this discussion, it is also easy to get lost in a mindset of "nifty
features". 

Besides a security "risk", it is also unwanted from a usability standpoint. I
find it highly aggravating when a document sets focus on something I don't
want; If JavaScript performs such task, then it is easily mitigated, by simply
disabling JavaScript, or use UserScripts like in Opera or Mozilla to modify the
scripts behavior to what I want it to do.

So do the benefits really outweigh the challenges it creates from a security as
well as a usability standpoint? Hard to say. My first intuition says no. It
doesn't. It takes a one-liner of JavaScript to perform the same procedure of
setting focus on an element in a document. 

I think it's a high price to pay when one supports such features over a solid
RESTful architecture, obeying SGML design principles. Certainly if the aim of
such feature could be achieved otherwise, namely: a scripting language.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Thursday, 5 August 2010 15:38:02 UTC