1D0-61B practice question 14 of 15

Katie developed her corporation’s intra net site using proprietary HTML language extensions based on the company’s current browser. The company has…

Full set: 55 questions
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 a new browser. Now the intra net site that Katie developed no longer renders its content consistently. What should Katie do to ensure that this site’s content renders consistently regardless of the browser used?
Answer options
A: Revise the site to include workarounds and hacks for the new browser.
B: Revise the site’s markup language in only those areas that are not rendering properly.
C: Update the site using a single language standard consistently, such as HTML5 or XHTML. Correct answer
D: Update the site using the proprietary language extensions required by the new browser’s rendering engine.
Correct Answer:
C. Update the site using a single language standard consistently, such as HTML5 or XHTML.
Explanation

The root cause of the inconsistent rendering is the use of proprietary HTML extensions, which are specific to a single browser's rendering engine. When the browser was updated, the new version no longer supported these non-standard extensions. The most robust and professional solution is to rewrite the site using a single, universally recognized web standard like HTML5 or XHTML. Adhering to W3C standards ensures that the code is interoperable and will be rendered predictably and consistently across all modern, standards-compliant browsers, resolving the current issue and preventing future compatibility problems.

Why Incorrect

A. Workarounds and hacks are brittle, short-term fixes that increase code complexity and do not address the fundamental problem of non-standard code.
B. Patching only the broken areas is an incomplete solution that leaves other non-standard code in place, creating a high risk of future compatibility issues.
D. This approach repeats the original mistake by replacing one browser-specific dependency with another, failing to achieve true, long-term cross-browser compatibility.

References

1. World Wide Web Consortium (W3C). "About W3C Standards." W3C. Accessed May 2024. In its description of the Open Web Platform, the W3C states its standards "enable developers to build rich interactive experiences... that are available on any device." This principle directly supports using a single standard (Option C) over proprietary extensions (the initial problem) to ensure content works everywhere.

2. Mozilla Developer Network (MDN). "Cross-browser testing introduction." MDN Web Docs, Mozilla, 2023. Section: "What are the main target browsers?". This document emphasizes testing across multiple browsers and implicitly advocates for writing standards-compliant code to minimize inconsistencies, stating, "The main reason we have cross-browser issues is that browsers often have bugs or implement features differently." Using a standard like HTML5 minimizes these differences.

3. Malan, David J. "CS50's Web Programming with Python and JavaScript." Harvard University, 2024. Lecture 0: HTML, CSS. The course materials emphasize the importance of web standards established by the W3C to move past the "browser wars" era where proprietary tags (like or ) caused websites to work in only one browser. The curriculum teaches writing standards-compliant HTML5 to ensure universal functionality.

Scroll to Top