Yep, You are correct that this wouldn't solve my problem. I have been fighting with it for a little while now. I don't want to hack and I don't want to alter. So more in frustration and giving up on my problem thought of the future, so I came here, Thanks for the response.
Thank you also for pointing me to initial value. I haven't found much about it in the spec I will have to play around with that, thanks.
Colt
-----Original Message-----
From: Tab Atkins Jr. [mailto:jackalmage@gmail.com]
Sent: Tuesday, April 27, 2010 9:30 AM
To: Colt Antonio Pini
Cc: www-style@w3.org
Subject: Re: Display
On Tue, Apr 27, 2010 at 9:20 AM, Colt Antonio Pini <Colt.Pini@nau.edu> wrote:
> The only problem with that is when coding in Visual Studio the way that the RequiredFeildValidator tag works is through that functionality, switching between display none and inline. In order to fix that problem I would need to go in and change the rendering JS in Visual studio. I agree that there are ways around this problem, and good ways around it, which I am going to have to do now, but just thought of this for a nice feature to have so that we wouldn't have to go through a work around. I am sure there are many more instances where this functionality would be nice to have.
Your suggestion wouldn't fix your problem, though. You'd still have
to change ASP to use display:default instead of display:inline; it
would take the same amount of effort to fix it correctly, with the
added benefit that you don't have to wait for this feature to be
specced and implemented in all browsers.
(That said, check out the 'initial' value. It's a special value that
all properties accept, and which should be what you're asking for. It
still wouldn't solve your problem, though, for the reason above.)
~TJ