Fuffy ,'Storyteller'
Do you have problems, concerns or recommendations about the technical side of the Phoenix? Air them here. Compliments also welcome.
So far, I haven't gotten anything to bleed over. The interesting thing is it seems to treat HTML with QuickEdit counterparts (italics, bold, etc) basically as QuickEdit, so it closes the tag at the end of the paragraph, not the post.
Okay, actually, it does close the tag at the end of the post, but the board doesn't continue the tag past the paragraph, which I thought it did.
Doesn't
it?
Oh, I guess it never did. Huh.
So you're saying it's your dancing that brings all the boys to the yard, DX?
:: pats brain down::
::nope still not tired of that joke::
So you're saying it's your dancing that brings all the boys to the yard, DX?
Sadly there are neither boys nor girls in my yard. My dancing ability is on a par with my baking ability.
Man. The code seems to be pretty resilient. I hit it with like seven nested tags, some multiples, and it caught them all.
I'm not having any luck breaking it. It might be a good idea to have another codehead give it a read-through. It is classes.Post->closetags()
I'm going to attack the mismatched-quotes-in-an-href problem, unless there are objections. It hoses things up right proper.
I'm not having any luck breaking it.
The main thing is that it seems to be working on making the ratio of open tags to closed tags 1:1, regardless of their position. So if you close a tag before opening it, the tag will bleed.
The main thing is that it seems to be working on making the ratio of open tags to closed tags 1:1, regardless of their position. So if you close a tag before opening it, the tag will bleed.
Yup. Will fix.
I'm going to attack the mismatched-quotes-in-an-href problem, unless there are objections. It hoses things up right proper.
Agree. That's probably the worst board breaker of all of them.
Ok, closing order for tags is installed, for all the testing types to jump up and down on.
Agree. That's probably the worst board breaker of all of them.
Cool. We need a thing that assures that any attribution in a tag is well formed. Next up.
I am very happy that new shiny things are getting coded for the board.
I support the use of money we already have to update us, especially if it will fix that big problem thing we had.
While people are feeling productive do we need to pull out the feature wishlist?