[BUG]: duplicate form field in the same form

[qutluq]

Describe the bug

Navigating to the Settings tab generates duplicate form field in the same form bug on the issues tab.

Steps to reproduce

1. Go to Settings tab.
2. Open web developers tools by choosing Inspect from the context menu.
3. Navigate to the issues tab.
4. See the error message in red: "duplicate form field in the same form".

Expected behavior

There should be no such message on the issues tab.

Screenshots

Additional information

No response

[armichaud]

@qutluq is this issue still active? I'm unable to reproduce this bug while running the dev platform app on Chrome Version 115.0.5790.114 on MacOS. As you'll see in the screenshot below, the issues tab does not flag multiple selectors with the same id. The console shows that two select tags have the same tabs value as their id, but both of these are hidden dropdowns that seem to have been replaced by newer UI features (I have disabled the sm:hidden class for those two elements in the screenshot below to highlight what I'm talking about).

[qutluq]

@armichaud apparently Google Chrome does not inform us about duplicate ids in the page anymore, as in the case of duplicate form field ids. Tried to reproduce it on my machine, and did not succeed. My version of chrome is 115.0.5790.171 (Official Build) (64-bit) on Windows 10. But, the duplicate ids are still there, you can find them by searching tabs keyword on Elements tab of Chrome dev tools on the mentioned page.

As discussed here the duplicate ids can still cause problems.

Usually developers do not recommend using the same id more than once, but since the bug is gone, we may leave it be, and close this issue.

@dahal What do you think, should we close it?

[armichaud]

Oh I agree in principle that there shouldn't be more than one element with the same ID attribute, I was initially unsure of the impact given that both elements were hidden by default. I've since realized that these drop-downs are visible on narrower viewports, and so the duplicate IDs should be addressed.

Since this is just a one-line fix, I went ahead and put together a PR: #574