Quote Originally Posted by RixStix View Post
The part that scares me is when I read portions of a current plugin is now part of core.... AND what happens to the portion of the plugin that is not core? For a user who might not read everything before they start. That's one thing I have learned over the past 10 years... people dont read... myself included at times. But at least I can say that I make an effort to read. Might not be able to comprehend what I am reading well enough to implement things or attempt to implement and cause myself a few days of headache. But I did read.
Two good points.

Again, think of the mod as having certain elements that may well have been moved into the core in 155 or especially 156. It may just be that new functionality in some other area of pricing eliminates the need for all of DPU to be ported over.

Reading!?! You think people need to read!?!. I like the ones that read the posting tips reminder juuuussssst enough to know to remove that portion before posting. No current version, no mods, no link, etc, etc, etc.

Your site does very well on Accessibility. The only item that is not already fixed in 1.5.7's non-css area is the contrast of your site. It's also one of the reasons we're revamping the Color Change mod for 1.5.7. In your case, color-second is the problem (probably copied from our mod -- or so I read) The hex is too harsh if the browser doesn't use the rgba. Compatibility is driving us to lighter hex and more opaque rgba colors to keep from "blasting" folks out.

And, so many are finding that the opacity really go off the charts if two or more are on top of each other. A quick example is to go to your site and F12 or right-click to inspect. Navigate to the @navManWrapper and turn off both the hex and rgba. Watch your Categories header as you turn either one back on. Notice how it can be three different colors depending upon where the opacity is entered.

Anyway, enough of the hijacking. Keep those positive thoughts going and you won't be #0000FF