openmct/platform/commonUI
Charles Hacskaylo e8e7067993 Fix legacy messages (#2323)
* Fix legacy message styling

- Code cleanup;
- Enable constants-mobile;
- Add _legacy-messages.scss;
- Add status color fg colors to theme constants;

* CSS refactoring, significant migration for messages classes

- Many messages classes migrated;
- c-click-icon > c-icon-button;
- c-click-icon rewritten;
- __close-btn refined in dialogs;

* About and splash screen styling

- Fixed splash in About screen;

* Update _mixins.scss

* Convert c-overlay__close-button to button

- <a> -> <button>;
- Set color of button;
- Normalized naming from close-btn to close-button;

* Fixed brightness filter issue on elements in overlays in VISTA;

* Fix dismiss button
2019-03-21 15:07:16 -07:00
..
about Build refactor to webpack (#2139) 2018-08-07 14:47:50 -07:00
browse Address testathon issues relating to context menu (#2235) 2018-12-07 10:15:11 -08:00
dialog Fix legacy messages (#2323) 2019-03-21 15:07:16 -07:00
edit remove root from navigation (#2309) 2019-03-18 09:50:23 -07:00
formats Review and integrate Time Conductor Vue style conversion (#2180) 2018-10-02 17:31:45 -07:00
general Fix legacy messages (#2323) 2019-03-21 15:07:16 -07:00
inspect Build refactor to webpack (#2139) 2018-08-07 14:47:50 -07:00
mobile Build refactor to webpack (#2139) 2018-08-07 14:47:50 -07:00
notification Quick compatibility fix to support dismissing notifications from legacy list (#2283) 2019-02-12 11:32:23 -08:00
regions Squashed commit of the following: 2018-08-31 12:03:15 -07:00
README.md [Licenses] Update copyright year to 2017 2017-04-05 14:52:46 -07:00

This directory contains bundles containing common user interface elements of Open MCT; that is, the user interface for the application as a whole (as opposed to for specific features) is implemented here.

Extensions

This bundles adds a stylesheets extension category used to inject CSS from bundles. These extensions are declaration-only (no scripted implementation is needed or used); a single property, stylesheetUrl, should be provided, with a path to the relevant CSS file (including extension) relative to the resources directory for that bundle.

Links to these CSS files are appended to the head when the application is started. These are added in standard priority order (see documentation for the framework layer); the order of inclusion of style sheets can change the way they are handled/understood by the browser, so priority can be used to provide control over this order.