I might be way off here, but is there any reason to extend myTestClass at
all? You can have multiple css classes per element, so simply doing:
ui:style
.myLOCALTestClass{ ...more properties specific for this binder...}
/ui:style
And then assigning both myTestClass and myLOCALTestClass to the
Hi Ryan,
I don't think you're way off, this is definitely a way to do it but there
are a few caveats.
You have to consider that in order to do it this way (assuming you're style
is coming from another cssresource) you would have to:
- declare the cssresource that had the original style via
Seth,
Currently I can do this by setting ui:style
src='relativepath/MyCss.css in A and B and it works nicely, uibinder
takes care of injecting the styles and everything. However I'm not sure if
this is the best way. There's also the issue that if I move A and B then
the relative path
Hi Joseph,
Thanks for the reply. You're right and I actually do this elsewhere
extending cssresource interfaces and using the @shared which also works;
it's definitely the way to go for larger extensions/additions that aren't
as local.
However what I like about the ui:binder approach is you
Hi all,
I have a Css resource that I would like to have inherited in other
uibinders and be able to have these binders extend the css classes if need
be.
For example:
Let's say I have .myTestClass{ ...properties...} in MyCss.css which is
setup as a CssResource syntactically.
Then I have
