Table of Contents
Constraint API
Translation of custom form verification message
Method 1: Use the browser's language settings
Method 2: Set the preferred language in local storage
Summary
Reference
Home Web Front-end CSS Tutorial Two Ways to Create Custom Translated Messaging for HTML Forms

Two Ways to Create Custom Translated Messaging for HTML Forms

Mar 08, 2025 am 09:57 AM

Two Ways to Create Custom Translated Messaging for HTML Forms

HTML forms have built-in methods to verify form input and other controls based on predefined rules such as setting input as required, setting minimum and maximum constraints for range sliders, or setting modes for email inputs to check if the format is correct. Native HTML and browsers provide us with many "free" features to verify form submissions without complex scripts.

If something is not verified correctly? We will get a "free" error message to show to the person using the form.

These are usually enough to get the job done, but if we need more specific error content, we may need to override these messages – especially if we need to process translated content across browsers. Here is how it works.

Constraint API

Constraint API is used to override the default HTML form validation message and allows us to define our own error message. Chris Ferdinandi even gave a detailed look at this on CSS-Tricks.

In short, the constraint API is designed to provide control over input elements. The API can be called in a single input element or directly from a form element.

For example, suppose we are using this simple form input:

<label for="fullName">Full Name</label>
<input type="text" id="fullName" required>
<button type="submit" id="btn">Submit</button>
Copy after login
Copy after login

We can set our own error message by getting the fullNameInput element and calling the setCustomValidity() method on it, and then passing it a custom message:

const fullNameInput = document.getElementById("fullName");
fullNameInput.setCustomValidity("This is a custom error message");
Copy after login
Copy after login

When you click the Submit button, the specified message will be displayed in the default message location.

Translation of custom form verification message

One of the main use case for custom error messages is to better handle internationalization. We can do this in two main ways. There are other ways to achieve this, but I'm going to introduce here the one I think is the most straightforward.

Method 1: Use the browser's language settings

The first method is to use the browser language settings. We can get the language settings from the browser and then check if we support the language. If we support the language, we can return the translated message. If we do not support that particular language, an alternate response is provided.

Continue to using the previous HTML, we will create a translation object to save your preferred language (inside the script tag). In this case, the object supports English, Swahili, and Arabic.

const translations = {
  en: {
    required: "Please fill this",
    email: "Please enter a valid email address",

  },
  sw: {
    required: "Sehemu hii inahitajika",
    email: "Tafadhali ingiza anwani sahihi ya barua pepe",
  },
  ar: {
    required: "هذه الخانة مطلوبه",
    email: "يرجى إدخال عنوان بريد إلكتروني صالح",
  }
};
Copy after login

Next, we need to extract the tags of the objects and match them to the browser's language.

// 翻译对象
const supportedLangs = Object.keys(translations);
const getUserLang = () => {
  // 拆分以获取第一部分,浏览器通常为 en-US
  const browserLang = navigator.language.split('-')[0];
  return supportedLangs.includes(browserLang) ? browserLang :'en';
};

// 翻译后的错误消息
const errorMsgs = translations[getUserLang()];
// 表单元素
const form = document.getElementById("myForm");
// 按钮元素
const btn = document.getElementById("btn");
// 名称输入
const fullNameInput = document.getElementById("fullName");
// 错误消息的包装器
const errorSpan = document.getElementById("error-span");

// 单击按钮时……
btn.addEventListener("click", function (event) {
  // 如果名称输入不存在……
  if (!fullNameInput.value) {
    // ……抛出错误
    fullNameInput.setCustomValidity(errorMsgs.required);
    // 为样式设置输入的 .error 类
    fullNameInput.classList.add("error");
  }
});
Copy after login

The getUserLang() function here compares and returns the supported browser language or alternative languages ​​in English. Run the example, when the button is clicked, a custom error message should be displayed.

Method 2: Set the preferred language in local storage

The second method is to use user-defined language settings in localStorage . In other words, we ask users to first select their preferred language from the <option></option> elements containing the optional <select></select> tag. Once the choice is made, we save their preferences to localStorage so that we can reference it.

<label for="fullName">Full Name</label>
<input type="text" id="fullName" required>
<button type="submit" id="btn">Submit</button>
Copy after login
Copy after login

With the <select></select> element, we can create a script that checks localStorage and uses saved preferences to return a translated custom verification message:

const fullNameInput = document.getElementById("fullName");
fullNameInput.setCustomValidity("This is a custom error message");
Copy after login
Copy after login

