ASP.NET Radio Buttons | Tech Off

JeremyJ
The pioneers would be appalled!

Does anyone know how to make a ASP.NET 1.1 radio button use the Windows XP visual style instead of the default style? Is this even possible?

W3bbo
The Master of Baiters

Ah, the naive questions of the inexperienced ASP.NET dev who equates Webforms to Windows.forms Smiley

ASP.NET just generates (X)HTML, the HTML for a radio button is: <input type="radio" />, according to the W3C HTML Forms module specification, it is up to the browser implementation to render them appropriately; usually using native OS widgets. Obviously, UNIX browsers render it differently to Windows browsers.

Please think of ASP.NET in terms of the HTML generated, rather than how it looks in a specific browser on a specific platform, you do no-one any favors that way.

JeremyJ
The pioneers would be appalled!

Yes I am aware that it is up to the OS and browser to render the control. I am using Windows XP with IE but it is not using the correct style. This app is going to have a limited user base that are all going to be using the same OS and browser.

I just want to make sure if they are using XP that it uses the XP visual style.

In ASP.NET 2.0 you can specify the Visual style. I am wondering if the same thing is possible in ASP.NET 1.1 even if it is a bit more difficult to implement.

W3bbo
The Master of Baiters

JeremyJ wrote:
In ASP.NET 2.0 you can specify the Visual style. I am wondering if the same thing is possible in ASP.NET 1.1 even if it is a bit more difficult to implement.

...where does it say that?

ASP.NET 2.0's "Skins" are something else, they just set some default CSS properties for the control elements. If you set even one CSS property on a native UI widget, then Firefox, Opera, and IE will all render the control using their own methods, but if you leave the elements alone then they're rendered as native UI widgets (and hence, with "visual styles")

Maurits
AKA Matthew van Eerde

<META HTTP-EQUIV="MSThemeCompatible" CONTENT="yes">

Or (presumably) add a
MSThemeCompatible: Yes
header to the page

W3bbo
The Master of Baiters

Maurits wrote:
<META HTTP-EQUIV="MSThemeCompatible" CONTENT="yes">

Or (presumably) add a
MSThemeCompatible: Yes
header to the page

It says that doesn't explicity change anything, the meta is only there to turn them off.

Anyway, it's invalid Tongue Out

You'd want this...

<meta http-equiv="MSThemeCompatible" content="yes" />

...instead

Maurits
AKA Matthew van Eerde

Right, the only way my link would help him is if he somehow had a content="no" on his web page. Removing it would then re-enable the visual styles.

But it does contain the informative sentence "By default, visual styles are applied to Microsoft Internet Explorer 6"... which I probably should have quoted in my previous post Smiley

JeremyJ
The pioneers would be appalled!

Maurits wrote:
Right, the only way my link would help him is if he somehow had a content="no" on his web page. Removing it would then re-enable the visual styles.

But it does contain the informative sentence "By default, visual styles are applied to Microsoft Internet Explorer 6"... which I probably should have quoted in my previous post

This is the part that has me confused. It says that they are on by default yet they are not working for me (and no I don't use the classic theme). I have tried both IE 7 beta 2 and IE 6 and they both use the old style. I have no place in the code that explicitly turns visual styles off.

JeremyJ
The pioneers would be appalled!

I figured out what the problem is.

I had various text fields on the form and I wanted them all to look the same so I had a blanket style like:

INPUT
{
border: solid 1px black;
}

I was using an asp radio button but I forgot that internally it was also an INPUT control. If you give a style like a border to a radio button it will strip off the theme and use the classic style instead.

I changed the style to:

.textBox
{
border: solid 1px black;
}

and all is well again. Sometimes I amaze myself when I try to rush something. Sad

W3bbo
The Master of Baiters

Just a note, but in future, when using XML element names in CSS selectors, they should be lowercase, as strictly-speaking, CSS selectors are case-sensitive (indeed: IE isn't case-sensitive about classnames or id="" attributes, yet Gecko and Presto are)