Skip to end of metadata
Go to start of metadata

Document Status - Experimental

This brick is experimental. It may be futile or full of errors because web browser technologies continually come into and exit from the environment without architectural review, let alone governance. The UW-IT strategic vision anticipates this trend due to the widespread use of commodity web browser technologies that enable bring-your-own-device access to mobile, social, and cloud resources in the consumer environment. Therefore, in our business architecture, the choice of web browser software is increasingly user-centric and consumer-oriented. It's a personal choice — and other architecture decisions follow accordingly. Web resource providers can align with this vision by adopting open, interoperable protocols and standards that work across platforms and adapt more easily to the web browser technologies used by our constituents in the wider consumer environment, one that increasingly includes web browser software with automatic update features that help browser users keep current with emerging and improved technologies. Responsive, mobile-friendly web design is another means by which web resource providers can align with this anytime, anywhere, any-device architecture.

Description

A Web browser is client software used by a browser user to interact with resources located on web sites. Web browsers allow a user to retrieve and interact with resources, as well as navigate between resources.

Status Table

The following table categorizes related technologies according to their current lifecycle status.

Emerging
(Trends to watch)
Strategic
(Future)
Tactical
(Limited support)
Baseline
(Full support)
Containment
(Reduced support)
Retirement
(Scheduled for retirement)

Software:


Protocols:

  • WIA-ARIA

Technical Services:


Software:

Protocols:

Technical Services:

Software:

Protocols:

Technical Services:

Software:

  • Desktop
    • Chrome (latest stable release)
    • Firefox 6.0 and above
    • Internet Explorer 7.0 and above
    • Safari 5.1 and above
  • iOS
    • Mobile Safari (latest stable release)
    • Chrome for iPhone and iPad (latest stable release)
    • Opera Mobile (latest stable release)
  • Android
    • Built-in Browser (latest stable release)
    • Chrome for Android (latest stable release)
    • Firefox for Android
  • Windows Mobile
    • Internet Explorer Mobile?
  • Other
    • any?

Protocols:

  • HTTP versions?
  • XHTML/HTML versions?
  • CSS versions?
  • JavaScript versions?
  • SSL/TLS versions:

Technical Services:

Software:

  • Desktop Browsers
    • Chrome
    • Firefox 5.0 and earlier
    • IE 6.0 and earlier
    • Safari 5.0 and earlier
  • Other
    • Lynx 2.8
    • BlackBerry Browser

Protocols:

Technical Services:

Software:

Protocols:

Technical Services:

Note: Refer to the IAM Brick Reference for complete descriptions of the six status designations and common lifecycle patterns.

Comments

  • Emerging
    1. WIA-ARIA...
  • Strategic
    1. No technologies have been evaluated for the strategic designation.
  • Tactical
    1. Some technologies here, but they're hard to identify.
    2. Tactical choices are sometimes required by teams who manage desktops, laptops, tablets, phones, and other devices for their customers. In these cases, customer choice and baseline options aren't always feasible.
  • Baseline
    1. Pattern: latest stable release, maybe also previous stable release
    2. Pattern: automatic updates
    3. Internet Explorer version 8.0 and above supports a feature called "Compatibility Mode" to emulate earlier pre-8.0 versions. Ironically, when this feature is enabled, users may experience compatibility problems.
  • Containment
    1. Many earlier versions of common web browsers are under containment.
  • Retirement
    1. Many other older versions of web browsers are or should be under retirement, way too many to track.

References

See Also

Last Review Date

April 1, 2013 — initial draft for discussion purposes only.