Re: Stopping bad HTML propagation ?

This WebDNA talk-list message is from

1997


It keeps the original formatting.
numero = 11522
interpreted = N
texte = > >Any suggestions or ideas ? Hi,Wost thing I've seen is when a guy changes the text color to match the same color as the background. Had this happen in chat rooms. Without the close tag, room goes dead right then.Back to suggestions?I'm trying to also put some of this remote power in the hands of the users. I'm trying to come up with lots of pre-flight proving-ground testing-locations where things can be checked on my server. You've got to give the authors of the content chances to screw around and not feel like the submit button might take down his/her page -- if not more.Then the next thing to implement is a way that the preflight can be approved with a simple button (perhaps) -- and then automatically cloned and put into the right location without needing to do a cut and paste.I'm thinking a whole test catalog devoted to pre-flight is one way to go. Perhaps some type of third catalog or some other methods could hold the scripts --> clone --> update --> copy & paste to live catalog routines. ??Sorry this post isn't much of a specific code helper to you. Go for it.-------------- Mark Rauterkus, Publisher, S.S.S.mrauterkus@sportsurf.net -------------- Associated Messages, from the most recent to the oldest:

    
  1. Re: Stopping bad HTML propagation ? (Ed Trefzger 1997)
  2. Re: Stopping bad HTML propagation ? (Sven U. Grenander 1997)
  3. Re: Stopping bad HTML propagation ? (Grant Hulbert 1997)
  4. Stopping bad HTML propagation ? (Sven U. Grenander 1997)
  5. Re: Stopping bad HTML propagation ? (Publisher1 1997)
> >Any suggestions or ideas ? Hi,Wost thing I've seen is when a guy changes the text color to match the same color as the background. Had this happen in chat rooms. Without the close tag, room goes dead right then.Back to suggestions?I'm trying to also put some of this remote power in the hands of the users. I'm trying to come up with lots of pre-flight proving-ground testing-locations where things can be checked on my server. You've got to give the authors of the content chances to screw around and not feel like the submit button might take down his/her page -- if not more.Then the next thing to implement is a way that the preflight can be approved with a simple button (perhaps) -- and then automatically cloned and put into the right location without needing to do a cut and paste.I'm thinking a whole test catalog devoted to pre-flight is one way to go. Perhaps some type of third catalog or some other methods could hold the scripts --> clone --> update --> copy & paste to live catalog routines. ??Sorry this post isn't much of a specific code helper to you. Go for it.-------------- Mark Rauterkus, Publisher, S.S.S.mrauterkus@sportsurf.net -------------- Publisher1

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

MacOS X Server problems (2001) How far do [showif]s go? (1997) carriage returns in data (1997) email error (2003) Bug Report, maybe (1997) [OT] DOD again (2003) [username][password] not showing up. (2000) Great product and great job ! (1997) Find one not all, code not working (2003) problem serving foreign languages text (1997) 3.0 [TEXT] variables (1998) WebCatalog2 Feature Feedback (1996) File commands and Wild Cards ?? (1998) WebCatalog Plug-in for Webstar. (1997) WebCat2.0 [format thousands .0f] no go (1997) no global [username] or [password] displayed ... (1997) How to display images? (2002) What am I doing wrong? (2000) encrypt (2000) UPDATE PROBLEM (1997)