automatic word wrap bug

  • globalcitizen

    (@dunkelangst)


    16 years, 5 months ago

    Dear WordPress developers!!

    WordPress 2.8.6 has got a Problem with the automatic word wrap. Type the following comment in a WordPress Blog: Thank you for your comment!<blockquote>this is a small quote</blockquote> Next Text Then you have to save the comment. If you validate the your publish, you will see, that the sentence “Thank you for your comment!” will be put into the following absurd tags: <p>Thank you for your comment!<br />. The same Problem exists when you type test 2 <p> break </p> next text. After the word test 2 you will miss the </p>.

    WordPress has got this mistake with every single elements like these one: <p>, <ul>, <ol>, <li>, <h1> bis <h6>, <div>, <blockquote> etc.

    When you make manuell a word wrap in front of these elements, you won’t finde any problem, so WordPress must put an automatic word wrap in front of theses elements and it doesen’t do it. Please fix this nerved bug!!

    regards, Dunkelangst from http://www.dunkelangst.org/

Viewing 10 replies - 1 through 10 (of 10 total)
  • Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    🏳️‍🌈 Advisor and Activist

    16 years, 5 months ago

    You are aware that’s invalid HTML, right?

    It should be like this:

    Thank you for your comment!

<blockquote>this is a small quote</blockquote>

Next Text

    Which gives you this:

    <p>Thank you for your comment!</p>

<blockquote>this is a small quote</blockquote>

<p>Next Text</p>
    Thread Starter globalcitizen

    (@dunkelangst)

    16 years, 5 months ago

    Yes, you have to do the word wrap manuell – than you’ve got the right code. WordPress have to do it autimatically and it doesn’t do it.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    🏳️‍🌈 Advisor and Activist

    16 years, 5 months ago

    WordPress is doing exactly what you’ve asked it to, so the ‘fault’ lies in … well, you. You input the information in an invalid format. WordPress, rightly, assumes you know what you’re doing.

    That isn’t a word-wrap bug, that’s a user input error.

    Thread Starter globalcitizen

    (@dunkelangst)

    16 years, 5 months ago

    What?! You can not assume that a user of a blog will put at every tag a manual word wrap! That doesn’t do any other web based software but not WordPress. It is a WordPress bug.

    WordPress is doing exactly what you’ve asked it to, so the ‘fault’ lies in … well, you.

    I don’t know who you are but if I were you, I wouldn’t call me a liar. 😉 That is just an insult.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    🏳️‍🌈 Advisor and Activist

    16 years, 5 months ago

    I didn’t say liar. Nor did I imply it. I said it was user-error, not a code bug.

    What?! You can not assume that a user of a blog will put at every tag a manual word wrap! That doesn’t do any other web based software but not WordPress. It is a WordPress bug.

    You’re not using the term ‘word wrap’ in a way I understand. Word wrap means, when I hit the end of the line, my text magically wraps around to the next line, and I don’t have to hit enter like we did in the days of typewriters.

    What you’re saying sounds like this: “When someone enters in HTML comments in an invalid way, the HTML output from WordPress is also invalid.”

    Which … yeah. You’re right. That’s how it works. Not a bug, user error.

    Thread Starter globalcitizen

    (@dunkelangst)

    16 years, 5 months ago

    What ever…

    I think you are right. word wrap was the wrong vocabulary. Sorry. I am from Germany and my English is not so good. Sorry.

    What ever you think about this posting I’ve put a bug report. I don’t think it is a User error. So you can comment it there. I’ve done my task now – the rest is not my problem.

    bye.

    Clayton James

    (@claytonjames)

    16 years, 5 months ago

    Yeah, Ipstenu… what he said. So there. 😛

    Interesting. I wonder if what he is experiencing could be some weird by-product or glitch from the modded css? It appears to be an adaptation of the “Falling Dreams” theme, which I think may have been originally intended for optimized viewing on mobile devices. Or at least very small view ports. I guess I would be curious to know if the symptoms persist with a different theme. Oh, well.

    Thread Starter globalcitizen

    (@dunkelangst)

    16 years, 5 months ago

    It appears to be an adaptation of the “Falling Dreams” theme

    Yes, I adjusted the falling dreams theme to my own individual requirements.

    I guess I would be curious to know if the symptoms persist with a different theme. Oh, well.

    The bug, I’ve put it here into the forum, is independent from any theme. So it is a bug of WordPress.

    Clayton James

    (@claytonjames)

    16 years, 5 months ago

    Well done! We’ll wait to see if anyone has a suggestion.

    Best wishes!

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    🏳️‍🌈 Advisor and Activist

    16 years, 5 months ago

    Oh no, I agree clearly that it is functionality of WordPress causing the issue. I just don’t agree that it’s a ‘bug’ or ‘flaw’ in WordPress to in-line validate bad HTML. The software just isn’t that smart is all, nor should, I feel, we expect it to be so. It’s not reasonable to expect WordPress to spit back an error on invalid HTML, since sometimes we WANT to do that.

Viewing 10 replies - 1 through 10 (of 10 total)

The topic ‘automatic word wrap bug’ is closed to new replies.