Katie developed her corporation's intra net site using proprietary HTML language extensions based on the company's current browser. The company has recently updated its systems to include the use of…

Question

Options

• ARevise the site to include workarounds and hacks for the new browser.
• BRevise the site's markup language in only those areas that are not rendering properly.
• CUpdate the site using a single language standard consistently, such as HTML5 or XHTML.
• DUpdate the site using the proprietary language extensions required by the new browser's rendering engine.

• A
  7% (4)
• B
  14% (8)
• C
  74% (43)
• D
  5% (3)

Explanation

Using a recognized standard like HTML5 or XHTML (option C) ensures the site renders consistently across all browsers because standards-compliant browsers are built to interpret the same markup in the same way - removing the dependency on any single vendor's rendering engine. Option A (workarounds and hacks) is a short-term patch that creates technical debt and breaks again with the next browser update. Option B (fixing only broken areas) still leaves proprietary extensions elsewhere, meaning the problem persists in untouched sections and will resurface with future browser changes. Option D simply repeats the original mistake - trading one proprietary dependency for another, guaranteeing the same inconsistency problem down the road.

Memory tip: Think "standards = stability." Proprietary = tied to one vendor; standard = works everywhere. Whenever a question involves cross-browser consistency, the answer will always favor open, widely-adopted standards over vendor-specific solutions.

No community discussion yet for this question.