You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[JENKINS-36539] OK button disabled if project type chosen first #17316
Hey, I believe I have a potential fix for this. However, I'm still new to the Jenkins community, and I believe I need to submit an individual CLA. After that, I will test my changes a bit more, and then submit a pull request. Thank you.
Hey, I believe I have a potential fix for this. However, I'm still new to the Jenkins community, and I believe I need to submit an individual CLA. After that, I will test my changes a bit more, and then submit a pull request. Thank you.
I could not reproduce the issue described here by using Jenkins 2.19.3, the previous version where the fix was delivered.
Steps
Click on New item option
Click on Pipeline job / project
Enter the a name for this new job
Change the focus from the form field
The submit button is enable
This introduces a clear regression related with the keyboard navigation. I was working on it during several days: PR-2250. I invite you to watch the screencast provided there.
I could not reproduce the issue described here by using Jenkins 2.19.3, the previous version where the fix was delivered.
Steps
Click on New item option
Click on Pipeline job / project
Enter the a name for this new job
Change the focus from the form field
The submit button is enable
This introduces a clear regression related with the keyboard navigation. I was working on it during several days: PR-2250. I invite you to watch the screencast provided there.
Activity
jenkins-infra-bot commentedon Jul 31, 2016
Raw content of original comment:
Hey, I believe I have a potential fix for this. However, I'm still new to the Jenkins community, and I believe I need to submit an individual CLA. After that, I will test my changes a bit more, and then submit a pull request. Thank you.
jenkins-infra-bot commentedon Nov 8, 2016
Raw content of original comment:
Fixed in 2.23 (fbb4dc0).
jenkins-infra-bot commentedon Nov 8, 2016
Raw content of original comment:
Code changed in jenkins
User: Jonathan Fuentes
Path:
war/src/main/js/add-item.js
http://jenkins-ci.org/commit/jenkins/7e8ea4a967057c3fc9ae4dc72028f780d9fa39e1
Log:
[FIXED JENKINS-36539] (#2495)
(cherry picked from commit fbb4dc0)
jenkins-infra-bot commentedon Dec 9, 2016
Raw content of original comment:
This kind of issues should provide information about the web browser.
jenkins-infra-bot commentedon Dec 9, 2016
Raw content of original comment:
I could not reproduce the issue described here by using Jenkins 2.19.3, the previous version where the fix was delivered.
Steps
This introduces a clear regression related with the keyboard navigation. I was working on it during several days: PR-2250. I invite you to watch the screencast provided there.
jenkins-infra-bot commentedon Dec 9, 2016
Raw content of original comment:
What is that regression? Is it filed in JIRA with the regression keyword and marked as blocking this issue?
jenkins-infra-bot commentedon Dec 12, 2016
Raw content of original comment:
jglick, the keyboard navigation does not work as I proposed. There is no a JIRA issue for that. I hope to file it.