Sometimes the message center URL sticks to the address bar (IE6), and it doesn't change when I click links, almost like I'm stuck in a frame. I can get out of it by forcing the browser Home. I think this happened once in Safari too, though. Maybe.
Womack ,'The Message'
Buffistas Building a Better Board
Do you have problems, concerns or recommendations about the technical side of the Phoenix? Air them here. Compliments also welcome.
Otherwise it's kinda embarassing.
You really think so?
Besides, unless we figure out a way to make it clear to the poster that only the poster can see the warning message, the poster will think everyone can see it and be just as embarassed as if we made the warning message public to begin with.
There should be an animated GIF of ita wagging her finger at the poster.
unless we figure out a way to make it clear to the poster that only the poster can see the warning message
Why can't we just tell them?
Honestly, I think it useless information to me that Jon forgot to close his italics tag, but valuable information for Jon.
At best I'm now more aware that Jon can't HTML to save his life, or is having a fat fingered thinko sort of day.
Something like ...
Private message: You fat-fingered the URL. Put the pipe DOWN.
Okay, maybe a little less blunt.
BTW: The only error that will be reported will be for unbalanced value delimiters that Tidy can't figure out. "Private message: HTML error found. Check your quote marks."
Can't you return a generic error message for anything Tidy needs to fix?
Is there any way that the poster could be notified before the post ...posts? Like, if the HTML is too screwy for Tidy, instead of posting, take the poster to the Edit page with a note at the top saying "Your HTML can't be Tidied, you'll have to fix it yourself."
That way, no board-breakage, and no embarrassment.
Gus -- correct me if I'm wrong -- if Tidy can find it, Tidy can fix it. If Tidy can't find it, it's mismatched quotes or mistyped tags. Mismatched quotes we also fix, and mistyped tags will probably be yanked out.
Basically, I think that if we can find it, we can fix it.
Tidy can find unbalanced quotes but won't fix them beyond containing the problem. Right now, I'm not post-Tidy processing to fix them. Should I? We already own most of the code to do that. Frankly, I don't know why Tidy throws in the towel on that one.
Mistyped tags are found by Tidy. It will report t bogus='100' out as an unknown tag. No one can automatically fix that problem. There is a message I could recast about the condition, and I'll do so.
Mistyped tags are found by Tidy.
No need, unless we're revisiting the decision to strip all but a subset of tags.