Bug 791345 - Sync Plans: Plan highlight looks strange after editing plan
Summary: Sync Plans: Plan highlight looks strange after editing plan
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: WebUI
Version: 6.0.1
Hardware: Unspecified
OS: Unspecified
unspecified
low vote
Target Milestone: Unspecified
Assignee: Eric Helms
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-16 19:57 UTC by Corey Welton
Modified: 2019-09-26 13:30 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-19 18:14:03 UTC
Target Upstream Version:


Attachments (Terms of Use)
screenshot snippet (12.49 KB, image/png)
2012-02-16 20:02 UTC, Corey Welton
no flags Details

Description Corey Welton 2012-02-16 19:57:29 UTC
Description of problem:
Minor, but odd-looking issue.

If a user creates a new sync plan and then edits it, highlighting that plan in the future shows a strange block extending from the bottom of the highlight.

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


How reproducible:


Steps to Reproduce:

Prerequisite: Assure you have no existing sync plans, as this only seems to happen on the first one (?).

1. Go to Content Management > Sync Management > Sync Plans
2. +New Plan
   Name = 'Google'
   Interval = None [leave as is - don't change]
   Start Date = $current_date
   Time = whatever you want
3. Click on 'Google' in Sync Plans
4. Edit plan 
   Change Interval to Daily
5. Click on 'Google' in Sync Plans
  
Actual results:

A little blob extending beyond the bottom of the div (see forthcoming screenshot)

Expected results:
Clean highlight

Additional info:

* I don't think this happens if more than one sync plan exists or is created. Or possibly they get hidden by the sync plans below them.
* Chrome and Firefox
* I don't think this is a serious issue beyond anything cosmetic, but who knows.

Comment 1 Corey Welton 2012-02-16 20:02:11 UTC
Created attachment 562582 [details]
screenshot snippet

Comment 2 Eric Helms 2012-12-18 21:04:01 UTC
Upstream - https://github.com/Katello/katello/pull/1309

Comment 3 Eric Helms 2012-12-19 01:20:10 UTC
This has been fixed as of 70c805802693a43635cb73aa8f9bc84790d8a203

Comment 4 Mike McCune 2013-08-16 18:11:45 UTC
getting rid of 6.0.0 version since that doesn't exist

Comment 5 Mike McCune 2013-09-19 18:14:03 UTC
These bugs have been resolved in upstream projects for a period of months so I'm mass-closing them as CLOSED:UPSTREAM.  If this is a mistake feel free to re-open.


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