Can't edit firewall rules in Chrome/MSEdge?

[pyrodex]

So I just tried to clone, edit, save an existing firewall rule and I've done this hundreds of times before 25.1 upgrade but in Chrome I couldn't hit the save button. Nothing happened so I tried MSEdge, same process nothing happened. I tried creating a new rule in both browsers and had no luck even with new rule creation but then I floated over to Firefox and it worked as expected. All three browsers are running the latest and greatest versions in Windows. Is this a bug or something else?

[EricPerl]

No issue with WIN10. I just rebooted my dual-boot Ubuntu+WIN10 test box and tried with Edge.
Clone, change name, save, apply, delete, apply.
Same with new rule.

Try in private mode?

[BombusAlpinus]

same here, opnsense 25.1,  rule creation/editing works in firefox but not in chrome.
clearing chrome browser cache and cookies didn't solve the issue.

[BombusAlpinus]

same here, opnsense 25.1,  rule creation/editing works in firefox but not in chrome.
clearing chrome browser cache and cookies didn't solve the issue.

tried a different system also with chrome where the editing of an existing rule worked... strange...

[lanrat]

I'm also having this issue. Chrome gives the following error in the console, so I think it may be due to a malformed select tag.

Code Select Expand

Form submission failed, as the <SELECT> element named '' was implicitly closed by reaching the end of the file. Please add an explicit end tag ('</SELECT>')
This is likely the same issue here: https://forum.opnsense.org/index.php?topic=45675.0

[pyrodex]

Is there a chance we could get an interim patch to fix the broken browsers? I am more than willing to collect data needed as I can reproduce this.

[brett.merrick]

This seems to be related to having experimental features enabled in chrome or its derivatives.

Go to

Code Select Expand

chrome://flags/#enable-experimental-web-platform-features and click Disable.

[lanrat]

This seems to be related to having experimental features enabled in chrome or its derivatives.

Go to

Code Select Expand

chrome://flags/#enable-experimental-web-platform-features and click Disable.

That fixed it for me. Thanks!

[momotombo]

Started running into this issue right after I upgraded: 25.1.4_1 -> 25.1.5_5.

Worked around it by using firefox, but can also confirm it started working in chrome after disabling chrome://flags/#enable-experimental-web-platform-features

For what it's worth, I dug a bit into the HTML and it seems to be the dropdown plugin that's misbehaving when creating the dom element, instead of it being an actual HTML syntax error..

[Patrick M. Hausen]

Why would anyone enable "experimental web platform features"? Don't tell me that's (enabled) the default? Wiiilmaaa ...!

[momotombo]

It's not on by default. I'm a web developer so I enable that every once in a while to test out new features. Admittedly though, it should disable itself automatically after X amount of time, I didn't even remember I had it on.