Re: Displaying text and populating form fields

This WebDNA talk-list message is from

2005


It keeps the original formatting.
numero = 61151
interpreted = N
texte = on 2/23/2005 12:09 pm, Donovan Brooke at dbrooke@euca.us so noted... > If it makes you feel better to use [input] in non-textarea > situations, then do it... I don't think it should harm anything > but its overkill, and it converts some unnecessary characters > (which I suppose can make it harder if the text is viewable > for editing). [input] wouldn't make things harder for editing viewable text. Any characters converted to HTML entities by [input] would (unlike when using [url]) be presented onscreen as the original, single character. Converting <>&" to < > & " is useful in the body of a web page too, not just in forms. Rob Marquardt Designer/Resident Wirehead Toast Design 800 Washington Avenue North Minneapolis MN 55401 612.330.9863 v 612.321.9424 f www.toastdesign.com ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ Associated Messages, from the most recent to the oldest:

    
  1. Re: Displaying text and populating form fields (again) ( Kenneth Grome 2005)
  2. Re: Displaying text and populating form fields (again) ( Donovan Brooke 2005)
  3. Re: Displaying text and populating form fields (again) ( Stuart Tremain 2005)
  4. Re: Displaying text and populating form fields (again) ( Stuart Tremain 2005)
  5. Re: Displaying text and populating form fields (again) ( Donovan Brooke 2005)
  6. Re: Displaying text and populating form fields (again) ( Stuart Tremain 2005)
  7. Re: Displaying text and populating form fields (again) ( Donovan Brooke 2005)
  8. Re: Displaying text and populating form fields (again) ( Stuart Tremain 2005)
  9. Displaying text and populating form fields (again) ( eLists 2005)
  10. Re: Displaying text and populating form fields (again) ( "eLists" 2005)
  11. Re: Displaying text and populating form fields ( eLists 2005)
  12. Re: Displaying text and populating form fields ( "eLists" 2005)
  13. Re: Displaying text and populating form fields ( John Peacock 2005)
  14. Re: Displaying text and populating form fields ( Kenneth Grome 2005)
  15. Re: Displaying text and populating form fields ( Donovan Brooke 2005)
  16. Re: Displaying text and populating form fields ( Kenneth Grome 2005)
  17. Re: Displaying text and populating form fields ( Kenneth Grome 2005)
  18. Re: Displaying text and populating form fields ( Kenneth Grome 2005)
  19. Re: Displaying text and populating form fields ( Rob Marquardt 2005)
  20. Re: Displaying text and populating form fields ( Donovan Brooke 2005)
  21. Re: Displaying text and populating form fields ( Donovan Brooke 2005)
  22. Re: Displaying text and populating form fields ( Rob Marquardt 2005)
  23. Re: Displaying text and populating form fields ( Donovan Brooke 2005)
  24. Re: Displaying text and populating form fields ( Donovan Brooke 2005)
  25. Re: Displaying text and populating form fields ( Rob Marquardt 2005)
  26. Re: Displaying text and populating form fields ( Terry Wilson 2005)
  27. Re: Displaying text and populating form fields ( John Peacock 2005)
  28. Re: Displaying text and populating form fields ( Rob Marquardt 2005)
  29. Re: Displaying text and populating form fields ( Donovan Brooke 2005)
  30. Re: Displaying text and populating form fields ( Terry Wilson 2005)
  31. Displaying text and populating form fields ... ( Kenneth Grome 2005)
on 2/23/2005 12:09 pm, Donovan Brooke at dbrooke@euca.us so noted... > If it makes you feel better to use [input] in non-textarea > situations, then do it... I don't think it should harm anything > but its overkill, and it converts some unnecessary characters > (which I suppose can make it harder if the text is viewable > for editing). [input] wouldn't make things harder for editing viewable text. Any characters converted to HTML entities by [input] would (unlike when using [url]) be presented onscreen as the original, single character. Converting <>&" to < > & " is useful in the body of a web page too, not just in forms. Rob Marquardt Designer/Resident Wirehead Toast Design 800 Washington Avenue North Minneapolis MN 55401 612.330.9863 v 612.321.9424 f www.toastdesign.com ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ Rob Marquardt

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:

Credit card number for testing (2003) WebCatalog for Dummies part 2 (2000) Attn: Bug in GeneralStore example b15 (1997) grep matching (2003) WebCat2b13MacPlugIn - [showif][search][/showif] (1997) Is this possible, WebCat2.0 and checkboxes (1997) international time (1997) WebCat2 - [format thousands] (1997) [WebDNA] Limits? (2009) Email (1998) Opinion: [input] should be called [output] ... (1997) Exclamation point (1997) [WebDNA] WebDNA and MAMP/Apache (Mac) (2018) credit card services (1997) Random search is not random (2002) [WebDNA] WebDNA and MAMP/Apache (Mac) (2018) [WebDNA] Hmmm ... and thanks! (2008) WebMerchant/MacAuthorize (1998) RE: Clearing orders and database help! (1997) Showif, Hideif reverse logic ? (1997)