Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 216313
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 11, 20262026-05-11T18:33:10+00:00 2026-05-11T18:33:10+00:00

This should be easy (at least no one else seems to be having a

  • 0

This should be easy (at least no one else seems to be having a similar problem), but I can’t see where it is breaking.

I’m storing Markdown’ed text in a database that is entered on a page in my app. The text is entered using WMD and the live preview looks correct.

On another page, I’m retrieving the markdown text and using Showdown.js to convert it back to HTML client-side for display.

Let’s say I have this text:

The quick **brown** fox jumped over the *lazy* dogs.

1. one
1. two 
4. three
17. four

I’m using this snippet of Javascript in my jQuery document ready event to convert it:

var sd = new Attacklab.showdown.converter();
$(".ClassOfThingsIWantConverted").each(function() {
   this.innerHTML = sd.makeHtml($(this).html());
}

I suspect this is where my problem is, but it almost works.

In FireFox, I get what I expected:

The quick brown fox jumped over the lazy dogs.

  1. one
  2. two
  3. three
  4. four

But in IE (7 and 6), I get this:

The quick brown fox jumped over the lazy dogs. 1. one 1. two 4. three 17. four

So apparently, IE is stripping the breaks in my markdown code and just converting them to spaces. When I do a view source of the original code (prior to the script running), the breaks are there inside the container DIV.

What am I doing wrong?

UPDATE

It is caused by the IE innerHTML/innerText “quirk” and I should have mentioned before that this one on an ASP.Net page using data bound controls – there are obviously a lot of different workarounds otherwise.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-11T18:33:10+00:00Added an answer on May 11, 2026 at 6:33 pm

    It was the Internet Explorer innerHTML/innerText “quirk” that was causing the problem. For all elements that weren’t marked as <pre>, IE strips whitespace for them before handing them off to Javascript.

    I couldn’t just leave the element with the markdown text in <pre> tags because then the HTML generated by Showdown wouldn’t appear right. The solution was to wrap it temporarily in a <pre> and then change it.

    The ASP.Net code looks something like this now:

    <div class="ClassOfThingsIWantConverted">
        <pre><%# Eval("markdowntext") %></pre>
    </div>
    

    And the Javascript/jQuery looks like this:

    var sd = new Attacklab.showdown.converter();
    $(".ClassOfThingsIWantConverted").each(function() {
       this.html(sd.makeHtml($("pre",this).text()));
    }
    

    works fine on both browser now…

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

It seems this should be easy but I'm having a lot of difficulty using
This seems like it should be easy, but I can't get the right syntax.
This should be easy to find out but I can't seem to find it
This should be an easy problem but... I need to format a currency for
This should be an easy question - but I'm having a hard time figuring
Seems like this should be easy or at least documented somewhere, I just cant
This should be an easy one to track down...but it isn't proving that way
OK, this should be easy, but I do not find the solution, at least
Feel silly asking this question, since this should be easy, but I can't figure
OK, I'm feeling like this should be easy but am obviously missing something fundamental

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.