Class PasswordField

All Implemented Interfaces:
AttachNotifier, BlurNotifier<PasswordField>, CompositionNotifier, DetachNotifier, Focusable<PasswordField>, FocusNotifier<PasswordField>, HasAriaLabel, HasElement, HasEnabled, HasHelper, HasLabel, HasSize, HasStyle, HasTheme, HasValidation, HasValue<AbstractField.ComponentValueChangeEvent<PasswordField,String>,String>, HasValueAndElement<AbstractField.ComponentValueChangeEvent<PasswordField,String>,String>, InputNotifier, KeyNotifier, HasAllowedCharPattern, HasClearButton, HasClientValidation, HasPrefix, HasSuffix, HasThemeVariant<TextFieldVariant>, HasTooltip, HasValidationProperties, InputField<AbstractField.ComponentValueChangeEvent<PasswordField,String>,String>, HasAutocapitalize, HasAutocomplete, HasAutocorrect, HasPrefixAndSuffix, HasValidator<String>, HasValueChangeMode, Serializable

@Tag("vaadin-password-field") @NpmPackage(value="@vaadin/polymer-legacy-adapter",version="24.2.3") @NpmPackage(value="@vaadin/password-field",version="24.2.3") @JsModule("@vaadin/polymer-legacy-adapter/style-modules.js") @JsModule("@vaadin/password-field/src/vaadin-password-field.js") public class PasswordField extends TextFieldBase<PasswordField,String> implements HasAllowedCharPattern, HasThemeVariant<TextFieldVariant>
Password Field is an input field for entering passwords. The input is masked by default. On mobile devices the last typed letter is shown for a brief moment. The masking can be toggled using an optional reveal button.
Author:
Vaadin Ltd.
See Also:
  • Constructor Details

  • Method Details

    • setMaxLength

      public void setMaxLength(int maxLength)
      Maximum number of characters (in Unicode code points) that the user can enter.
      Parameters:
      maxLength - the maximum length
    • getMaxLength

      public int getMaxLength()
      Maximum number of characters (in Unicode code points) that the user can enter.
      Returns:
      the maxlength property from the webcomponent
    • setMinLength

      public void setMinLength(int minLength)
      Minimum number of characters (in Unicode code points) that the user can enter.
      Parameters:
      minLength - the minimum length
    • getMinLength

      public int getMinLength()
      Minimum number of characters (in Unicode code points) that the user can enter.
      Returns:
      the minlength property from the webcomponent
    • setRequired

      public void setRequired(boolean required)
      Description copied from class: TextFieldBase
      Specifies that the user must fill in a value.
      Overrides:
      setRequired in class TextFieldBase<PasswordField,String>
      Parameters:
      required - the boolean value to set
    • setPattern

      public void setPattern(String pattern)
      Sets a regular expression for the value to pass on the client-side. The pattern must be a valid JavaScript Regular Expression that matches the entire value, not just some subset.
      Parameters:
      pattern - the new String pattern
      See Also:
    • getPattern

      public String getPattern()
      A regular expression that the value is checked against. The pattern must match the entire value, not just some subset.
      Returns:
      the pattern property from the webcomponent
    • isRevealButtonVisible

      public boolean isRevealButtonVisible()
      Set to false to hide the eye icon which toggles the password visibility.
      Returns:
      true if the button is visible, false otherwise
    • setRevealButtonVisible

      public void setRevealButtonVisible(boolean revealButtonVisible)
      Set to false to hide the eye icon which toggles the password visibility.
      Parameters:
      revealButtonVisible - true to set the button visible, false otherwise
    • getEmptyValue

      public String getEmptyValue()
      Description copied from interface: HasValue
      Returns the value that represents an empty value.

      By default HasValue is expected to support null as empty values. Specific implementations might not support this.

      Specified by:
      getEmptyValue in interface HasValue<AbstractField.ComponentValueChangeEvent<PasswordField,String>,String>
      Overrides:
      getEmptyValue in class AbstractField<PasswordField,String>
      Returns:
      empty value
    • setValue

      public void setValue(String value)
      Sets the value of this password field. If the new value is not equal to getValue(), fires a value change event. Throws NullPointerException, if the value is null.

      Note: Binder will take care of the null conversion when integrates with password field, as long as no new converter is defined.

      Specified by:
      setValue in interface HasValue<AbstractField.ComponentValueChangeEvent<PasswordField,String>,String>
      Overrides:
      setValue in class AbstractField<PasswordField,String>
      Parameters:
      value - the new value, not null
    • getValue

      public String getValue()
      Returns the current value of the password field. By default, the empty password field will return an empty string.
      Specified by:
      getValue in interface HasValue<AbstractField.ComponentValueChangeEvent<PasswordField,String>,String>
      Overrides:
      getValue in class AbstractField<PasswordField,String>
      Returns:
      the current value.
    • setRequiredIndicatorVisible

      public void setRequiredIndicatorVisible(boolean requiredIndicatorVisible)
      Description copied from interface: HasValue
      Sets the required indicator visible or not.

      If set visible, it is visually indicated in the user interface.

      The method is intended to be used with Binder which does server-side validation. In case HTML element has its own (client-side) validation it should be disabled when setRequiredIndicatorVisible(true) is called and re-enabled back on setRequiredIndicatorVisible(false). It's responsibility of each component implementation to follow the contract so that the method call doesn't do anything else than show/hide the "required" indication. Usually components provide their own setRequired method which should be called in case the client-side validation is required.

      Specified by:
      setRequiredIndicatorVisible in interface HasValue<AbstractField.ComponentValueChangeEvent<PasswordField,String>,String>
      Specified by:
      setRequiredIndicatorVisible in interface HasValueAndElement<AbstractField.ComponentValueChangeEvent<PasswordField,String>,String>
      Parameters:
      requiredIndicatorVisible - true to make the required indicator visible, false if not
    • getDefaultValidator

      public Validator<String> getDefaultValidator()
      Description copied from interface: HasValidator
      Returns a validator that checks the state of the Value. This should be overridden for components with internal value conversion or validation, e.g. when the user is providing a string that has to be parsed into a date. An invalid input from user will be exposed to a Binder and can be seen as a validation failure.
      Specified by:
      getDefaultValidator in interface HasValidator<String>
      Returns:
      state validator
    • addValidationStatusChangeListener

      public Registration addValidationStatusChangeListener(ValidationStatusChangeListener<String> listener)
      Description copied from interface: HasValidator
      Enables the implementing components to notify changes in their validation status to the observers.

      Note: This method can be overridden by the implementing classes e.g. components, to enable the associated Binder.Binding instance subscribing for their validation change events and revalidate itself.

      This method primarily designed for notifying the Binding about the validation status changes of a bound component at the client-side. WebComponents such as <vaadin-date-picker> or any other component that accept a formatted text as input should be able to communicate their invalid status to their server-side instance, and a bound server-side component instance must notify its binding about this validation status change as well. When the binding instance revalidates, a chain of validators and convertors get executed one of which is the default validator provided by HasValidator.getDefaultValidator(). Thus, In order for the binding to be able to show/clear errors for its associated bound field, it is important that implementing components take that validation status into account while implementing any validator and converter including HasValidator.getDefaultValidator(). Here is an example:

       @Tag("date-picker-demo")
       public class DatePickerDemo implements HasValidator<LocalDate> {
      
           // Each web component has a way to communicate its validation status
           // to its server-side component instance. The following clientSideValid
           // state is introduced here just for the sake of simplicity of this code
           // snippet:
           boolean clientSideValid = true;
      
           /**
            * Note how clientSideValid engaged in the definition
            * of this method. It is important to reflect this status either
            * in the returning validation result of this method or any other
            * validation that is associated with this component.
            */
           @Override
           public Validator getDefaultValidator() {
                return (value, valueContext) -> clientSideValid ? ValidationResult.ok()
                       : ValidationResult.error("Invalid date format");
           }
      
           private final Collection<ValidationStatusChangeListener<LocalDate>>
               validationStatusListeners = new ArrayList<>();
      
           /**
            * This enables the binding to subscribe for the validation status
            * change events that are fired by this component and revalidate
            * itself respectively.
            */
           @Override
           public Registration addValidationStatusChangeListener(
                   ValidationStatusChangeListener<LocalDate> listener) {
               validationStatusListeners.add(listener);
               return () -> validationStatusListeners.remove(listener);
           }
      
           private void fireValidationStatusChangeEvent(
                   boolean newValidationStatus) {
               if (this.clientSideValid != newValidationStatus) {
                   this.clientSideValid = newValidationStatus;
                   var event = new ValidationStatusChangeEvent<>(this,
                           newValidationStatus);
                   validationStatusListeners.forEach(
                           listener -> listener.validationStatusChanged(event));
               }
           }
       }
       
      Specified by:
      addValidationStatusChangeListener in interface HasValidator<String>
      Returns:
      Registration of the added listener.
      See Also:
    • setManualValidation

      public void setManualValidation(boolean enabled)
      Description copied from interface: HasValidation
      Sets whether manual validation mode is enabled for the component.

      When enabled, the component doesn't perform its built-in constraint validation on value change, blur, and other events. This allows manually controlling the invalid state and error messages using the HasValidation.setInvalid(boolean) and HasValidation.setErrorMessage(String) methods. Manual mode is helpful when there is a need for a totally custom validation logic that cannot be achieved with Binder.

      Example:

       Field field = new Field();
       field.setManualValidation(true);
       field.addValueChangeListener(event -> {
           if (Objects.equal(event.getValue(), "")) {
               field.setInvalid(true);
               field.setErrorMessage("The field is required.");
           } else {
               field.setInvalid(false);
           }
       });
       

      For components that don't have built-in validation, the method has no effect.

      Specified by:
      setManualValidation in interface HasValidation
      Parameters:
      enabled - whether to enable manual validation mode.
    • validate

      protected void validate()
      Performs server-side validation of the current value. This is needed because it is possible to circumvent the client-side validation constraints using browser development tools.
    • onAttach

      protected void onAttach(AttachEvent attachEvent)
      Description copied from class: Component
      Called when the component is attached to a UI.

      The default implementation does nothing.

      This method is invoked before the AttachEvent is fired for the component.

      Overrides:
      onAttach in class Component
      Parameters:
      attachEvent - the attach event