#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):
@Michele
We can't "predict" the mangled output of "name" as a fixed ID for every
case. If I use a widget inside a form, it will have one ID, if I use it
by itself, it will have another, it I use it inside a fieldset inside a
form, it will have yet another ID.
You have three cases depending on where you ".display()"/".render()" your
widget and you can't use the same $('field_id') to access all of them.
Besides that, one has to render the page -- if it is too complex to use
the shell... -- to find out what the ID will be.
These reasons make it very interesting to be able to specify an "id"
attribute.
I'm also from the already stated opinion that we aren't babysitters and if
the guy / girl wants to shoot him/herlself in the foot, let it be. Not
repeating ids in an HTML page is something that is inherent to how HTML
works, not how TG works...
--
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
-~----------~----~----~----~------~----~------~--~---
