P-C, all this has been remedied in the lab.
Am-Chaun has done some testing there, but only by her lonely.
Bring your t br's on!
Andrew ,'Damage'
Do you have problems, concerns or recommendations about the technical side of the Phoenix? Air them here. Compliments also welcome.
P-C, all this has been remedied in the lab.
Am-Chaun has done some testing there, but only by her lonely.
Bring your t br's on!
You're not having a good linking day today, are you, Gus.
You're not having a good linking day today, are you, Gus.
No.
Fixed, now.
P-C, What were you testing here: [link] (#168)?
Remember my original problem of not closing the original tag with a right caret?
<BROops I'm dumb
I tried it with various other tags:
<bThis should be here and bold</b>
And I thought maybe the code would fill in that right caret and make the tag functional, but instead it just obliterated everything from the left caret onward.
That's asking for a lot of guessing, P-C.
Computers aren't good at guessing??? Who'da thunk it?
That's asking for a lot of guessing, P-C.
I know, but Gus is a badass.
Oh. I don't think we want to chase after malformed tags. There are just too many ways to malform them.
eta: despite the badness of my ass.
wheaties:
There hasn't been much independent testing going on in the lab. If we're comfortable that the all function is there, though, I can move on to making the changes to do the automagic stuff on display, rather than before save. This will allow preservation of the text in P-C's testcase.
My present guess is that comparing the timing of a threadsuck in the present mode to the timing of the same threadsuck in the on-display mode will get us a number reflecting the performance impact. Anyone have a better test in mind?