Span breaking XHTML strict

This isn't fixable. If you're putting in block level fields and you care about w3c validation, you'll have to override the theme and change it on an individual basis.I can't wrap it in a div because it might NOT be a block element, and I can't wrap it in a span because it might be a block element and I have to wrap it in something to get a class.

So it can only be fixed via theming.

From a markup perspective you cannot just wrap everything in a div element since div is block level. The CSS properties, display: [block|inline]; are only that, CSS properties and only have a bearing on the display of markup.

Inserting block level elements into inline elements is invalid markup.

After re-reading the comments. Is there ever a time a view is not a block-level entity? This is to distinguish it from being a block in Drupal parlance vs. being block-level in markup parlance. Unless you you have a one-liner view is there a reason not to wrap it in a div element?

Not the view, an individual field within a view.

Gotcha, sorry for the noise.

Fix committed. This might be a little tricky.

I'm still seeing this bug in the current version for embedded video fields even though their not set to inline. Does something need to change in the emvideo module or is there still a bug in views?

This should be up to the module to set its fields up properly.

OK, will check there then. Thanks.

Hi,

What about overriding the default element type not only for being displayed as inline ?

Right now you can set up if you want the element to be displayed with a SPAN, but there is no method for forcing the field to be displayed as a block.

I have experienced the same problem as #10 with a "user: picture" field, which by default displays itself as inline.
Therefore we would have to handler three cases: forcing it as inline, forcing it as block, or leaving its default behaviour.

(Maybe I am missing something because I am not a D6 guru - yet)

Isn't it possible to override the theme function? I thought these HTML things are put into a theme function which can be overriden in template.php?!

Yes, all of Views output can be overridden with theming.

Ok, thank you for your answers.... after reading #1 I see it clearly that it must be done with theme overriding.... but then I still get confused about why it is implemented the option for forcing a field as inline...because this could also have been done with theming, ¿right?