Red Hat Bugzilla – Bug 1470976
Edit Autoscaler page does not show scale up/down button in the input fields in iPad Pro & iPhone Safari.
Last modified: 2017-11-28 17:01:28 EST
Description of problem: Edit Autoscaler page does not show scale up/down button in the input fields in iPad Pro & iPhone Safari. Version-Release number of selected component (if applicable): openshift v3.6.144 kubernetes v1.6.1+5115d708d7 How reproducible: Always Steps to Reproduce: 1.Create rc $ oc run myrun-rc --image=yapei/hello-openshift --generator=run-controller/v1 2.Create HPA from the replication controller page Add name,Min replicas(2),Max replicas(10),Target CPU Utilization Actual results: 2.no show scale up/dwon button at end of input fields Expected results: 2.Should show sacle up/down button Additional info:
https://github.com/openshift/origin-web-console/pull/1847
Commit pushed to master at https://github.com/openshift/origin-web-console https://github.com/openshift/origin-web-console/commit/59d62673976b2a0ed523ae2b78baca89e41c98a8 Bug 1470976 - Support number input on iOS For the iOS keyboard to prompt for numbers, the inputs must have a `pattern` attribute of digits. Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1470976
Checked on 3.7.0-0.147.0, only issue on iPhone is fixed. Still reproduces on iPad. The full keyboard rather than the number input was used on iPad.
Created attachment 1338165 [details] iphone is fixed as expected
According to Comment 1, this is fixed on ipad and iPhone, please see the screenshot. Verified on OpenShift v3.7.0-0.147.1
> Still reproduces on iPad. The full keyboard rather than the number input was used on iPad. The iPad doesn't have a number-only keyboard, so this is expected. The change should affect the iPhone. It's working as intended.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2017:3188