An example would be the view helper:
[...] formButton($name, $value, $attribs): Creates an <input type="button" /> element. formCheckbox($name, $value, $attribs, $options): Creates an <input type="checkbox" /> element. formFile($name, $value, $attribs): Creates an <input type="file" /> element. [...] In HTML the <input> tag has no end tag. Darby Felton wrote: > > What I glean from this is a fine suggestion: being flexible on the > markup (or, view) used by parts of the Zend Framework that perform such > output. > > Perhaps you can enumerate particular places with which you're having > trouble, so that we can document them (e.g., in JIRA)? > > Thanks! > > Best regards, > Darby > > debussy007 wrote: >> Hello, >> >> I have noticed that any function that generates markup, >> will generate XHTML markup. >> >> So for any of us that use a HTML 4.01 Doctype, >> this will lead to invalid Html pages. >> >> Here are some reasons for one to use HTML 4.01 : >> >> http://webkit.org/blog/?p=68 >> http://hixie.ch/advocacy/xhtml >> http://www.webdevout.net/articles/beware-of-xhtml#conclusion >> >> Also a lot of good css or javascript coders recommend 4.01 Doctype. >> E.g. just ask in the css irc-channel. >> >> Not saying that the html 4.01 doctype is the Doctype to use, >> but would it be possible to take this point in cosideration in the ZF for >> the one of us who choosed an HTML Doctype rather than XHTML ? >> >> By for example adding some static method that would let one choose the >> markup Xhtml / Html ? >> >> Thank you for any response !! > > -- View this message in context: http://www.nabble.com/Suggestion-for-ZF---Markup-generation-tp14234398s16154p14256723.html Sent from the Zend Framework mailing list archive at Nabble.com.
