Firebug gives you the "interpreted" DOM, not the actual output, unless you are looking the Response tab of the AJAX request. Anything in the HTML tab is kind of sanitized.
Sean chris wrote: > Oops, I wasn't aware of that :). > > It is through firebug since the resulting data is from an ajax > request. I am assuming that the issue? > > On Nov 2, 6:26 am, Sean Cribbs <[EMAIL PROTECTED]> wrote: > >> FWIW, <h3> is not permitted inside <p>. Are you looking at Firebug >> output or the actual source? >> >> Nathan Weizenbaum wrote: >> >>> That sounds like a bug, but I can't reproduce it. What version of Haml >>> are you using? >>> >>> chris wrote: >>> >>>> Here is the code: >>>> ============= >>>> %p.search-results >>>> - if @people.nil? >>>> %h3.center-text No matching people were found. >>>> >>>> - else >>>> ... >>>> >>>> With the above code the <p class="search-results"> tag is always >>>> closed too early and all the following code gets rendered after the </ >>>> p>. >>>> >>>> If I remove the %p it works as expected, and if I replace the p with >>>> div it also works. >>>> >>>> Am I missing something or is this a bug? >>>> >> > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Haml" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/haml?hl=en -~----------~----~----~----~------~----~------~--~---
