On 3/12/07, Gaspar [EMAIL PROTECTED] wrote: Iam working with the interface/html team and maybe the team that build the aplications wouldn be so open to that changes, they say that is easiest and quicky putting the native elements of .net tham building, They're absolutely right, it is easier.
artifacts on my screen (they show up more on the Macbook for some reason). Also, the sub-menus on the left-hand navigation appear, then grow slightly in size (in both Safari and Camino on MacOSX). I'm not sure if that's intentional or not, but it's a bit distracting. Cheers, -- Olly Hodgson http
On 10/13/07, Christian Montoya [EMAIL PROTECTED] wrote: In a way, it's kind of like embed vs. object. In a way, but... Of course, if you really want to use innerHTML, you could probably go right ahead. But if you are already using a very DOM-friendly framework like jQuery, you may as well
On 10/27/07, Simon Cockayne [EMAIL PROTECTED] wrote: So...how can I spread the good word of valid CSS, XHTML and WCAG...without spoiling the site with verbose text or logos? To be honest, I wouldn't bother. If the client doesn't want it, and it's not adding anything to the site, why are you
On 10/29/07, Rob Mason [EMAIL PROTECTED] wrote: My eyes, my beautiful eyes...it burns. whisperI actually quite like it./whisper It's nice to see someone trying something slightly away from the norm. OK, so they don't quite pull it off -- the mad scrolling stuff could do with being toned down a
for International Users: Practical Tips rather enlightening. The audio and slides are available from http://www.vivabit.com/atmedia2007/europe/schedule/ Cheers, -- Olly Hodgson http://thinkdrastic.net/ *** List Guidelines: http
On Nov 14, 2007 10:37 PM, Michael Horowitz [EMAIL PROTECTED] wrote: I have examples using one value onchange=showSubcategory(this.value) from a form to a script. What if I need to send two values one from the current element in the form and one from another element
On Nov 14, 2007 11:11 PM, Olly Hodgson [EMAIL PROTECTED] wrote: onchange=showSubcategory(this.value, document.getElementById(anotherElement).value); While I'm here, two points: Doing anything major using the onchange event isn't a great idea. The reason being it can scupper keyboard users