Details
-
Type:
Task
-
Status:
Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 6.0.6 GA
-
Fix Version/s: --Sprint 12/11, 6.1.0 CE RC1
-
Component/s: UI > JavaScript & CSS
-
Labels:None
-
Similar Issues:
Description
Related to http://issues.liferay.com/browse/AUI-402:
Currently, using the classNamePrefix property in Alloy prevents us from using core YUI modules, as well as modules from the gallery.
The reason for this is because while the javascript will write out markup like this:
<div class="aui-slider"></div>
The css still references .yui3-slider.
The only workable fix long term is to rename our CSS classes from .aui-* to .yui3-aui- to not only go along with the grain of existing css classes, but do so in a way that prevents collision with other modules.
So css classes like yui3-widget will still exist (since that is a YUI css class), but our widgets, like Dialog, TreeView, AutComplete, etc, will have:
.yui3-aui-* in front of them, like so: .yui3-aui-dialog, .yui3-aui-treeview, etc.
Issue Links
- is related to
-
AUI-402
Convert Alloy css classnames to YUI3 classnames
-

I'm making one last change for this:
We're going to keep all YUI widgets as "yui3-" so that all YUI components will still work.
But instead of having aui widgets be "yui3-aui-", we're instead going to be using "aui-" as the prefix.
This means that QA's test scripts will have to change (sorry guys), but it's a very simple find/replace:
find: yui3-aui-
replace: aui-
Of course, let me know if there's anything I can do to help make the transition easier.