D
@acne said:@db2 said:As someone who writes aspx pages (among other things) for a living, and tests them primarily in Firefox, I'd love to hear the presumed reason for the two being incompatible. Well, this may not be caused by aspx itself, but this very same page has 274 warnings according to my "HTML Validator" extension... If your generated code is not clean, there is no wonder it displays incorrectly in some browsers.
A few possibilities:
ASP.NET isn't 100% generated HTML. You can still put in all kinds of ugly stuff if you wish.
I've seen Tidy bitch about element IDs using XML syntax (probably the "__" at the beginning or something). This usually includes __VIEWSTATE and its kin.
Usability warnings like missing alt text on img tags, tables lacking summary attributes, empty spans, etc. also show up in Tidy.
Looking at the page source of the job posting, though, it appears to be a little of option 3, and a lot of option 1. Holy cow.
However, the Real WTF™ of this job page is that it's an ASPX that creates a frameset which simply displays a standard ASP 3.0 page. Granted, it's not always necessary or practical to update all your asp pages to aspx, but it's almost like they're hiding it. Heh.