Textpattern Support Forum

Strange enough in this discussion: If you specify a label tag it is not even applied/output although the attribute’s name suggests so: The result is as if you write Search manually in front of a handcoded search form. (So this’d be obviously a valid fourth option ;)

I can’t tell when txp:search_input got its own form attribute, but as we have forms of type category and section now, shouldn’t there be one of type search for the sake of consistency?

I set up a second example in Textbook for showing the minimum of code required to build a customized search form. But neither is my coding waterproof nor is my English. Would someone be so kind and have a look if anything needs some sandpaper?
Thanks!

Last edited by uli (2009-11-13 22:12:30)

Els wrote:

there is no labeltag attribute

Of course you’re right.

I think calling it “label” made me think the thing that’s named label here would be enclosed by labeltags, because otherwise I wouldn’t need an attribute, I could just write it in front of the form, semantically perfect or not. Small “but”, I know: It would be outside of the form then.

Eric, the disutility of hard-coded markup in core tags is undisputed. This thread is currently revolving around suggestions on how to solve this in a backward-compatible, coherent manner.