Assuming you meant add/remove from classList as you proposed in the first post,
then I think the answer is yes. I think that's simple enough to emulate and
will work most of the time. I think you have to use classList instead of
className because there will be other things in the classList.
F
Thanks Alex, but - as a follow-on, do you think the styleName setter should
set the className if it has a string value assignment? Or should we be
telling people to manually edit the code/mxml and swap styleName string
value assignments to 'className' value assignments? I think for the
majority of
Without thinking too hard, I would output a warning if someone passes something
other than a string. Then we'll know if anybody really needs the more complex
cases and can figure out what to do about it then.
-Alex
On 5/6/20, 2:11 PM, "Greg Dove" wrote:
This question is mainly for Alex
This question is mainly for Alex or anyone else involved in porting an
MXRoyale application.
When porting styleName='myStyleName' what is considered the best approach?
I would have assumed that styleName could simply be added to the underlying
element's classList if it is a string, so it (I assum
