Wait, strike that. I was removing all of /3rdparty, not just blueprint. The updated list of what changes if BP goes away is this:
Nothing. It was all in humanmsg, I guess. I saw no difference on any pages when I removed /3rdparty/blueprint. This of course was all just 'ocular inspection', nothing programmatic. If anybody has one of those unused CSS analyzers, it probably wouldn't hurt to run it. -mikelietz On Feb 20, 9:31 am, mikelietz <[email protected]> wrote: > We do still use something in BP for the publish page - removing it I > see extra shapes around the textareas. > > Also, the dropbuttons disappear without it. > > The 'add user' text boxes get messed up. > > Logs don't expand. > > These I tested in Chrome on r3231. This is everything I saw, but I may > have missed pages or links. > -mikelietz > > On Feb 19, 7:24 pm, Michael Bishop <[email protected]> wrote: > > > Aside from Mzingi using Blueprint (which was a decision based on our > > admin using it at the time) is there a reason that we are including it > > still with our download? As far as I know, admin doesn't use it all, > > as we moved the CSS reset to the admin style sheet. > > > If not, should we just remove BP from Mzingi and remove it? > > Otherwise, should we upgrade to the latest .8 release for our .6 > > release? > > > ~miklb --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/habari-dev -~----------~----~----~----~------~----~------~--~---
