-
Notifications
You must be signed in to change notification settings - Fork 3
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
Remove display:none for suggetion5 #39
Comments
I've uploaded this change to our current test view in the Sandbox, available here: I think I've gotten the right test case but I'm open to corrections! |
Looks right to me. Production push will be related to https://osticket.library.pitt.edu/scp/tickets.php?id=21796 |
I'll refresh my memory on how we handle deployments, then, and put this into production. This feels like a pretty minor change, so do we need to notify anyone besides the Primo Admins group? |
And should I be updating the change management spreadsheet or are we delegating that to someone else? |
This is tied to change record 271 in the main sheet; but that row represents both this change and the config change in Alma. |
This CSS rule needs to be removed to support modifications to
nui.noresults.suggestions5
.primove-default-view/view/css/custom1.css
Lines 202 to 205 in da84211
The text was updated successfully, but these errors were encountered: