> In a recent thread, Jeremy told me that having id elements is a bit of a > problem because each tiddler can be transcluded more than once into any given > tiddler' which would result into a broken html with a repeated id value. > > This is true. > > But if id are required, shouldn't it be up to the programmer to make sure > there is no problem? Of course, the doc would tell that specifying id is a > tricky things to be done with great precaution. But this is IMHO better that > forbidding id specification altogether. > > As was the exposed, this has to do with WCAG requirements ignoring the > CORRECT HTML (stated as accessible on official docs) <label><input/></label> > are requiring <label for=foo/><input id=foo/> as the only validating way of > accessible code. (with some variations for WAI-ARIA)
Just to be clear, the core doesn't forbid using "id" attributes, it's perfectly possible to use them as long as care is taken. The thing that's particularly hard is to use IDs within a reusable component without the user of that component being aware of the mechanism. So, the core avoids the complexity of these techniques. Best wishes Jeremy. > > -- > Jean-Pierre > -- > You received this message because you are subscribed to the Google Groups > "TiddlyWiki" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/tiddlywiki/d739e00f-ba01-4425-b0d0-9730d6524986n%40googlegroups.com. -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/DDEE59DF-F889-4678-9591-BBC693F816DA%40gmail.com.