This script sets the initial value to the currently selected option, saves the value to localStorage, and retrieves it from localStorage as needed. Meanwhile, the script updates the selected options in every change event triggered by the <select></select> element while maintaining the original fallback to ensure a good user experience.

If we turn on DevTools, when selecting language preferences, we will see that the user's preferred value is available in localStorage.

Summary

That's it! I hope this quick little trick helps. I know I wanted to have it before when figuring out how to use the constraint API. This is one of those things on the web that you know possible, but the exact method is hard to find.

Reference

  • Form Verification Series (Chris Ferdinandi)
  • Understand the Pseudo-Class Selector (Chris Coyier)
  • Constraint Verification (MDN)
  • Client Form Verification (MDN)

The above is the detailed content of Two Ways to Create Custom Translated Messaging for HTML Forms. For more information, please follow other related articles on the PHP Chinese website!

Statement of this Website
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn

Hot AI Tools

Undresser.AI Undress

Undresser.AI Undress

AI-powered app for creating realistic nude photos

AI Clothes Remover

AI Clothes Remover

Online AI tool for removing clothes from photos.

Undress AI Tool

Undress AI Tool

Undress images for free

Clothoff.io

Clothoff.io

AI clothes remover

Video Face Swap

Video Face Swap

Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Roblox: Bubble Gum Simulator Infinity - How To Get And Use Royal Keys
1 months ago By 尊渡假赌尊渡假赌尊渡假赌
Nordhold: Fusion System, Explained
1 months ago By 尊渡假赌尊渡假赌尊渡假赌
Mandragora: Whispers Of The Witch Tree - How To Unlock The Grappling Hook
4 weeks ago By 尊渡假赌尊渡假赌尊渡假赌

Hot Tools

Notepad++7.3.1

Notepad++7.3.1

Easy-to-use and free code editor

SublimeText3 Chinese version

SublimeText3 Chinese version

Chinese version, very easy to use

Zend Studio 13.0.1

Zend Studio 13.0.1

Powerful PHP integrated development environment

Dreamweaver CS6

Dreamweaver CS6

Visual web development tools

SublimeText3 Mac version

SublimeText3 Mac version

God-level code editing software (SublimeText3)

Hot Topics

Java Tutorial
1677
14
PHP Tutorial
1279
29
C# Tutorial
1257
24
A Comparison of Static Form Providers A Comparison of Static Form Providers Apr 16, 2025 am 11:20 AM

Let’s attempt to coin a term here: "Static Form Provider." You bring your HTML

Weekly Platform News: HTML Loading Attribute, the Main ARIA Specifications, and Moving from iFrame to Shadow DOM Weekly Platform News: HTML Loading Attribute, the Main ARIA Specifications, and Moving from iFrame to Shadow DOM Apr 17, 2025 am 10:55 AM

In this week&#039;s roundup of platform news, Chrome introduces a new attribute for loading, accessibility specifications for web developers, and the BBC moves

A Proof of Concept for Making Sass Faster A Proof of Concept for Making Sass Faster Apr 16, 2025 am 10:38 AM

At the start of a new project, Sass compilation happens in the blink of an eye. This feels great, especially when it’s paired with Browsersync, which reloads

Some Hands-On with the HTML Dialog Element Some Hands-On with the HTML Dialog Element Apr 16, 2025 am 11:33 AM

This is me looking at the HTML element for the first time. I&#039;ve been aware of it for a while, but haven&#039;t taken it for a spin yet. It has some pretty cool and

Paperform Paperform Apr 16, 2025 am 11:24 AM

Buy or build is a classic debate in technology. Building things yourself might feel less expensive because there is no line item on your credit card bill, but

Quick Gulp Cache Busting Quick Gulp Cache Busting Apr 18, 2025 am 11:23 AM

You should for sure be setting far-out cache headers on your assets like CSS and JavaScript (and images and fonts and whatever else). That tells the browser

Where should 'Subscribe to Podcast' link to? Where should 'Subscribe to Podcast' link to? Apr 16, 2025 pm 12:04 PM

For a while, iTunes was the big dog in podcasting, so if you linked "Subscribe to Podcast" to like:

Weekly Platform News: Text Spacing Bookmarklet, Top-Level Await, New AMP Loading Indicator Weekly Platform News: Text Spacing Bookmarklet, Top-Level Await, New AMP Loading Indicator Apr 17, 2025 am 11:26 AM

In this week&#039;s roundup, a handy bookmarklet for inspecting typography, using await to tinker with how JavaScript modules import one another, plus Facebook&#039;s

See all articles