Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Switching pages causes select/checkbox/radio fields to briefly highlight as invalid #2007

Closed
helllicht opened this issue Aug 16, 2019 · 1 comment

Comments

@helllicht
Copy link

commented Aug 16, 2019

Describe the bug

When switching pages in the panel (for example by using the left/right navigation to switch between sibling pages or by navigation to parent or child page) all fields of type radio/checkbox/select are highlighted as "invalid" just before the pages switches. So it's only there for a brief moment.

Important to mention that this happens although the fields are not required and filled out.
Also, when switching away and back to the page, the fields will still not show up as invalid – because they aren't. The "flashing" only appears in the split second before switching away.

To Reproduce

Steps to reproduce the behavior:

  1. Add any field with the afflicted field types (select / checkbox / radio) to a page blueprint
  2. Navigate away from the page, e.g. to a sibling page with same blueprint
  3. See "flashing" of afflicted fields with "error" style (see screenshot above)

Expected behavior

Prior to Kirby 3.2.(3) switching pages did not result in the behavior described above. The fields should not validate as "invalid" if they aren't.

Screenshots

Bildschirmfoto 2019-08-16 um 13 48 27

Kirby Version

3.2.3

@helllicht helllicht changed the title Switching pages causes select/checkbox/radio fields to briefly highlight as erroneous Switching pages causes select/checkbox/radio fields to briefly highlight as invalid Aug 16, 2019
distantnative added a commit that referenced this issue Sep 14, 2019
@distantnative distantnative self-assigned this Sep 14, 2019
@distantnative distantnative added this to the 3.2.5 milestone Sep 14, 2019
distantnative added a commit that referenced this issue Sep 15, 2019
bastianallgeier added a commit that referenced this issue Sep 16, 2019
@bastianallgeier

This comment has been minimized.

Copy link
Contributor

commented Sep 16, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
3 participants
You can’t perform that action at this time.