Details
-
Type: Improvement
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 3.0
-
Fix Version/s: 3.0.1, EE-3.0.0.GA
-
Component/s: ACE-Components
-
Labels:None
-
Environment:Portlets, Liferay 5
-
Affects:Documentation (User Guide, Ref. Guide, etc.)
Description
After solving the problems reported in ICE-7717, there were still some styling issues in some ACE components. The Liferay 5 UI was also affected, specifically in the Add Application menu. Further debugging revealed that the presence of combined.css, in particular the contents of jquery-ui.css were causing these issues.
Activity
Arturo Zambrano
created issue -
Arturo Zambrano
made changes -
Field | Original Value | New Value |
---|---|---|
Assignee | Arturo Zambrano [ artzambrano ] |
Ken Fyten
made changes -
Salesforce Case | [] | |
Fix Version/s | 3.0.1 [ 10282 ] |
Ken Fyten
made changes -
Salesforce Case | [] | |
Assignee Priority | P2 |
Ken Fyten
made changes -
Salesforce Case | [] | |
Assignee Priority | P2 | P3 |
Arturo Zambrano
made changes -
Status | Open [ 1 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Ken Fyten
made changes -
Resolution | Fixed [ 1 ] | |
Status | Resolved [ 5 ] | Reopened [ 4 ] |
Arturo Zambrano
made changes -
Status | Reopened [ 4 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Ken Fyten
made changes -
Comment |
[ If a subtree render is invoked via f:ajax, the DOM subtree will be looked up by client ID, so the clientID on the containing element of the component must be exactly the client ID of the component. ] |
Ken Fyten
made changes -
Resolution | Fixed [ 1 ] | |
Status | Resolved [ 5 ] | Reopened [ 4 ] |
Affects | [Documentation (User Guide, Ref. Guide, etc.)] |
Arturo Zambrano
made changes -
Status | Reopened [ 4 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Ken Fyten
made changes -
Fix Version/s | EE-3.0.0.GA [ 10262 ] |
Ken Fyten
made changes -
Summary | ACE components styling issues in Liferay 5 | Find Workaround for ACE Component styling issues in Liferay 5 |
Issue Type | Bug [ 1 ] | Improvement [ 4 ] |
Salesforce Case | [] |
Ken Fyten
made changes -
Status | Resolved [ 5 ] | Closed [ 6 ] |
Assignee Priority | P3 |
The specific styling issues are the following:
Unfortunately, Liferay 5 also uses the same jQuery UI convention we use of CSS class names in various parts of its UI, without taking measures to avoid affecting other content on the page that uses the same CSS class name patterns. This means that in our case, there are two sets of styling rules that are applied to the components mentioned above. Whichever set of rules that is loaded last (usually Liferay's) is the one being applied on the page. If somehow we managed to load our styling rules last, then we would be affecting the Liferay UI. So, this is a logical contradiction and there can't be a proper fix for this situation.
However, it is possible to come up with a workaround, which would consist in wrapping our components/portlets in a container <div> and add a class name to it (let's say 'ace'), so that we can define an additional set of rules which will only be applied to elements preceded by the 'ace' class name. This set of rules would most likely be defined in a <style> element somewhere on the page and will try to undo the styling from Liferay in the ace components.