Two bugs according to read only fields

Torsten Landsiedel
(@zodiac1978)

1 week ago

Hi there!

I think I have found two bugs in your plugin (maybe just the second is a bug and I misunderstood the docs).

(1) If you apply the CSS class ff-read-only to a select field, it is not disabled. If this works only on input fields, this could be texted a little bit clearer. Or even better, this could be implemented via JS if the class is there.

(2) The second one happens only in a multipage form with autofocus enabled. If the first field on a page is a read only date field the autofocus still opens the date picker and allows changing the date, although this field should not be allowed to be changed.

Just a heads-up!

All the best
Torsten

Viewing 3 replies - 1 through 3 (of 3 total)

Plugin Support akilgazi
(@akilgazi)

1 week ago
Thank you for reporting these issues.

For the first issue, we tested the ff-read-only class on our end, and it is working as expected. We’ve also shared a short video for your reference. [Video]

Please make sure that the ff-read-only class is added under the Element Class option, and then try the following:
1. Clear your site and browser cache and test again.
2. Temporarily disable any optimization or caching plugins to rule out possible JavaScript or CSS conflicts.
For the second issue, we were able to reproduce the behavior with the autofocus and read-only date field. We’ve forwarded this to our development team for further investigation.

We appreciate you bringing these issues to our attention.
Thread Starter Torsten Landsiedel
(@zodiac1978)

1 week ago

Hi @akilgazi

thanks for the ultra-fast reply on a Saturday. Much appreciated!

And sorry for my bad report. I forgot to mention, that I enabled “Enable Searchable Smart Options” (which uses choices.js). With this option enabled the select is not read only anymore.

Thanks for reporting the other issue to the dev team and sorry for missing the crucial detail in my first report.

All the best
Torsten

Plugin Support akilgazi
(@akilgazi)

1 week ago

No worries at all, and thank you for providing the additional detail.

We’ve also been able to reproduce the issue with “Enable Searchable Smart Options” enabled, and we’ve forwarded it to our development team for further investigation.

We appreciate the clarification and your help in identifying the issue.

Viewing 3 replies - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.