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

"Matching Fields" header may be linked incorrectly on Form Validation #501

Open
mdrxy opened this issue May 9, 2024 · 1 comment
Open
Labels
Confirmed Bug Issues which are confirmed to be a bug next Release
Milestone

Comments

@mdrxy
Copy link

mdrxy commented May 9, 2024

With the Examples tab active, clicking the "Matching Fields" header under the sidebar Rule Examples header incorrectly makes the Usage tab active. The expected behavior upon clicking "Matching Fields" (with Examples active) would be scrolling to the "Matching Fields" header that is under the Examples tab. The other buttons (such as "Payment" and "Length") do this correctly.

Screenshot 2024-05-08 at 23 19 00

Furthermore, even if you do scroll to the "Matching Fields" header under the Examples tab, if you click the header (or copy the header as a link), the same issue persists (wherein the user is brought to the Usage tab). The expected behavior here would be to make the "Matchin Fields" header under the Examples tab to become active in the browser URL field, as well as to have it scrolled to the top edge of the screen.

Screenshot 2024-05-08 at 23 26 27

I suspect the root of this issue to be the duplicate header titles.

https://github.com/fomantic/Fomantic-UI-Docs/blob/master/server/documents/behaviors/form.html.eco

@lubber-de
Copy link
Member

Thanks for reporting!
Fixed by #502

@lubber-de lubber-de added this to the 2.9.4 milestone May 10, 2024
@lubber-de lubber-de added Confirmed Bug Issues which are confirmed to be a bug next Release labels May 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Confirmed Bug Issues which are confirmed to be a bug next Release
Projects
None yet
Development

No branches or pull requests

2 participants