OK, I admit this is more a general show off rather than asking for advice but Iíd like to present you the redesigned website of funk and soul band Black Coffee because Iím really proud of it (and it was a lot of work). I did everything except the monsters graphic which was designed by an illustrator who also did the cover of the first album (and will do the second one, too). The handwritten font is also by him. The site is powered by CMS Made Simple and the shop by PrestaShop.
Are you blocking Facebook by default or would that actually be an error? I did probably forget to remove the background color after development (but then there would just be a blank square). Hm… Facebook isn’t quite famous for graceful degradation – need to think about something, possibly a graphical link to the Facebook page.
What problem? These errors are related to the Facebook widget on the code of which I have no influence and the only solutions I’ve found that would make it valid (X)HTML are to insert the widget(s) with JS where I don’t like to rely on JS only to provide basic functionality. Hmm, but now that I think of it – average Facebook users are probably not browsing with JS disabled anyway so if nothing shows up without JS it wouldn’t matter, I guess. I’m gonna look into it. I just need something to put there instead of the Like Box then? Though decisions here.
Originally Posted by bazz
I loaded the page in ff 3.6.10 and noscript not enabling the site. the horizontal nav menu at the top, displayed with the last link behind the white timetable.
once I told noscript to allow the page, the nav menu shrunk, the font chnaged and all was visible, because the nav menu became narrower.
So, you have NoScript set to disallow font-face embedded fonts, too, right? I’ve noticed this issue with older browsers that don’t support font-face (like Firefox 3.0) but have yet to find a standard font that’s narrow/small enough to at least remotely match the custom font. Looking at the browser statistics of the site the oldest Firefox that was detected to be used by a visitor was version 3.5. Then also six hits with unknown browsers.
So, I could completely ignore this issue for the odd visitor that might suffer from it but I really do bother. However, with my aim to make websites work without JS I’m a little stuck here since there is no way to check for font-face support without JS (to style the site differently if unsupported). The only way I found is a JS font-face feature detection by Paul Irish and another one with Modernizr. So, in your case, bazz, with JS disabled and no font-face “support” there’s not much I can do, I’m afraid.
Hmm, well – it just made me thinking – I could probably get around the overlapping issue by floating the time table and navigation instead of positioning them absolutely. But I’d have to rearrange some things then. Need to ponder about it a little more.