Hi,
I'm curious why this mod uses *both* rgb and hex?
It wouldn't bother me, accept that the last value of rgba is opacity. And I discovered that the default css included in the mod (stylesheet_colors_split.css) has many instances where hex is given along with rgba, but the rgba specifies something other than "1".
For instance, on line #23:
a.list-more {background-color:#6699cc;background-color:rgba(102,153,204,0.6);}
Perhaps other css is applying an opacity to that hex, so the rgba is matching it?
But this presents the very real possibility of accidentally using two totally different colors.
It's my understanding that there may be some advantage to rgba over hex for animations, but other than that rgba vs hex comes down to personal preference. I happen to prefer hex, but would happily switch to rgba on a case by case basis.
Is there some specific reason for calling both that I'm missing here? Like maybe some popular browser refuses to process hex?
I'm early on in my template and considering killing all rgba references that have a hex specified. If unexpected results crop up, I can deal with them as they come.
Can you see any reason I shouldn't do that?
Thanks!


Reply With Quote
