Move `.js-epic-container` class to fix E2E spec
requested to merge 283932-flaky-test-qa-specs-features-ee-browser_ui-2_plan-epic-epics_management_spec-rb-39-plan into master
What does this MR do?
Related to #283932 (closed)
The way the @content_class variable was being set was causing issues when alerts were shown on the page. This MR removes the .js-epic-container class from @content_class and puts it on a container that is specific to the Epic view.
See #283932 (comment 460027737) for more context
Screenshots (strongly suggested)
| Page | Before | After |
|---|---|---|
| "Epics and Issues" tab |  |
 |
| "Roadmap" tab |  |
 |
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry - [-] Documentation (if required)
-
Code review guidelines -
Merge request performance guidelines -
Style guides - [-] Database guides
-
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers - [-] Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
- [-] Label as security and @ mention
@gitlab-com/gl-security/appsec - [-] The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
- [-] Security reports checked/validated by a reviewer from the AppSec team
Edited by Peter Hegman