-- Andreas Möller <[email protected]> wrote (on Thursday, 15 November 2012, 03:41 PM +0100): > > I have forgotten to do so, but have amended the view script. In the > > form, though, still the unfiltered value is rendered. > > Thanks for providing feedback at the gist at > > * https://gist.github.com/2ac6f7be6aa0a5575845 > > The problem I see with this, though, is that - users will now be > confused because the validation error messages doesn't match the state > of the form. > > Here, <html> is entered in the form, but the validation error message > says that a value is required and it can't be empty.
I understand what you're getting at -- as I mentioned in my comment on the gist, that's how I originally coded it. However, the feedback I received then (after the initial release in beta4) was that this situation was more confusing to end users. I can definitely see both sides; I'm just not sure how we can accommodate both. You can override this behavior by providing your own view helpers at this stage -- so if it's important to you, you can definitely make this happen inside your application. As for the framework, we *may* be able to provide a flag in the AbstractHelper in the form component that would allow toggling this, though it would likely require changes to each of the helpers to honor that flag. Anybody else want to throw in some ideas or feedback on this issue? -- Matthew Weier O'Phinney Project Lead | [email protected] Zend Framework | http://framework.zend.com/ PGP key: http://framework.zend.com/zf-matthew-pgp-key.asc -- List: [email protected] Info: http://framework.zend.com/archives Unsubscribe: [email protected]
