Asked by La'niyah

Acme Company has been receiving complaints from its suppliers saying that its extranet site does not render correctly in all their employees' browsers. The suppliers are asking that the extra net site to be fixed so that everyone can access it, regardless of browser type. When examining this problem, the Acme Web Development team finds that many developers worked on the site and each used code that he or she was comfortable with. To resolve this problem, what can the Acme developers do?

All Answers 1

Answered by GPT-5 mini AI
They should stop relying on browser-specific hacks and make the site standards‑based and consistently coded. Practical steps:

1. Audit and validate
- Run the HTML/CSS/JS through validators (W3C HTML/CSS validator, linting tools) to find broken or non‑standard markup.
- Inventory browser failures so you know which features are failing where.

2. Use standards and a consistent DOCTYPE
- Choose a modern DOCTYPE (e.g. <!DOCTYPE html>) so browsers use standards mode.
- Standardize on semantic, valid HTML and CSS across the site.

3. Move to progressive enhancement (or graceful degradation)
- Build core functionality in plain HTML/CSS that works everywhere.
- Layer on advanced features with JavaScript only for browsers that support them.

4. Use feature detection, polyfills and shims — not browser sniffing
- Use Modernizr (or native feature detection) to detect capabilities and load polyfills.
- Add polyfills for missing APIs (e.g. Fetch, Promises, HTML5 features, etc.) or include HTML5shiv for older IE if needed.

5. Use cross‑browser libraries and CSS normalization
- Use a stable DOM/CSS abstraction library (e.g. jQuery or modern equivalents) to smooth inconsistencies.
- Include a normalize.css or reset to reduce browser default differences.

6. Refactor and enforce coding standards
- Adopt a front‑end style guide and best practices so all devs use the same patterns.
- Introduce code reviews and automated linting to prevent regressions.

7. Test across target browsers and automate
- Define supported browsers/versions and run manual and automated tests against them (BrowserStack, Sauce Labs, Selenium, CI).
- Continuously test as new code is added.

8. Deploy incrementally
- Roll out changes in stages and monitor supplier feedback; fix edge cases as they appear.

Taken together these steps will make the extranet render consistently across the suppliers’ browsers and prevent the problem from recurring.