Smart GWT Portlets and Classic CSS

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 6.0.6 GA
• Fix Version/s: 6.0.6 GA
• Component/s: UI > JavaScript & CSS
• Labels:
  • CSS
  • Portlet
  • SmartGWT
  • conflict
• Environment: Windows XP, Liferay 6.0.6 bundled with tomcat 6.0.29
• Similar Issues: Show 5 results ; ;

  LPS-911	create a portlet using gwt 1.5 (best using smartgwt)
  LPS-913	create a portlet using gwt 1.5 (best using smartgwt
  LPS-25683	Update Classic Theme CSS to use SASS
  LPS-7526	Hudcrumb styling should be in Classic custom css
  LPS-15450	Portlet CSS

Smart GWT based portlets, are not being correctly shown in the Liferay Portal.

Smart GWT applications, have a "pixel-perfect" approach, and so, they can't allow external CSS styling interfering with them.

All the CSS from Smart GWT are based in the .class approach. And that create some conflicts with the portal theme CSS definitions.

A clearly example is the base.css (classic theme) where we have padding and margin styling in basics elements (such as, TD, TR, DIV, TABLE, etc).

The solution here, is to find a way to allow the CSS Portlet rules to have a high priority over the theme ones (maybe an option ?). Let me state than the SmartGWT CSS are loading by the JavaScript application itself.

Quote from SmartGWT :

"I'm seeing visual glitches like unnecessary scrollbars, gaps in headers or misplaced elements :

You have external CSS in your project that is styling the basic browser elements (e.g. TD, TH,
etc) which will interfere with pixel-perfect layout facilities provided by Smart GWT (or any
similar system)."

[Jean-Michel Garcia]

Someone ?

[Mika Koivisto]

If your portlet creates restrictions on the theme then you need to create a theme that respects those restrictions. The classic theme is just a sample theme and if you need a theme without any styling then you should create one based on _unstyled. It is literally unstyled so it might not look pretty.

[Edward Gonzales]

Hello everyone! We are in the process of removing component "Portlet" from LPS. Please replace this issue's component, "Portlet", with a new component. There are over 200+ components, in the newly organized component list. Also, make the necessary adjustments to affected filters. Thanks!