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

Input field for the time in datetime picker is disabled #15695

Closed
NikhilNagdev opened this issue Dec 24, 2019 · 6 comments
Closed

Input field for the time in datetime picker is disabled #15695

NikhilNagdev opened this issue Dec 24, 2019 · 6 comments
Assignees
Labels
Bug A problem or regression with an existing feature has-pr An issue that has a pull request pending that may fix this issue. The pull request may be incomplete ui Issues relating to the user interface
Projects
Milestone

Comments

@NikhilNagdev
Copy link
Contributor

Describe the bug

When we click on the calendar button to insert timestamp for a column in the insert tab the input field for time is disabled, whereas while editing a timestamp value from browse tab the input field is not disabled.

To Reproduce

Steps to reproduce the behavior:

  1. Create a column in a table with type TIMESTAMP.
  2. Go in insert tab and click on the calendar button near the input field of that column.
  3. You will see that the input filed for time is disabled.

Expected behavior

The input field for time must not be disabled.

Screenshots

In insert tab

insert_timestamp_issue

In browse tab

issue_timestamp

@williamdes
Copy link
Member

@NikhilNagdev #15685 ?

@williamdes williamdes added Bug A problem or regression with an existing feature ui Issues relating to the user interface labels Dec 24, 2019
@williamdes williamdes added this to Needs triage in issues via automation Dec 24, 2019
@NikhilNagdev
Copy link
Contributor Author

Sorry i didn't get you

@williamdes williamdes moved this from Needs triage to to be fixed soon in issues Dec 24, 2019
@williamdes
Copy link
Member

williamdes commented Dec 24, 2019

Sorry, I was thinking that It was solved by your PR that I just merged

@NikhilNagdev
Copy link
Contributor Author

Ohh it's okay :)

@yashrajbothra
Copy link
Contributor

are you working on this @NikhilNagdev

@NikhilNagdev
Copy link
Contributor Author

No.
You can find a solution for this @yashrajbothra786

yashrajbothra added a commit to yashrajbothra/phpmyadmin that referenced this issue Dec 26, 2019
Signed-off-by: Yash Bothra <yashrajbothra786@gmail.com>
yashrajbothra added a commit to yashrajbothra/phpmyadmin that referenced this issue Dec 26, 2019
Signed-off-by: Yash Bothra <yashrajbothra786@gmail.com>
yashrajbothra added a commit to yashrajbothra/phpmyadmin that referenced this issue Dec 26, 2019
Signed-off-by: Yash Bothra <yashrajbothra786@gmail.com>
yashrajbothra added a commit to yashrajbothra/phpmyadmin that referenced this issue Dec 26, 2019
Signed-off-by: Yash Bothra <yashrajbothra786@gmail.com>
@williamdes williamdes self-assigned this Dec 26, 2019
@williamdes williamdes added this to the 4.9.3 milestone Dec 26, 2019
williamdes added a commit that referenced this issue Dec 26, 2019
Signed-off-by: William Desportes <williamdes@wdes.fr>
@williamdes williamdes added the has-pr An issue that has a pull request pending that may fix this issue. The pull request may be incomplete label Dec 26, 2019
issues automation moved this from to be fixed soon to Closed Dec 26, 2019
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 26, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Bug A problem or regression with an existing feature has-pr An issue that has a pull request pending that may fix this issue. The pull request may be incomplete ui Issues relating to the user interface
Projects
issues
  
Closed
Development

No branches or pull requests

3 participants