Bug 806353 – Sync Plans: Manually entering a time can cause time selector to get stuck on screen

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 806353 - Sync Plans: Manually entering a time can cause time selector to get stuck on screen

Summary:	Sync Plans: Manually entering a time can cause time selector to get stuck on ...

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Satellite 6
Classification:	Red Hat
Component:	WebUI (Show other bugs)
Sub Component:
Version:	6.0.1
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified (vote)
Target Milestone:	Unspecified
Target Release:	Unused
Assigned To:	Eric Helms
QA Contact:	Corey Welton
Docs Contact:

URL:
Whiteboard:
Keywords:	Triaged, ZStream

Depends On:
Blocks:	826629
	Show dependency tree / graph

Reported:	2012-03-23 10:20 EDT by Corey Welton
Modified:	2013-08-16 14:11 EDT (History)
CC List:	7 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:	The timepickr plugin initialized after every access of the time selector widget. As a result, the Sync Plans' time selector widget remains in place after time selection. This obscures the "Save" button. This fix corrects the timepickr behavior. The widget no longer remains on the page after time selection.
Story Points:	---
Clone Of:
Clones:	826629 (view as bug list)
Environment:
Last Closed:	2012-12-04 14:43:43 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
screenshot (17.89 KB, image/png) 2012-03-23 10:23 EDT, Corey Welton	no flags	Details
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2012:1543	normal	SHIPPED_LIVE	Important: CloudForms System Engine 1.1 update	2012-12-04 19:39:57 EST

Groups: None (edit)

Description Corey Welton 2012-03-23 10:20:42 EDT

Description of problem:
If a user is creating a sync plan, manually enters a time/makes modifications to the value of the "Time" field, and subsequently tries to use the selector tool, the tool itself gets stuck on the screen and does not go away. In addition to being kind of ugly, it obscures the submit button so user cannot submit his sync plan.

I saw this a very long time ago but could not get a 100% repro case. Now it seems to do it every time (Chrome, Firefox)

Version-Release number of selected component (if applicable):


How reproducible:
Seems to be every time but I'm not sure

Steps to Reproduce:
1.  Content Management > Sync Management > Sync plans> +New Plan
2.  Enter name of "asdf"
3.  In the "Time" field, MANUALLY modify the time to something other than $current_time -- like 1 hour ahead or something - and subsequently hover atop the time select tool.
4. Select hours/minutes/AM|PM in the widget and move mouse away.
  
Actual results:
Selector widget does not disappear; user cannot hit the submit button.

Expected results:
Field gets populated, widget disappears

Additional info:

Comment 1 Corey Welton 2012-03-23 10:21:19 EDT

Workaround is to, of course, re-start the steps of creating a new sync plan

Comment 2 Corey Welton 2012-03-23 10:23:09 EDT

Created attachment 572291 [details]
screenshot

Comment 3 Eric Helms 2012-05-22 16:24:37 EDT

This bug was a result of the timepickr jQuery plugin being initialized every time the input field was accessed.  This has been fixed as per the commit below:

https://github.com/Katello/katello/pull/135

Comment 7 Corey Welton 2012-09-20 18:37:12 EDT

QE Verified.

CloudForms System Engine Version: 1.1.12-7.el6cf

Comment 9 errata-xmlrpc 2012-12-04 14:43:43 EST

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.

http://rhn.redhat.com/errata/RHSA-2012-1543.html

Comment 10 Mike McCune 2013-08-16 14:11:31 EDT

getting rid of 6.0.0 version since that doesn't exist

Note You need to log in before you can comment on or make changes to this bug.