Sticky drawer

2. Requesting enhancements

• Describe the use cases and requirements of the new feature or enhancement you are requesting.
  Use case: As A customer I want to see a list of recommendations in the table, I want to view the detail of different recommendations and decide which one is worth action. On a high level, for MVP we do not provide any "label" or anything that would tell the customer the "priority" or "severity" of the recommendation.
  I would like to provide a sticky drawer for customers so that they can scroll on the table as well as have recommendations open.

• Explain why this feature is needed and/or why these requirements cannot be met using existing components.
  The current Drawer is not sticky. We don't have enough data to build a whole new page for a detail of recommendation and a modal option feels weird to me like it disrupts the context. (I could be wrong but I don't think it's suitable for this use case)

• If this is for specific applications, list them here along with any dates that you need this for.
  Resource optimization for OpenShift. Before summit.

• Link any detailed design documents, rough sketches, wireframes, or workflows.
  https://www.sketch.com/s/c1987a7a-9bf0-432a-a31f-ff05976ffec7/a/eKPj74p

• State whether this is a new feature or an enhancement of an existing pattern by labeling it accordingly
  This is an enhancement. The notification service has a sticky drawer.

• If this is an enhancement to an existing feature, identify the feature that you want to modify.
  When the customer scrolls the page, the drawer stays still.
  (Sorry for the poor description, I am doing this a second time)

Jira Issue: PF-2141

Start by examining the existing Drawer and the notification service's sticky drawer, then review the linked Sketch design and Jira issue PF-2141 for requirements. Confirm how the Drawer behaves while the page scrolls and compare it with the existing sticky pattern. Done means customers can scroll the recommendations table while the open recommendation drawer remains fixed without losing context.