Ingress Rules tab misbehaving with enter key #13147
Labels
kind/bug
QA/dev-automation
Issues that engineers have written automation around so QA doesn't have look at this
Setup
Describe the bug
On the
create
screen foringresses
-rules
tab - if the user focuses on therequest host
and presses theenter
key, a row for rules path disappears. If you focus again on that same input and pressenter
it appears againTo Reproduce
On the
create
screen foringresses
-rules
tab - if the user focuses on therequest host
and presses theenter
key, a row for rules path disappears. If you focus again on that same input and pressenter
it appears againResult
adds/removes a rules
path
rowExpected Result
should not have any implication with the rules
path
rowsScreenshots
Screen.Recording.2025-01-17.at.16.45.08.mov
Additional context
If you console.log on this method in
RulePath
https://github.com/rancher/dashboard/blob/master/shell/edit/networking.k8s.io.ingress/RulePath.vue#L102-L105 you'll see that theenter
key press triggers this method on the@click
.Same for when it's adding a new row via the weird
enter
behaviour, this method on@click
triggers https://github.com/rancher/dashboard/blob/master/shell/edit/networking.k8s.io.ingress/Rule.vue#L167-L173All evidence points to some weird propagation of events, since both those elements are
button
elements and those captureenter
keypresses.TBD how is this being exactly propagated and what is the correct fix. Smoking gun is that if you replace those
button
elements forspan
with the same@click
handlers the bug disappearsThe text was updated successfully, but these errors were encountered: