Inline labels are not inline

Ok, so it looks like the label itself is being wrapped in a span, groovy. But the element immediately after it is wrapped in a div (in this case, because I set the Fences spec to div). <span><div> displays as if the label is block...

Here's a screenshot to explain the problem more clearly.

Ok — here's what's happening.

Core without Fences

Drupal creates this markup for a field that has an inline label.

<div class="field field-name-[fieldname] field-type-text field-label-inline clearfix">
     <div class="field-label">Label:</div>
     <div class="field-items"><div class="field-item even">This too, it's just a Core field</div></div>
</div>

Note the class on the outer div, field-label-inline.

Then there is CSS that floats the label (wrapped in a div) to the left so that the field content (also wrapped in a div) will appear to be inline. Both elements are still actually block, they just appear inline.

line 6 of field.css in core:

.field-label-inline .field-label, 
.field-label-inline .field-items {
    float: left;
}

When we use Fences, the outer wrapper is removed (yay!) and therefore there's nothing to mark whether the label is inline or not. I think we need a class on the label's <span> so we can float it left.

Yes, we three agree. We need a class on the element that wraps the Label. I think that should do it Alan, yes? There might be use-cases for more markup, but to simply get an inline label to be inline, I think moving the class from the (no-longer-existing)-outer-div to the element (div or span) that directly wraps the label will do it. We just need something to toggle between 'inline' and nothing so that the needed CSS can be written.

<div class="field-label inline">Label:</div>

<span class="field-label inline">Label:</div>

Not having any more inline labels doesn't work.

I haven't tested multiple value fields either. But can we open a separate issue for that? Let's at least fix this one thing. Then if there are more problems, we can fix those as well.

If my memory is right, multi-vaule fields get a separate set of tpls to handle the fact they are different.

Also — hi Alan!