On Fri, Dec 23, 2011 at 1:46 AM, Al Sparber <[email protected]> wrote: > On 12/22/2011 12:19 PM, Ghodmode wrote: > >> display: table-cell >> box-shadow: inset ... >> border-radius: ... > > > This tutorial was published in 2009: > http://www.projectseven.com/tutorials/css/3-column-flex-display/ > > >> A.K.A. JavaScript? Doesn't that make this not the CSS solution that >> the title implies? > > The layout is part of the download package. > > >> I checked the demo page with JavaScript disabled. It doesn't work. >> Accessibility... Portability... Security... anyone? > > Security ;-)
There are some security and privacy concerns about enabling Javascript in browsers when it isn't necessary. It's a common enough concern that we should take it into consideration when making web sites. ref: http://krebsonsecurity.com/2011/05/blocking-javascript-in-the-browser/ > Obviously you are confused over what accessibility means. Accessibility > means access to content. For instance, the gray links in this particular > site (which happens to be yours): Accessibility is often an appropriate concern when dealing with Javascript because screen readers don't execute Javascript. However, since the Javascript isn't necessary for site navigation or access to content here, you're right. > http://www.ghodmode.com/blog/ > > That's an accessibility problem. Not the height of columns :-) No, that's just an ugly site with a poorly chosen color scheme :( The coding of my site is crap. I admit it. I originally meant to make it a highly-customized and regularly updated modification of Wordpress, but I didn't stick with it. I'll fix it all when I get a round to it (http://en.wiktionary.org/wiki/round_tuit), but then I'll probably stop before it's done again. Instead of doing something productive with my time, like updating my own site, I spend it making curmudgeonly cynical comments about other people's sites... sorry about that :-} >> Every few milliseconds seems inefficient. I looked at the code. It's >> every 20 milliseconds. > > I'm afraid you are very wrong. Count to twenty milliseconds then look at > this page: > > http://www.projectseven.com/tutorials/css/pvii_columns/examples/widget.htm I might be missing something here. I didn't mean to say that 20 milliseconds is too slow, but that it's too often. Admittedly, it's a small piece of code, but having the browser execute something 50 times per second doesn't seem like a good idea. I'm not enough of a Javascript ninja, and this isn't the right place to discuss it, but wouldn't it be better if code like this was associated with an event handler for onclick or something like that? Hmmm... is there a js-discuss mailing list? >> PVII, it's time to update your site rather than promoting it by >> posting outdated JavaScript-dependant solutions on a CSS mailing list. > > > Update our site? OK. I'll start working on that immediately :-) > > You have a very Merry Christmas or whatever it is that you celebrate this > time of year and make sure you scrutinize the motives behind every gift you > get. Okay, you're right... I was a little harsh. It was the cheesy sales-talk of your first message that set me off. It reminded me of an infomercial. I made some valid points about the code, though. > > -- > Al Sparber - PVII ______________________________________________________________________ css-discuss [[email protected]] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
