jeffamm

Ste,Thanks but won't that bold everything? I'm trying to selectively bold words within the list item.

When I try to bold some text within a list item, as in:<ol><li><b>Topic 1</b> - text text text</li></ol>I see that it is not considered valid with xhtml 1.0 transitional. I'm trying to keep all my code valid. Is there a proper way to do this, or is it not possible with list items?many thanksJeff

Vchris,Interesting that it works for you (with Firefox I assume) but I just fixed it - another newbie mistake. When I drew the border I had used the z-index=2 so the links were obscured by the box. I didn't need the z-index, they were just vestiges of old code, so removing them fixed it. thanksJeff

I have a list of links on our home page in a "top 50" box that Firefox ignores (doesn't see as links, cursor doesn't change) as follows:<div style="position: absolute; left: 480px; top: 495px; background-color: transparent; width: 280px; padding: 0px;"> <br /><a href= "http://www.allmusicmethods.com/product_details.aspx?item_guid=6c0bfc16-748d-4035-88b4-f75b1cb28b12" class="Top50List">1. Hal Leonard Guitar Method Book 1 - Bk</a><br /><a href= "http://www.allmusicmethods.com/product_details.aspx?item_guid=aaa1efbb-3c7a-4114-9475-c79dc1891c48" class="Top50List">2. Hal Leonard Guitar Method Book 1 - Bk/CD</a><br />and so on to a closing </div>The page and CSS have been validated.What am I missing, and can I just put the class'"Top50List" in the div tag and not repeat it per line?thanks much

I finally got my homepage to validate, and learned a lot about asp.net in the process, but I'm finding that FireFox 2.0 doesn't recognize some links as links. I'm sure I can trouble shoot the specific links that don't work - my real question is whether XHTML 1.0 transitional validation means that FireFox will work, or is it still a case by case issue? If I validated to strict, would that then "guarantee" it?

OK that was too easy. I didn't realize the HorizontalAlign was non-standard. Changing to align took care of it.many thanks

I'm finding that HorizontalAlign="center" renders as align="Center" and generates an error from the W3C validator. I've already put in a fix (Browser Caps) to cause the validator to appear as a newer browser, and that fix has fixed other rendering errors, but this one remains. Just wondering if perhaps this isn't a rendering error, or if anyone has some thoughts on it.many thanks and happy holidaysJeff

Thanks for your help jesh - the browser caps search led me to Phil Scott's Weblog where I found the item below. I created a browser caps section in my web.config and added the code below, and it cleared up the error I was getting due to rendering for different browsers. I was still left with one rendering error, which I'm posting in this forum separately, but was able to work-around it be deleting it. Crude, but it validates, and appears to have no other effect on my site. thanks again,Jeff"With the go-live of ASP.NET 2.0, I've been actually using it at a level of more than "ooh, pretty new feature." I'm kinda of a standards nerd, so naturally I've been messing around with the XHTML output and making sure I like what I'm seeing. So far, so good. But I ran my page against the W3C's validator and it freaked out, complaining about form tags having names and the such. So I take a look at the source, and it looks good to me. So I go back to the validator, and run it one more time, this time enabling "Show Source." Ah, there's the problem. ASP.NET thinks that the validator is some ghetto browser from 1996 so it is sending it invalid markup.The fix was pretty easy once I tracked it down. Simply update the browseCaps section of your web.config to tell ASP.NET about the W3C's user-agent. Here's the code I'm using:<case match="W3C_Validator+"> browser=Netscape frames=true tables=true cookies=true javascript=true javaapplets=true ecmascriptversion=1.5 w3cdomversion=1.0 css1=true css2=true xml=true tagwriter=System.Web.UI.HtmlTextWriter</case>Now when you validate your page, ASP.NET will send out the same HTML as it would if Firefox or IE were requesting the page. Now what I'd really like to do is tell ASP.NET to shove it, and spit out XHTML on unknown browsers. Anyone have any ideas?"

I'm working on getting the main pages of my website to validate, but keep getting an error in one line of code that is created dynamically by asp.net pages. If you load the page with an older browser it delivers code with older-compatible html. If you load it with a new browser, you get more recent and valid (by W3C standards) html/xhtml. The validator "browser" type must be or appear "old" in that it is getting the non-valid code. Is there any way to tell the validator to view the site with a more advanced browser? I apologize if my language isn't completely precise but hopefully you understand the issue and question.many thanksJeff

I have a .aspx website (www.allmusicmethods.com) and I'm trying to get the homepage to validate with XHTML 1.0 Transitional. The homepage is comprised of a main site.master page, left_nav.ascx bar, top_nav.ascx bar, default.aspx page and main.css which recently validated.I'm getting this error:Line 103, column 159: there is no attribute "border" . ...arch" src="images/btn_go.gif" border="0" />The challenge for me is that this line of code literally does not exist in any file. The line of code that contains the phrase src="images/btn_go.gif" is actually as follows:Private m_ImageURL As String = "~/images/btn_go.gif" in a file "c_search.ascx" which is incorporated in the left_nav.ascxThe c_search.ascx calls a sub called Ms_search through a register at the top of the file (<%@ Register Src="~/controls/c_search.ascx" TagName="ms_search" TagPrefix="uc1" %>) and displays the Ms_search through this:<table class="tableleft" cellpadding="0" cellspacing="0" bgcolor="#c8c8c8" > <tr> <td class="tdleft" style="width: 285px; height: 76px"> <uc1:ms_search ID="Ms_search1" runat="server" />My question is, is the border="0" coming from the CSS items, either tableleft or tdleft? The CSS for those is below. The second question is what do I change to get it to stop creating the border="0" that the validator doesn't pass? Appreciate any guidance that anyone can offer.thanks.tableleft{ border-right: gray 1px solid; border-top: gray 1px solid; border-left: gray 1px solid; border-bottom: gray 1px solid; padding-right: 0px; padding-left: 0px; padding-bottom: 0px; padding-top: 0px;}.tdleft{ border-right: 1px solid; border-top: 1px solid; border-left: 1px solid; border-bottom: 1px solid; background-color: gray; color: white; font-size: x-small;}

The updated one is still on our staging server until I finish some more testing. Then I'll move it to our live server and submit the URL. Right now I'm having some trouble getting the stage server to recognize the line-height attributes in a couple of our CSS elements. I'm going to experiment with % values instead of the 1.4 type numbers that I've been using.thanks

Thanks Boen, yes I have been uploading the file, I'll try it with the URL and see what happens

Jonas,Are you sure you read it right? Look again, it says Jonas.(OK, kidding aside, I just changed it - sorry to get it wrong, I was up about as late last night in my time as you were in yours.)Thanks for your comments, they were very helpful again. Anyway, the link you gave shows the file and says "Congratulations" and here, use the valid CSS icon. I'm not getting the congratulations or the suggestion to use the icon, which for some reason I really want. I'm just wondering why it's not coming up?

OK, with a lot of help from Snoja I cleaned up and fixed all my errors, but when I submit the file for validation it doesn't say "Valid", it just shows no error. I was under the impression that when you were valid you would see a green header saying "Valid" or something similar. I do have many warnings still to clean up but I've been told they don't "count". What message do others receive when they are validated?Also, many of the warnings are to add either a background color and/or a color to many CSS classes that haven't otherwise needed them. I tried dealing with this last night by adding background-color:transparent but it didn't appear to be acceptable to the validator. Shouldn't transparent work - the CSS Primer I read seemed to indicate it was fine to use?thanksJeff