Forum Replies Created

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter justfloatingonby

    (@justfloatingonby)

    Let’s forget about <br> for a moment. Let’s talk about a new tag I just invented called <foo>.

    If I created:

    <foo></foo>

    and WordPress turned that into

    </foo>

    what would we say?

    We would say – WordPress has a bug. It is always illegal in all and every case without exception in XHTML or XML or HTML to have a close tag without an open tag. </foo> is a close tag. WordPress mangled <foo></foo> into </foo> and produced illegal, invalid XHTML/XML/HTML.

    In this case it so happens that WordPress exhibits this behavior with the <br></br> tag but that isn’t the relevant point. It doesn’t matter what element triggers the behavior. All that matters is that WordPress is outputting illegal HTML/XML/XHTML.

    So how do I file a bug that WordPress is outputting illegal markup?

    Thanks,

    Yaron

    Thread Starter justfloatingonby

    (@justfloatingonby)

    Right and my content is XHTML which is XML where <x/> == <x></x>. So <br/> == <br></br>. Unless XHTML put on some additional restriction?

    But in any case I’m guessing that we can all agree that wordpress turning <br></br> into </br> when the breaks are inside of a

     tag isn't the right behavior so hence I want to file a bug but I don't know how.

    BTW I did upgrade to 2.2 but I never use the editor. I actually upload my posts directly to MySQL using JDBC. So is the problem in 2.2 the editor or in whatever code is used to process posts before they are displayed?

    Which leads to one of my original questions - is there anyway to turn off all XHTML pre-processing in WordPress? I want what's in the database to just be displayed. Is this possible in WordPress?

    Thanks!

    Thread Starter justfloatingonby

    (@justfloatingonby)

    I actually ran a test. If I enter:

    foo<br></br>bar

    then things work fine.

    But if I enter:

    foo<br></br>bar

    Then my <br></br> gets turned into </br>. So this is a 100% repro bug in WordPress.

    How do I report it?

    If I enter <br/> then things work fine. So there is a bug in WordPress’s processing code.

    Thanks!

    Yaron

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