Dropdown fix

[cn1t]

Description

Please include a summary of the changes and the related issue. Please also include relevant motivation and context. List any dependencies that are required for this change.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update
• Project infrastructure change (like issue templates, etc.)

How Has This Been Tested?

Please check all browsers you have tested on. Please also list any relevant details for your test configuration

• Chromium Based Browser
• Mozilla Firefox

Test Configuration:

• Windows
• Linux
• MacOS
• BSD

Checklist:

• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules
• I am a web developer

[cn1t]

This now uses templating and works

[cn1t]

Finally

[9glenda]

Shouldn't we wait for #573 to be merged that would Marke Mord sense

[9glenda]

I implemented the new dropdown thing yesterday

[9glenda]

Merging this will just cause merge conflicts it will be removed as soon as I ported edit to the new dropdown implementation

[cn1t]

But this impl is working fully and the other impl still looks weird and is less responsive and uses the same amount of code

[9glenda]

The other impl is straight up bad code nobody understands it. It's just the CSS which needs to be improved in the other one. Here everything is fucking bad except for the css

[cn1t]

The other impl is straight up bad code nobody understands it. It's just the CSS which needs to be improved in the other one. Here everything is fucking bad except for the css

nuh uh

[9glenda]

I'm against merging it but yeah