785505 - anchor containing figure tag incorrectly rendered

Status: RESOLVED WONTFIX

(Camino Graveyard :: General, defect)

Description

[skeetergraphics]

Attachment: Used Firebug Lite bookmarklet to reveal rendered markup in Camino.

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_4) AppleWebKit/537.1 (KHTML, like Gecko) Chrome/21.0.1180.82 Safari/537.1

Steps to reproduce:

Wrapped a figure tag with an anchor and viewed with Camino Version 2.1.2 (1.9.2.28 20120308211433) on Mac 10.7.4. See code in question (from—http://vq.vassar.edu/):

<article>
  <div class="article article-homepage-feature"> 
    <a href="/issues/2012/02/features/campaign-update.html">
    <h1>Campaign Update</h1>
    <figure>
      <div class="figure"> 
        <img src="/issues/2012/02/images/home-campaign-update.jpg" width="325"/>
        <figcaption>
          <div class="figcaption">Take a look at how far alumnae/i and friends have come in satisfying the goals of the Vassar 150: World Changing campaign ... and what’s still left to do.</div>
        </figcaption>
      </div>
    </figure>
    </a> 
    </div>
</article>


Actual results:

On render, figure converted to self-closed tag and anchor applied to individual elements instead of wrapping all in one anchor (see attached). 


Expected results:

Figure should have remained as coded.

If I put <figure> inside <div class="figure"> it works fine.
It has something to do with being inside the anchor—removing anchor without changing div order leaves rendered markup unchanged.

Thanks for having a look at this!

Comment 1

[Robert Longson [:longsonr]]

Your camino uses gecko 1.9.2 which does not have an html5 parser. The html5 parser was first introduced in gecko 2.0 You either need to wait for a camino version to come out based on a newer gecko version or use Firefox.

Comment 2

[philippe (part-time)]

(In reply to Robert Longson from comment #1)
> Your camino uses gecko 1.9.2 which does not have an html5 parser.

Exactly this. The HTML parser in the Gecko version that ships with Camino doesn't know about the 'figure' element.

Won't fix (because the really is no 'can't fix' resolution in Bugzilla).

Comment 3

[skeetergraphics]

Thanks for your quick attention. Sorry I didn't realize gecko 1.9.2 didn't have an html5 parser at all. Interesting that wrapping <figure> inside a <div> produces expected redering. I've wondered if it's best to wrap html5 elements in div or place div inside html5 element. This result indicates wrapping html5 element in <div> may be preferable because it produces proper results in cases where html5 parser is not available. Thanks!