Home/ Questions/Q 8960477
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-15T15:40:02+00:00

I am working on a Native mobile application CMS system using client-side technology(javascript via

  • 0

I am working on a Native mobile application CMS system using client-side technology(javascript via JQuery for the most part) and have implmented a templating system similar to that of ASP.NET.

So suppose I have a navigation control which has a starttemplate, endtemplate and itemtemplate as follows:

<div data-type="navigation" id="navigationControlDemo">
    <div data-type="starttemplate">
      <ul id="Menu">
    </div>
    <div data-type="itemtemplate">
      <li><a href="[[Link]]">[[Text]]</a></li>
    </div>  
    <div data-type="endtemplate" >
        </ul>
    </div>
 </div>

My problem is the browser as it laods seems to decide to want to fix the html so that the tags are closed “properly” as follows:

 <div data-type="navigation" id="navigationControlDemo">
    <div data-type="starttemplate">
      <ul id="Menu">
      </ul>
    </div>
    <div data-type="itemtemplate">
      <li><a href="[[Link]]">[[Text]]</a></li>
    </div>  
    <div data-type="endtemplate" >

    </div>
    </div>

I’ve tried some workaround and quick hacks to no avail..
I have tried replacing the “<” “>” with certain characters and then replacing them after load but the problem still occurs.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Basically, you’re asking for a way to force a browser to display malformed, messy tag-soup. Thank God most browsers don’t just blindly render that kind of code, because the results would be unbearable and make your page unintelligible all together.
    That said, if you view the raw page source, you’ll probably see the un-corrected, raw markup. But because the browser can’t really render it, the engine steps up to the plate and does its best.

    But please, don’t waste your time finding a way around this, it’s just a feature to help you, not to annoy you. Also: HTML5 has a lot more rules about what is allowed and what is not, and how the browser is expected to deal with invalid markup (in your code: <div><ul></div> is deemed invalid, for example). If you feel up to it, you can look at the W3C specifications for more info on the subject.

    • 0