You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
I suspect the root of this issue to be the duplicate header titles.
With the
Examples
tab active, clicking the "Matching Fields" header under the sidebarRule Examples
header incorrectly makes theUsage
tab active. The expected behavior upon clicking "Matching Fields" (withExamples
active) would be scrolling to the "Matching Fields" header that is under theExamples
tab. The other buttons (such as "Payment" and "Length") do this correctly.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 theUsage
tab). The expected behavior here would be to make the "Matchin Fields" header under theExamples
tab to become active in the browser URL field, as well as to have it scrolled to the top edge of the screen.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
The text was updated successfully, but these errors were encountered: