screen that says "post buggered continue/edit?"
The continue option is important, so that we don't revive accusations of being "interface fascists."
Dawn: Any luck? Willow: If you define luck as the absence of success--plenty.
'Touched'
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.
Noumenon - Nov 28, 2002 6:17:39 pm PST #1766 of 10000
No other candidate is asking the hard questions, like "Did geophysicists assassinate Jim Henson?" or "Why is there hydrogen in America's water supply?" --defective yeti
§ ita § - Nov 28, 2002 6:38:14 pm PST #1767 of 10000
Well not canonically, no, but this is transformative fiction.
I think the continue option should be a teeny tiny little button that's never in the same place twice. Why should you continue?
Bad Buffista! No cookie!
Rob - Nov 28, 2002 7:18:43 pm PST #1768 of 10000
There's nothing elegant about an error page, but I don't care for elegant so it's fine for me.
Jon B. - Nov 28, 2002 8:42:11 pm PST #1769 of 10000
A turkey in every toilet -- only in America!
I think the continue option should be a teeny tiny little button that's never in the same place twice.
Ooooh! HTML coding with a random element! I'm up for it!
John H - Nov 28, 2002 8:44:11 pm PST #1770 of 10000
I was thinking about this and I now want it to be another page along the lines of
You made an HTML error. We fixed it. You were short a <b> tag. You can go ahead and post by clicking on the "OK, I'm a doofus and I promise to try harder next time" button.
And a quote from Buffy, maybe from around Willow's addiction period.
Jon B. - Nov 28, 2002 8:58:45 pm PST #1771 of 10000
A turkey in every toilet -- only in America!
I'm thinking a page like the current Edit Post page. You see what the post will look like with the forced-closed tags, and you have an edit box immediately below it to allow the user to move the closed tags where he really wants them.
Sorry, the large amount of food in my stomach is affecting my ability to create grammatically clear sentences.
John H - Nov 28, 2002 9:02:46 pm PST #1772 of 10000
You see what the post will look like with the forced-closed tags, and you have an edit box immediately below it to allow the user to move the closed tags where he really wants them.
Makes sense. Seems very grammatical. Mind you the beer I had to celebrate my tax return might be affecting me.
§ ita § - Nov 28, 2002 9:06:51 pm PST #1773 of 10000
Well not canonically, no, but this is transformative fiction.
With error text to the effect of "You have x unclosed t b tags, y unclosed t i tags, and 1 unopened t /table tag."
Or something.
John H - Nov 28, 2002 9:11:20 pm PST #1774 of 10000
It'll be slightly easier, the way I've coded it, to say "the following tags didn't get closed: <b>,<i>,<b>,<table>" but same diff.
John H - Nov 29, 2002 12:34:17 am PST #1775 of 10000
OK I started thinking about the unclosed HREF problem.
Am I crazy or is it quite simple? We look for
HREF=
followed by a quote of some kind, and we check what's between that and the next quote, or what's between that and the end of the post, if no quote appears.
Like if we find
HREF="http://somewhere.com"
we grab the "http://somewhere.com" part and examine it for characters that shouldn't be there.
That way if we find we've grabbed
HREF="http://somewhere.com' >somewhere interesting</a>
... so, as I was saying...
we'll find the spaces, the brackets and so on, "inside" the HREF, which tell us that it's not a valid link.