-
-
Notifications
You must be signed in to change notification settings - Fork 9k
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
[JENKINS-69787] Create new dismiss component #7265
base: master
Are you sure you want to change the base?
Conversation
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.
When you have more than one dismiss button on the form, this can be used to determine | ||
which button is pressed, as the server will get a parameter by this name. | ||
</s:attribute> | ||
<s:attribute name="tooltip" use="required"> |
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.
Needs to specify the expectation around HTML content.
Thanks everyone for the reviews. Ill fix the leftovers within the next week when I hopefully have time |
Please take a moment and address the merge conflicts of your pull request. Thanks! |
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.
Noting the requirement of #7265 (review)
Hey @CrystallDEV, would you mind addressing the outlined feedback above, please? Thanks in advance! |
@NotMyFault @daniel-beck @uhafner I finally managed to find time and motivation to fix the PR. Looks good on my machine 😄 |
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.
Thanks for addressing most of the feedback! Can you please also update the screenshots in the PR description?
which button is pressed, as the server will get a parameter by this name. | ||
</s:attribute> | ||
<s:attribute name="value"> | ||
The tooltip text of the dismiss button. |
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.
Make clear that HTML is not allowed in tooltip.
</s:documentation> | ||
<button | ||
name="${attrs.name ?: 'Dismiss'}" | ||
tooltip="${attrs.value ?: '%Dismiss'}" |
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.
Wouldn't it make more sense to have no tooltip if not given? It would not help if it is the same as the name. (If not you should at least make it consistent to the name). Is the %
a typo?
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.
% is for internationalization
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.
Then it should be in name as well?
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.
name is used as part of form submission so definitely should not change in different locales. tooltip is what's displayed to users (although as you said should probably be omitted if it's the same as attrs.value
as it provides no value)
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.
So anything I should 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.
Probably should remove the tooltip I think. Or make it customise-able without also changing value.
e.g.
tooltip="${attrs.tooltip}"
I think would work
Updated Screenshot |
Please take a moment and address the merge conflicts of your pull request. Thanks! |
…in messages
See JENKINS-69787.
Testing done

- Executed all existing testsProposed 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
N/A
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).