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?
Yo, canna save the edit on the problem link in this post.
I'm not seeing the right hand threads anywhere except on the home page and Message Center. (Windows XP, IE 6)
Yo, canna save the edit on the problem link in this post.
It's a single-quote/double-quote mismatch in the HREF. Also, I'm not sure if that #a342 garbage at the end of the html is relevant.
It's a single-quote/double-quote mismatch in the HREF. Also, I'm not sure if that #a342 garbage at the end of the html is relevant.
The pound is relevant. Usually, I can fix a quote mismatch pretty easily, but this time, it wasn't letting me.
So the URL was [link] and there was a mismatched quote in the href?
Yep. Opened with a single quote, closed with a double quote.
I just tried it over in Gus's lab, and the unmatched quotes were fixed automatically. Pretty cool.
Guys,
I have a really bad typo problem. I tend not to hit the shift key long enough, so I start hrefs with a ' and end them with a ". I do try to check for this, honest.
But whenever I make this mistake, it screws the board up something fierce. Is there any way to check for a ' immediately after href=?
