If "Wrap field in HTML" isn't checked (and the same goes for "label", and "label+field"), shouldn't the default output be clean? Its a hassle to update every field in every view to "not wrap" the field, the label, AND the whole field+label in HTML by adding this setting.

I'm not trying to be critical of the new Views functionality, but new site administrators would instinctually expect that no wrapping tags will be output unless the "wrap" settings are checked. Since there is a "-default-" value for each HTML wrap setting, one would anticipate that this will only be used when the checkbox is activated.

Comments

merlinofchaos’s picture

merlinofchaos commented

Yeah,the checkboxes were added to the UI without actually modifying the behavior based on the checkboxes, and the wording isn't very good. It really should say "Change the default wrapping" or something.

Unfortunately, changing the behavior of the checkboxes has pretty deep ramifications, since it woudl significantly change the output of almost all existing views.

One thing that might help you specifically would be if we added a global setting that defined the default behavior. i.e, by default "Use Views' classes and HTML wrapping on fields" and if you uncheck that, all the views would suddenly have a lot less output. That might still have ramifications for modules that utilize Views and expect markup, though.

dboulet’s picture

dboulet commented

Yeah, the wording of those checkbox labels is very unfortunate. In order to have no wrapping HTML, I need to check a box that is labelled 'Wrap field in HTML', and then choose 'None'—not intuitive at all.

I would rather change the behavior of the checkboxes—I find it much more convenient to just quickly uncheck boxes instead of having to use awkward drop downs—but I do realize that it does have ramifications, as you said merlinofchaos.

If we need to instead change the labels for the checkboxes, my suggestion would be 'Customize wrapper HTML'.

ryan.armstrong’s picture

ryan.armstrong commented

I would agree with dboulet that changing it to "Customize the wrapper HTML" would go a long ways into cluing people in that the 'none' option is to be found there.

merlinofchaos’s picture

merlinofchaos commented
Status: Active » Fixed

Ok, I committed a fix to change the wording. I like the "Customize", it's much nicer than 'Override' and I think it is very clear what is going on when you check that box.

The other half of this issue is here: http://drupal.org/node/1124130 -- I would love any comments before dig in on it.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.