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

Fixes #38196 - Remove use of $.removeAttr from Katello #11304

Merged
merged 1 commit into from
Feb 11, 2025

Conversation

jeremylenz
Copy link
Member

What are the changes introduced in this pull request?

Because of this breaking change in jQuery 3.0, the 'Select None' button on the Sync Status page had stopped working. This change should make it work again.

Considerations taken when implementing this change?

The solution is to replace removeAttr() with .prop(attrName, value). I found several other instances of its use, which I also updated. There were a few where I'm not sure false is the correct value, but I don't know if that will matter..

What are the testing steps for this pull request?

Reproduce the issue:
Make sure your Foreman is up to date with latest develop and Katello is latest master
Run npm i

Fix the issue:
Check out this PR
check Sync Status page Select None button, make sure it works
Check other Angular pages and make sure I didn't break anything

@jeremylenz
Copy link
Member Author

@sjha4 Restored those 3 files. 👍

Copy link
Member

@sjha4 sjha4 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Won't experiment with other files here..Some are dead code, the files in 'app/assets/javascripts/katello/widgets/' for example..Deleting others caused weirdness in my console although the UI seemed to be working alright. Fine to leave them alone with the jquery fix.
Ack 👍🏼

@jeremylenz jeremylenz merged commit 0b6754e into Katello:master Feb 11, 2025
19 checks passed
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