leadermontanus
commented
6 years ago Suggested solutions
-
Separate out 100% all styles that are NOT used on the Mlab editor page.
- Keep in a single separate file
- No need for Mlab prefix
- Don't reuse/reference in any way in Mlab editor/components stylesheets
-
(Try to) never use !important inside Mlab editor styling. This should be left as a standard way for components to ensure that they look correctly without having to know about all other components.
-
Don't use any #mlab_editor
-
Don't style HTML elements in the editor interface outside the editing rectangle using #mlab_editor selector. Instead use the DIVs IDs or classes for the different areas of the page.
-
Don't style generic HTML elements in the editor interface. I.e. don't use
span, instead use.my_span_class -
Use same paths for design time and runtime styling, in other words do not refer to
#mlab_editor .xxxand.mlab_main_body_contentfor components. Instead just use .mlab_main_body_content which is present both in runtime and design time. -
Create a separate namespace for dialog boxes (qtip2). Here, in contravention of the points above, I suggest that we use a namespace path that is
#mlab_editor .qtip_class ELEMENTS.This would take it out of the remaining namespaces and avoid clashes with others without having a too long name path.
TIMER HV
=63 timer
HV requires a template, need to find someone to do it and then implement it.
Youtube, video and upload media has ccs in mlab_component_config.css - should be placed under the component
upload media - add classes to the html code - and add the css there instead of overwriting css classes... same for youtube and maybe others.
Think all dialog box styling needs to move into it's own namespace, for instance mlab_dt_dlg rather than (for example) mlab_dt_label.
The mlab_all.css and maybe others are too long and needs to be split up.