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

[ui_next] Datetime component does not load in Firefox #9871

Closed
unlikelyzero opened this issue Apr 9, 2021 · 5 comments
Closed

[ui_next] Datetime component does not load in Firefox #9871

unlikelyzero opened this issue Apr 9, 2021 · 5 comments
Assignees

Comments

@unlikelyzero
Copy link

ISSUE TYPE
  • Bug Report
SUMMARY

Datetime component does not load in Firefox

ENVIRONMENT
  • AWX version:04/09/21
  • AWX install method: yolo and docker
  • Ansible version: X.Y.Z
  • Operating System: macOS
  • Web Browser: Firefox ESR (maybe more recent versions, too)
STEPS TO REPRODUCE
  1. Edit a schedule
  2. Click on datetime field
EXPECTED RESULTS

HTML datetime picker to load

ACTUAL RESULTS

😭

ADDITIONAL INFORMATION

Screen Shot 2021-04-09 at 5 22 24 PM

@jakemcdermott
Copy link
Contributor

Just reproduced this on non-esr as well

@unlikelyzero
Copy link
Author

To the interested QE member who picks this up for needs_test: Cypress doesn't allow for testing the HTML native datetime picker so this will have to be stubbed until the patternfly implementation lands

@jakemcdermott
Copy link
Contributor

Note: Will need to double-check on the status of the related patternfly component

@jakemcdermott
Copy link
Contributor

I'm removing the waiting_for_pf label - I think we may just need to use the pf-react datepicker component.

@keithjgrant noticed that we're still using a raw input field in parts of the schedule component, so it may just be that we need to replace it with the pf-react component.

@mabashian
Copy link
Member

Fixed by #10291

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants