#902: [PATCH] All input widgets should have a "field_id" param to allow
overriding the DOM element's id
---------------------+------------------------------------------------------
Reporter: alberto | Owner: anonymous
Type: defect | Status: new
Priority: normal | Milestone: 1.0b1
Component: Widgets | Version: 0.9a5
Severity: major | Resolution:
Keywords: |
---------------------+------------------------------------------------------
Comment (by godoy):
Even though I like this idea, I'd like to remember Roger's recent cleanup
on widgets and the fact that to be *valid* (X)HTML we have to have id ==
name, otherwise we'd get warnings from validators.
I believe that id == name, so no new attribute is needed and we're
generating valid (X)HTML output. I would love if all output from TG is
valid because I'll know that any problems on my page can be fixed by me
and are not my framework's fault.
Since we're tying id at instantiation time -- as we do with name -- I see
no advantage to allowing it to be different because we'll already have
duplicate names on the page if we have to ".display()" calls. As for
accessing each individual field on a multi-form page, we can always
qualify our forms (that should also have the same id as the name...).
So, I'm -1 for all this but +1 on fixing the generated id to be equal to
the name of the widget.
--
Ticket URL: <http://trac.turbogears.org/turbogears/ticket/902>
TurboGears <http://www.turbogears.org/>
TurboGears front-to-back web development
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TurboGears Tickets" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/turbogears-tickets
-~----------~----~----~----~------~----~------~--~---
