Step attribute on input type time is not supported.

Same problem here. Just noticed the error in the console when filling out the time part of a date field.

Thanks! That brought me on track.

I got this working for all time fields being present on first page load. For new fields coming in after loading in a paragraphs type using ajax I did not achieve it yet. I still think this bug should be solved in the main module.

$(document).once('cvjquery').on('cv-jquery-validate-options-update', function (event, options) {
  function cvrules() {
    item = {}
    $("input[type=time]").each(function() {
      var field_name = $(this).attr("name");
      item [field_name] = {'step': false};
    });
    return item;
  }
  options.rules = cvrules();
});

I created a MR based in #5 to provide this rules by default on module

Created patch from MR in #7.

This looks like a workaround to me, the step attribute in the input[type=time] is indeed valid.

Instead of removing the step attribute the plugin should allow to use it.

This issue boils down to a limitation in the jQuery validation library currently only supporting text, number and range inputs.

https://github.com/jquery-validation/jquery-validation/blob/master/src/c...

// https://jqueryvalidation.org/step-method/
step: function( value, element, param ) {
	var type = $( element ).attr( "type" ),
		errorMessage = "Step attribute on input type " + type + " is not supported.",
		supportedTypes = [ "text", "number", "range" ],
//...
// Works only for text, number and range input types
// TODO find a way to support input types date, datetime, datetime-local, month, time and week
if ( notSupported ) {
	throw new Error( errorMessage );
}

There is an open stale PR that was never properly reviewed by maintainers of jQuery validation probably due to the effort to test all the different date/time input types and the fact that there are no automated tests or even manual tests provided.

https://github.com/jquery-validation/jquery-validation/pull/2119

Amazingly the patch applies cleanly, with offsets to the "dist" version of the jquery.validate.js file, despite the diff being generated against the "src/core.js", if you just specify the dist file, it applies!

$ cd docroot/libraries/jquery-validate
$ wget https://patch-diff.githubusercontent.com/raw/jquery-validation/jquery-validation/pull/2119.diff
$ patch -p1 < 2119.diff
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/src/core.js b/src/core.js
|index f2d98611..88224f78 100644
|--- a/src/core.js
|+++ b/src/core.js
--------------------------
File to patch: dist/jquery.validate.js
patching file dist/jquery.validate.js
Hunk #1 succeeded at 1087 (offset 43 lines).
Hunk #2 succeeded at 1512 (offset 66 lines).
Hunk #3 succeeded at 1592 (offset 66 lines).
Hunk #4 succeeded at 1605 (offset 66 lines).

However the issue then becomes the minified version jquery.validate.min.js

Fortuitously, the Drupal module loads the unminified version when it is configured to NOT use the CDN.

So I've copied the diff file to my local patches/ folder in the repository and changed "src/core.js" to "dist/jquery.validate.js" and put it into composer and it worked.

So, as long as you're using the npm-asset method documented in the composer.example.json file provided with the clientside_validation module, you can add the following to the "extra" > "patches" section in composer.json and get it working.

"npm-asset/jquery-validation": {
  "#3200530 - Step attribute on input type time is not supported": "https://www.drupal.org/files/issues/2022-02-22/3200530-jquery-validate-step-datetime-inputs.patch"
}

It appears that the PR approach on https://github.com/jquery-validation/jquery-validation/pull/2119 has some issues with Drupal node's date fields.

I'm unable to save the node due to client side validation errors on the min/max functionality that the PR adds for date fields. Something seems wrong with the MM/DD/YYYY format.

Note, this screenshot is using the Publication Date module, but I assume the same thing would happen with just native Drupal and the Authored on field.

We're seeing this error on our site, too. I wanted to understand the root cause, and it seems to be this module.

To verify that no custom code on our side was throwing this, I created a site on Simplytest.me with the following modules installed and enabled
- office_hours@1.17.0
- clientside_validation@4.0.2
- clientside_validation_jquery@4.0.2

I used the default configuration.

While entering the hour range, the site threw this error when going from the "From" to the "To" field.

Still seeing this in 2025, anyone come up with a useful workaround for it?

@jackfoust I posted a patch on issue 2949540 for allowing us to exclude forms by form id so that we could use the browser's built-in validation. That is our current work-around.