[SOLVED] field > microdata > span > is not all valid html

hi there,

I think it is a problem that Flexicontent encloses microdata-enabled fields with a span tag.
Since spans are inline elements, it is illegal to put any block level element inside, only inline elements may be contained within inline elements.

Wouldn't it be better to render a div tag instead? That could still be styled inline if nessecary and be valid at the same time.
And for now, how could i quick-fix this, meaning: In which file is the span tag rendered?

Hope, I'm nopt totally off here, so correct me if i'm wrong
Thanks a lot, and keep up your incredibly great work!
kath

Hello

you spean of passing HTML validation tests, right ?

we eliminated a big number of invalid HTML in both backend and frontend,
it is a continues work

- about this particular case, eliminating BLOCK elements inside INLINE elements is not always easy
because when you eliminate one you find 1 more at a higher level
e.g. we recently changed value containers in default built-in template from SPAN to DIV

so if you have an issue with a template it must be an older copy ?

what i meant was this:
BE > fields > Edit field > FIELD TYPE specific configuration > SEO > Microdata support
When a value is set here, the field might be rendered like so:
<span itemtype=" schema.org/Person " itemscope="">
<div class="my_custom_class">some content</div>
<p>my first name</p>
...
</span>
Here, both <p> and <div> would be illegal.

Hello

i only found 1 case the fieldgroup field is using SPAN to the containt of fields when MICRODATA itemtype is enabled

but most fields have been updated
- give specific details

so for fields, which FLEXIcontent field type is it ?

if you speak of FLEXIcontent Itme type, then which FLEXIcontent template is the type using (please test with built-in ones)

Ok, it happens for me with a field of field type "Fieldgroup (A multi-value field that groups other fields)". When I configure it in "FIELD TYPE specific configuration" > "SEO" > "Microdata support" > "Microdata type" with -say- "Person", source code looks like:

Hello

yes already made the hange for fieldgroup field (for v3.0.14)
- did after your 1st post in this thread

any other case ?