On Jan 27, 2010, at 11:45 AM, mdipierro wrote: > I agree it is a bug that ids may not be unique. Yet fixing this will > break backward compatibility. > Perhaps we can add the same strings to the class attribute without > breaking backward compatibility but we should not remove them from id. > What do people think?
It's better than not doing it. But duplicate IDs is bad. If you serve an xhtml page as xhtml (rather than as html), and it has duplicate IDs, the browser will not display it. Period. I question whether backward compatibility needs to extend to propagating bugs. > > On Jan 27, 1:36 pm, Jeremy Dillworth <jdillwo...@gmail.com> wrote: >> Thanks. But I wasn't too concerned about ambiguity in the CSS. I was >> more concerned about there being duplicate IDs in the DOM. The w3c >> HTML validator flags this kind of thing as a problem. As far as I know >> it doesn't create a problem in any current browser (other than making >> document.getElementById useless), but since these IDs are only used >> for CSS, wouldn't it be safer to move these labels into the class >> attributes and modify the default stylesheets as needed? >> >> Thanks >> >> Jeremy -- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web...@googlegroups.com. To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/web2py?hl=en.
