We’re still getting errors like “Rendering of template gallery-wp-eStore.php failed” —we do know about that one: thank you, Ed. That’s occurring on my stuff, Jane’s, and Lynn’s.
But if others of you have time today, kind of randomly prowl Closed Circle and look around; report any bugs like that to us. It was, due to having two administrators operating and implementing at the same moment, one involving a software upgrade, and the other a template/formatting adjustment, a particularly buggy event.
Still looks great on my MacBook. Color, typeface, navigation have no problems.
Okay, everybody. With what I did, there s/b absolutely no difference visually between the CC that was and the CC that now is. I’ve posted an image of what the site should look like with the transparency in place. The color’s probably a bit wonky…its been through two art programs that I’m trying to reconcile, but the transparency should show up.
I’ve changed it for the time being, since the transparency is evidently screwed. Right now, there should just be a flat mauve behind all the words. I’ve also lightened the default BG color, which makes the drop down menu more readable, even if it screws the color balance for the page.
It’s important for me to know if the disappearance of the transparency is a new phenomenon. If you’ve been to the site before and the transparency was there, and visited it earlier today to find it gone, this is a very important piece of information.
As always…thanks for your help.
The missing opacity wasn’t a new thing for me, but depending upon browser.
SeaMonkey 1, Opera 9 and Internet Explorer 7 didn’t do the partial transparency, SeaMonkey 2 and Opera 10 did.
I didn’t have Internet Explorer 8 at the time of testing in February.
The opacity thing isn’t in the CSS2.1 Candidate Recommendation. It’s only in the working draft of CSS3, so the recommended naming and behaviour of that feature hasn’t (theoretically) been fixed yet and apparently the IE currently doesn’t support the proposed opacity, but uses different, IE specific, features.
Last November that last paragraph wouldn’t have made sense to me. Scary. I now understand it perfectly. 😆 Way too perfectly! Thanks, Sabina!
Jane will tell this story over in her blog, but in short, she found out that the gamma on the HP laptop was set to blazing, so visually hot she would squint while working on it in a dim room. She has corrected it, via Paint Shop Pro [her old favorite software] which didn’t correct it well; then after a conference with my brother [who’s a graphics artist] via Photoshop, which proves to be a better manager. Now she’s going through the image files with the gamma correction, [images is where gamma matters a lot] and straightening things out—so the word that we had yet another ‘color issue’ crop up, unrelated to the gamma, and involving a whole new aspect of producing pretty images on lighted screens, gave her a hard afternoon.
We had an important conference with Lynn [Threadbender] last evening on the technicalities and what to do, and she has got a query in with the software creator, but that takes time. Meanwhile we now have a ‘fix’ that enables the site to make sense to various browsers…we hope.
In short, because we have no lab such as the Big Companies have, where we could pre-test our work on various browsers/brands/varieties, and analyze the result, we have to depend on our friends on Wave, Captain, and Chaos to tell us what they’re seeing. It’s really helped, friends: you hear screams of anguish from our direction—that’s only human—but without you guys, we’d be outputting areas that aren’t readable. We hope what we’ve done has improved legibility throughout the site.
I have used this site -> http://browsershots.org/ to get a preview across various systems (don’t try to fix any problems cropping up with Dillo, that thing’s neither fish nor flesh, in fact, exclude that browser from the test).
They don’t always work perfectly so you might want to have someone specifically looking at one browser/OS combination if the results are too out of whack with other versions of that browser.
And I was recently referred to another interesting website, thanks Busifer, showing how a colorblind is likely to see your website http://colorfilter.wickline.org/ (And to get shocked, the black and white filters are supposed to leave a screen completely in that color.)
Thank you so much, Sabina! This will be useful!
Thanks very much for those two links, Sabina and Busifer!
My tries with transparency/opacity left me muttering like a dockworker in my gfi.
IE insists on handling it its own way, badly, with IE5 and IE6 not handling it at all, and IE7 and IE8 handling it IE’s way, non-standard. Firefox attempts to handle it according to a candidate addition. The web design community has been waiting for CSS3 for years, but much (most) is still not out of committee and not implemented in the major browsers.
I’d love to be able to do the cool new things CSS3 promises, but they are not yet reliably doable.
—–
As of now, 2010-08-06 at about 12:40 AM US CST, In FF latest and Win7, I see CC with the light blue and pale beige and dark text, including in the menu bar and dropdown menus and mouseovers. It looks good. In my case, I will have Firefox “zoom in” so the text is bigger on my laptop. Hmmm… My bookmark is set to go directly to Closed Circle’s shop, bypassing the doorbell. I’d be just as happy to have the doorbell jingle as not, but I have fond memories of the cowbell (grins) my mom had on the art store’s entrance. (It was a small to medium jingly cowbell, not a clunky large low cowbell. 😉 ) — The jingly, bright sound of a small bell for a shopkeeper’s doorbell? Cool, bring it on. My opinion only.
Looks like you folks are working out the bugs just fine. Heh, and you didn’t even need an entomologist. Or an anteater. Or a pink scoundrel of a panther…. Or a bunch of gung-ho paratroopers from a certain other SF writer….
Here’s hoping you don’t have to battle the giant ants of Them! either. (Fun old movie.)