-
-
Notifications
You must be signed in to change notification settings - Fork 8.6k
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
Revamp icon legend as a modal #7718
Revamp icon legend as a modal #7718
Conversation
There is an overlay (it darkens the page)
That makes sense to me, especially for a simple modal like this.
👍 Just opened a PR for dark theme jenkinsci/dark-theme-plugin#338 Thanks! |
The overlay only works on safari, doesn't work on Firefox or Chrome |
Hadn't spotted that, thanks - opened a new dark theme PR to address janfaracik/dark-theme-plugin#44 |
That’s been opened against your fork not the origin |
Whoops, opened it again jenkinsci/dark-theme-plugin#339 |
remove: function(element) { | ||
element = $(element); | ||
element.parentNode.removeChild(element); | ||
return element; | ||
}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why was this removed? it's what is causing the ATH failures.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It was interfering with the removal of the modal (I'm assuming because the modal doesn't have a parent?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do we still need to remove this function now that you've changed the core components to not use it?
https://github.com/search?q=org%3Ajenkinsci+Element.remove%28+language%3AJavaScript&type=code&l=JavaScript&p=1
It looks like it should be okay to remove.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(Accidentally resolved this in case you missed it)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If I'm understanding correctly, we still need to remove the function as it interferes with removing the modal.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tested locally and it seems to be working fine? not sure how it could be causing an issue if nothing is calling it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
weird I get that error in Safari but not chrome...
Maybe it has a parent in chrome, I guess we already hit a browser difference with this functionality.
ATH passed: jenkinsci/acceptance-test-harness#1062 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A very welcoming change :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested manually on FF, Chrome and Safari, seems to behave as expected.
Security-wise looks good to me too.
/label ready-for-merge This PR is now ready for merge, after ~24 hours, we will merge it if there's no negative feedback. Thanks! |
Please take a moment and address the merge conflicts of your pull request. Thanks! |
</l:main-panel> | ||
</l:layout> | ||
<j:jelly xmlns:j="jelly:core" xmlns:l="/lib/layout"> | ||
<h1 class="jenkins-modal__title">${%Icon legend}</h1> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since this is no longer a standalone view, attempts to access the URL /legend
(e.g. from links in outside documentation, or browser history) will result in the logging of the message
Mar 17, 2023 5:00:06 PM WARNING jenkins.security.stapler.StaplerFilteredActionListener onDispatchTrigger
New Stapler dispatch rules result in the URL "/legend" no longer being allowed. If you consider it safe to use, add the following to the whitelist: "hudson.model.Hudson legend". Learn more: https://www.jenkins.io/redirect/stapler-facet-restrictions
This seems unnecessary. Perhaps rename the view to _legend
so it's a simple 404?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Relates to https://issues.jenkins.io/browse/JENKINS-68357
Testing done
Proposed changelog entries
Proposed upgrade guidelines
N/A
Submitter checklist
@Restricted
or have@since TODO
Javadocs, as appropriate.@Deprecated(since = "TODO")
or@Deprecated(forRemoval = true, since = "TODO")
, if applicable.eval
to ease future introduction of Content Security Policy (CSP) directives (see documentation).Desired reviewers
@jenkinsci/sig-ux
Maintainer checklist
Before the changes are marked as
ready-for-merge
:upgrade-guide-needed
label is set and there is a Proposed upgrade guidelines section in the pull request title (see example).lts-candidate
to be considered (see query).