{"id":65560,"date":"2024-11-13T03:01:00","date_gmt":"2024-11-12T17:01:00","guid":{"rendered":"https:\/\/www.rjmprogramming.com.au\/ITblog\/?p=65560"},"modified":"2024-11-13T05:38:46","modified_gmt":"2024-11-12T19:38:46","slug":"textarea-content-masking-tutorial","status":"publish","type":"post","link":"https:\/\/www.rjmprogramming.com.au\/ITblog\/textarea-content-masking-tutorial\/","title":{"rendered":"Textarea Content Masking Tutorial"},"content":{"rendered":"
\"Textarea<\/a>

Textarea Content Masking Tutorial<\/p><\/div>\n

Our fascination with the HTML textarea element (well, you had to be there)<\/font> continues further to some ideas at Textarea and Div Box Shadow Primer Tutorial<\/a> recently. Today’s interest is to do with a piece of functionality, that as a default, is missing. The thing is, the …<\/p>\n


\npattern<\/a> attribute is only available for input element (types text, date, search, url, tel, email and password)
\n<\/code><\/p>\n

… and we’re thinking the reason, here, is to do with the line feed and carriage return additional talents the textarea element enjoys? Caviar, anyone?<\/a><\/p>\n

Think of this pattern attribute idea, as like … like … you like?<\/sup> … a content mask<\/i> over textual (keyboard generated) content. You’ve probably seen it in action filling out your telephone number on some online form, and certain characters will not be allowed … like … type of thing.<\/p>\n

Well, today, with an inhouse project, we’re going to tip our toes into pursuing some inhouse ideas here, and see how far we go … maybe, eventually, via the use of an external Javascript call … we’ll see. Today’s start, though, offers the user a chance to enter into some textboxes, optionally containing, either …<\/p>\n

    \n
  1. character set disallowed<\/li>\n
  2. character set allowed<\/li>\n<\/ol>\n

    … regarding keyboard entries made into an accompanying textarea element also presented in a first draft textarea_onkeyup.html<\/a> Textarea Content Masking<\/a> web application …<\/p>\n