Microsoft KB Archive/255634

From BetaArchive Wiki
Knowledge Base

INFO: Visual InterDev and Cross-Browser Compatibility

Article ID: 255634

Article Last Modified on 4/22/2001


  • Microsoft Visual InterDev 6.0 Standard Edition

This article was previously published under Q255634


Visual InterDev provides the option to produce code that either utilizes the rich feature set of Microsoft Internet Explorer or is cross-browser compatible for a broad reach.

The Visual InterDev broad reach code should target any HTML 3.2-compliant browser. However, as this article describes, the code may appear different in different browsers and is not strictly compliant with HTML 3.2.

Keep in mind that Visual InterDev does not limit a developer to HTML 3.2. Visual InterDev makes several features (such as cascading style sheets) available for use that may not be compatible with older browsers. As always, a developer should intentionally limit code and features to those understood by the target browser. In addition, a developer should test pages in all target clients.


The following is a list of broad-reach code that is not strictly compliant with HTML 3.2.

  • Scripting Object Model <FORM> tags are not within <BODY> tags.

    When you enable the Scripting Object Model (SOM), Visual InterDev places <FORM> tags at the top and the bottom of the page outside of the <BODY> tags. Although HTML 3.2 specification states that you should place <FORM> tags within <BODY> tags, the SOM functions properly.
  • Enabled check box for Design-time Controls is not directly supported by non-DHTML browsers.

    The Textbox, Checkbox, Listbox and OptionGroup Design-time Controls (DTCs) have an Enabled check box on their property sheets. When you clear this check box, you enable the code to check if the browser that requests the page is DHTML capable.

    For DHTML browsers, add a Disabled attribute to the <INPUT> tag. This causes Microsoft Internet Explorer to display the actual control in a disabled state, or a state that cannot be edited.

    If the browser is not fully DHTML capable, then it uses straight HTML to display the control, which can alter the display. For example, the Textbox DTC, which appears across a page in Internet Explorer, may appear in a column in other browsers. To precisely control the layout of DTCs, you can place the controls in an HTML table.
  • Design View can use Absolute Positioning.

    HTML 3.2 does not support the Absolute Positioning option in Design View editor. If you do not want to use Absolute Positioning, make sure that you do not enable the absolute positioning option on the Design toolbar.
  • InterDev Theme uses unknown attribute "VI6.0THEME."

    When you use unrecognized attribute tags, the tags are ignored. This should not cause any undesired results.
  • Browser does not draw grid borders when cell contains no data.

    Netscape browsers and Internet Explorer 5.x do not draw table cell borders when the cell is empty. Beginning with Visual Studio 6.0 Service Pack 4, the Grid DTC checks for the existence of an empty cell and inserts an HTML encoded non-breaking space so that all cells display with borders.
  • Graphics from Visual InterDev Themes may not display in Netscape browsers.
  • This is a known bug in Netscape Navigator. For additional information, click the article number below to view the article in the Microsoft Knowledge Base:

    238342 PRB: Graphics from Visual InterDev Themes May Not Display in Netscape Browsers

The third-party products that are discussed in this article are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.

Keywords: kbinfo KB255634