On Thu, Dec 13, 2012 at 9:35 AM, Ralf Eggert <[email protected]> wrote:
> Marco Pivetta schrieb am 13.12.2012 16:21:
>> Why would fieldsets in the form component represent HTML fieldsets? HTML
>> fieldsets have no meaning at all IMO... They could be replaced by <div/> if
>> it wasn't a question of semantics.
>
> Well, the <fieldset>-Tag is connected to a <form>-Tag. Ask any
> webdeveloper what a fieldset is and most of them will answer something
> like this:
>
> http://www.w3.org/wiki/HTML/Elements/fieldset
>
> So, Zend\Form\Fieldset will be set in connection to the <fieldset>-Tag
> if you like it or not. And with this in mind it is quite confusing, that
> Zend\Form\Fieldset behave in a different way than normal <fieldset>-Tags
> do.
>
> We already have the Collections in Zend\Form. So I would expect the
> collections to work like a collection with logically grouping elements.
> And let the good old fieldsets just group elements visually as long as
> they are not used as collections.
>
> http://zf2.readthedocs.org/en/latest/modules/zend.form.collections.html

The default behavior was requested as part of the RFC process. You can
disable it on a given form by setting the wrapElements flag to a
boolean false.

Whether or not you want it personally, the bulk of those who discussed
the forms RFC wanted individual fieldsets to be namespaced in order to
prevent naming collisions.


--
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]


Reply via email to