Skip Navigation

[Resolved] W3C error on distance filter

This support ticket is created 2 years, 6 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: Asia/Karachi (GMT+05:00)

This topic contains 4 replies, has 2 voices.

Last updated by martijnH 2 years, 6 months ago.

Assisted by: Waqar.

Author
Posts
#2376455
2022-06-02_17-17-25.jpg

The input element below is failing in w3c validation, because attribute 'min' is not allowed at this point. 'min' attributes on input elements are only allowed when type is date, month, week, time, datetime-local, number or range.

Do you have a fix for this?

<input type="text" id="toolset-maps-distance-center" name="center" class="form-control js-toolset-maps-distance-center js-wpv-filter-trigger-delayed js-toolset-maps-address-autocomplete pac-target-input" value="" placeholder="Voer uw plaats of postcode in" aria-label="Enter a location" autocomplete="off">

The element can be found on this page hidden link

#2376871

Hi,

Thank you for contacting us and I'd be happy to assist.

I've shared this feedback internally with the concerned team for further review.

Unfortunately, there is no hook or filter available to override that part of the markup, so for now, you can remove min="0" part by editing the plugin file "/wp-content/plugins/toolset-maps/includes/toolset-views-maps-distance-filter.php" at line# 1506:


<input type="text" min="0" id="toolset-maps-distance-center"

regards,
Waqar

#2379377

Hi,

Thanks for this solution. Are you going to implement this in an update?

#2379521

Thanks for writing back.

Yes, as the nature of this fix is very simple, most likely it will be covered in the next Maps plugin release.

#2379567

My issue is resolved now. Thank you!