Timestrip View doesn't display Plans properly

[charlesh88]

Summary

Title says it all. Have a look:

This is probably due to a broken CSS selector stemming from updated markup. @shefalijoshi I'll take a look first and ping you if it's something I can't figure out.

Expected vs Current Behavior

Title says it all.

Impact Check List

• Data loss or misrepresented data?
• Regression? Did this used to work or has it always been broken?
• Is there a workaround available?
• Does this impact a critical component?
• Is this just a visual bug with no functional impact?

Steps to Reproduce

1. Add a plan from the tree to a Timestrip view.
2. Observe that the result is the same as the screenshot at the top of this issue.

Environment

• Open MCT Version: 1.8.3 / 1.8.4
• Deployment Type: /stable /testathon
• OS: Mac
• Browser: Chrome

Additional Information

[charlesh88]

Problem found, but solution not yet clear. Sometime after 1.8.2, we changed the strategy behind how Plans are added to Timestrips in a way that kills the grid layout:

What we need to do is

1. Know when a Plan is inside c-object-view and
2. Write CSS that selects appropriately for that.

[charlesh88]

Testing Instructions

1. Create or edit a Timestrip view.
2. Add a Plan view to the Timestrip view. Add another object view like a telemetry point or Sine Wave Generator.
3. Verify the Plan does NOT appear as the first screenshot in this issue, but instead looks something like this:

or this

4. Check for regressions: click the Plan view itself in the tree, and verify it looks something like this:

[shefalijoshi]

Verified fixed