Version Headaches
As a further complication, there are the inevitable prerelease versions of browsers and standards.
Browser prereleases are sometimes called “preview editions” or “beta” versions. While not officially released, these versions give us a chance to see what new functionality will be available for content display in the next-generation browser. Authors who follow browser releases closely sometimes worry when certain aspects of their current pages fail to work properly in prerelease versions. The fear is that the new version of the browser is going to break a carefully crafted masterpiece that runs flawlessly in released versions of the browser.
Somewhere between the releases of Netscape Navigator 2 and 3, I learned not to fret over breakages that occur in prerelease browser versions. Of course, it is vital to report any problems to the browser maker. I refuse, however, to modify my HTML or scripting code to accommodate a temporary bug in a prerelease version of a browser, as it is being used by an extremely small percentage of the population. My feeling is that anyone who uses a prerelease browser does so at his or her own risk. If my pages are breaking on that browser, they’re probably not the only ones on the Net that are breaking. A user of a prerelease browser must understand that using such a browser for mission-critical web work is as dangerous as entrusting your life’s work to a beta version of a word processing program.
On the standards side, working groups ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access