The Browser Compatibility Check (BCC) feature helps you locate combinations of HTML and CSS that have problems in certain browsers. When you run a BCC on an open file, Dreamweaver scans the file and reports any potential CSS rendering issues in the Results panel. A confidence rating, indicated by a quarter, half, three-quarter, or completely filled circle, indicates the likelihood of the bug’s occurrence (a quarter-filled circle indicating a possible occurrence, and a completely-filled circle indicating a very likely occurrence). For each potential bug that it finds, Dreamweaver also provides a direct link to documentation about the bug on Adobe CSS Advisor, a website that details commonly known browser rendering bugs, and offers solutions for fixing them.
By default, the BCC feature checks against the following browsers: Firefox 1.5; Internet Explorer (Windows) 6.0 and 7.0; Internet Explorer (Macintosh) 5.2; Netscape Navigator 8.0; Opera 8.0 and 9.0; Safari 2.0.
This feature replaces the former Target Browser Check feature, but retains the CSS functionality of that feature. That is, the new BCC feature still tests the code in your documents to see if any of the CSS properties or values are unsupported by your target browsers.
Three levels of potential browser-support problems can arise:
An error indicates CSS code that might cause a serious visible problem in a particular browser, such as causing parts of a page to disappear. (Error is the default designation for browser support problems, so in some cases, code with an unknown effect is also marked as an error.)
A warning indicates a piece of CSS code that isn’t supported in a particular browser, but that won’t cause any serious display problems.
An informational message indicates code that isn’t supported in a particular browser, but that has no visible effect.
Browser compatibility checks do not alter your document in any way.