Member Avatar for sant

I have just finished developing a website which is working fine in IE but giving some problems in FF and NS.Converting all to CSS is not possible:sad: .Please cite some solutions for this...
--sant:?:

  • 4 Contributors
  • 3 Replies
  • 127 Views
  • 1 Month Discussion Span
  • Latest Post Latest Post by M_K_Higa

Dani AI

Generated

— IE-only behavior usually traces to a few predictable causes: missing or wrong DOCTYPE (quirks vs standards mode), browser-default CSS differences (margins, line-height, form styles), layout rules that only IE implements (older IE has "hasLayout" quirks), and JavaScript/DOM differences. In ASP.NET you can also get different HTML emitted because the framework detects the browser and changes control rendering.

A practical troubleshooting checklist:

  • Create a minimal, static test page that reproduces the problem. Reduce until the bug is isolated.
  • Validate the HTML/CSS to catch markup errors that trip other engines.
  • Use each browser’s inspector to view computed styles and box sizes, and check the console for JavaScript errors.
  • Compare computed styles across browsers to spot defaults (margins, padding, display).
  • Disable CSS to see the raw flow, then reintroduce rules one at a time.
  • If server-side rendering is suspected, output the generated HTML (view source) or return a static sample to compare.
  • When asking for help, include DOCTYPE, browser versions, ASP.NET version, and a minimal HTML/CSS snippet that reproduces the issue (not the whole site).

On the ASP.NET point raised by : update or add browser definition files at the app level (App_Browsers) rather than editing machine-level files. That teaches ASP.NET which features a client supports and avoids incorrect fallbacks. Prefer feature detection and client-side polyfills over server-side user-agent sniffing.

Design workflow note for : designing to standards-compliant browsers first (Firefox/Opera/modern Chrome) then applying small, targeted IE fixes (conditional comments or IE-only rules) tends to be fastest. Always re-test tweaks in all target browsers to avoid regressions.

Recommended Answers

All 3 Replies

Member Avatar for ses5909

What version of the framework are you using? You would need to post some code or some links so we can look at it.

Member Avatar for reklawnnelg

Check out http://slingfive.com/pages/code/browserCaps/ for information on how to modify ASP.NET to recognize the advanced capabilities of other browsers. By default, ASP.NET does not recognize that other browsers can do the same fun stuff that IE can do. I have not tried this, but it looks promising.

Member Avatar for M_K_Higa

I use IE 6 as my main browser. However, when I design CSS, I usually design against Firefox and Opera because these browsers are more standards compliant.

Once I get it right in FF and Opera, then I can start tewaking for IE, but keep in mind that you should test every tweak in FF and Opera to assure that you didn't break anything.

You may want to add IE 7 to the inital design target along with FF and Opera because IE 7 has good CSS standard compliance. Personally, I haven't added IE 7 as a target browser simply because IE 7 and IE 6 cannot co-exist on my machine. (Can't afford another PC and don't have enough memory for any kind of VM solution.) :(

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.