Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

~Fix move confirmation set to 0 when changing other pref - Fixes #13244 #13250

Closed

Conversation

TheMadSword
Copy link
Contributor

No description provided.

@ornicar
Copy link
Collaborator

ornicar commented Jul 20, 2023

this just undoes the fix to that issue and will restore a previous bug.

Please use git blame to see why things are how they are

@ornicar ornicar closed this Jul 20, 2023
@TheMadSword
Copy link
Contributor Author

TheMadSword commented Jul 20, 2023

Was fixed via e7f091d instead.

My commit didn't reintroduce the bug, as I tested before and after, nor was an "undo" (if you compare both commits, one doesn't simply undo the other). Your previous commit added a reference to "data-name" attribute which was missing.

I didn't know that I had to add "data-name" instead of simply re-adding "name".

@ornicar
Copy link
Collaborator

ornicar commented Jul 20, 2023

the name attribute was causing a bug, as the hidden field has the same attribute. That's why I changed to data-name but failed to commit the change in the scala template

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants