Jump to content


can somebody help me with this question?

  • Please log in to reply
3 replies to this topic

#1 garylee

  • New Members
  • Pip
  • Newbie
  • 2 posts

Posted 13 June 2006 - 10:17 PM

anyone in this forum know the answer for the question below?

What are the ways you can deal with x-browser issues? What are the pros and cons of each?

thank you,

#2 AndyB

  • Staff Alumni
  • Advanced Member
  • 5,465 posts
  • LocationToronto

Posted 13 June 2006 - 11:59 PM

Expect cross-browser issues - not every visitor to your site comes equipped with the latest and greatest browser (or your favourite browser).

The sane way to deal with so-called cross-browser issues is to write code that complies with W3C standards. It's a trivial exercise to use online validators for html and CSS, and it's not at all difficult to write valid code to start with. 'Cross-browser' issues then become cases of browsers that fail to comply with reasonable standards. I'm not suggesting you expect CSS2 and CSS3 to be supported, but the CSS1 standard is a sensible goal.

Once you've eliminated a very large percentage of the cross-browser issues by coding rationally and to a standard, the few true cross-browser issues can be resolved with conditional CSS coding NOT by browser sniffing and using a zillion style sheets. The majority of these issues are where IE does not comply, although there are plenty of cases where IE is 'more compliant' than other mainstream browsers.

There are enough CSS-compliance versus browser version tables around to steer you away from trying to make something work that is never going to work :)

Needless to say, check your work with more than one browser and at more than one screen resolution.
Legend has it that reading the manual never killed anyone.
My site

#3 phpvolution

  • Members
  • PipPip
  • Member
  • 13 posts

Posted 14 June 2006 - 10:39 AM

The main thing I do is code for MSIE and Firefox as that takes care of probably 95% of your visitors. That's frustrating enough to get identical appearance on both browsers, so I wont even bother with AOL, Netscape etc. I'm sure they'd have close resemblence on others if you can get the code to work on the big 2.

The biggest issue i've found is with <div>'s, it's pushed as the replacement for <table>'s now, but even the big sites still use tables throughout. They seem to display much more consistantantly across the browsers.

#4 moberemk

  • Members
  • PipPipPip
  • Advanced Member
  • 695 posts

Posted 14 June 2006 - 01:14 PM

Actually, Netscape will now look exactly like either Firefox or IE, because it has adopted the Gecko core but added an IE viewing mode.
Kinda ironic that netscape has taken on the code from a fork of itself.
Disclaimer: No matter how harsh I may be, I'm always IMO only.

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users