|Best Browsers||Engaging the Java Console in Your Browser|
|Performance||launching a browser|
|Detecting Which Browser||Browsing Locally from Hard Disk|
|Browser Bugs||Learning More|
|Setting Default Font||Links|
|Please select one of these modern browsers to download and install free.|
|Click the corresponding browser icon to download the latest free browser software, or click the browser name for more information.|
|IE11||11.0.9600.17501||with the Java 1.8.0_102 JRE (Java Runtime Environment). Now works with Java Applets. Some websites will work with no other browser, though many work on everything but this eccentric browser. 10% market share.|
|Google Chrome||53.0.2785.92||with the Java 1.8.0_102 JRE. Dropped support for Java Applets. Good for YouTube. Frequently automatically updated. Has no edit source button. Slow starting when it fiddles with a proxy. Poor downloading — it hides the fact it is doing so in the bottom left corner. Often downloads without you asking. Handles foreign language sites particularly well since it integrates with Google Translate by automatically translating. Best for interacting with Google. BrowserMark rates this as the fastest browser. Good for ecommerce. Can’t print white writing on a black background. 53% market share.|
|Firefox||49.0||with the Java 1.8.0_102 JRE. No longer suppoorts Java Applets. Most widely supported next to IE. Many add-ins. Very fast rendering. Weak on table rendering. Best for printing. Fairly slow to start up. Often stalls on first page from a new site. Must hit reload. 9% market share.|
|SeaMonkey||2.40||with the Java 1.8.0_102 JRE. Similar to Firefox, with integrated Email. No longer supports Java Applets.|
|Safari||5.1.7||with the Java 1.8.0_102 JRE. For both Macs and PCs. No longer supports Java. Apple has dropped support for the PC version. Freezes. Simple and stripped down. 12% market share.|
|Opera||39.0.2256.71||with the Java 1.8.0_102 JRE. It no longer its own rendering engine, which was its main advantage. It uses Chrome. It no longer supports Java Applets.No longer lets you configure your own editor. No bookmarks. Implements SPDY for faster communication. In Turbo mode, caches pages in encrypted compressed form. 6% market share.|
|Edge||25.10586.0.0||with the Java 1.8.0_102 JRE. Stripped down browser without features. It does not support Java or any other plug-in.|
|Temporary Internet Files||Cache||Cache|
|Address Bar||Location Bar||Address Bar|
|Links Bar||Bookmarks Toolbar||Bookmarks Panel|
|Copy Shortcut||Copy Link Location||Copy Link Address|
|Save Target As||Save Link As||Save Target As|
|RSS (not supported)||Live Bookmark||Feed|
There is no common format for bookmarks. You can import/export bookmarks only between a fairly small subset of all browsers. Reinstalling losses you bookmarks. Switching browsers loses your bookmarks. OS (Operating System) crashes lose your bookmarks. The best stratgy is to maintain your bookmarks as HTML (Hypertext Markup Language) files. Then they will work for any browser, and they are easy to back up. You can also maintain them with bulk search/replace tools and link checkers.
Opera: ignores <col format settings for table columns. Ignores CSS (Cascading Style Sheets) max-width property. Does not support CSS overflow to permit scrolling tables. Can’t access a printer to print a selection in Vista.
Firefox: Does not display borders on Applets. Ignores <col class and alignment settings for table columns.
Mozilla: Does not display borders on Applets.
SeaMonkey: draws boxes needlessly around links that consist of an image plus text.
Internet Explorer: does not render *.png image files with transparent backgrounds properly. In the latest update of IE (Internet Explorer), it won’t render Applets unless you click on them. This makes Applets like CurrCon which displays all the prices on a page in your local currency useless. This is just another part of Microsoft’s dirty war against Java.
Report bugs to the vendors in their support forums. The squeaky wheel gets the grease.
Officially, browsers are not supposed to support <col class= command out of some idiotic prissiness. Some browsers support it anyway out of common sense.
|Browser Colgroup Support|
Those browsers marked with an x all have a bug. They will not render <col class="xxxx">s correctly. The ones with a tick render it correctly. The Opera people say this is a feature not a bug. The language lawyers claim the W3 spec says that the browser is supposed to ignore the color attribute from the <col class. Logically, I think the <col styles should apply to the entire column, but not to <th rows. In addition Firefox, SeaMonkey, Safari and Flock also ignore the <col align attribute. Opera and IE render it properly.
Firefox, SeaMonkey and Opera support almost all the HTML5 entities. Chrome and Safari support many of them.
|Style Test||Alignment Test|
|On Every row||style||alignment|
If both cells in the left hand Style Test column are the same colour, then your browser (the one you are using now to view this page) supports <col class=.
If both cells in the right hand Alignment Test column right-align, then your browser supports <col align= correctly.
Dreamweaver lets you apply a css style to all rows individually. Last revised/verified: 2016-09-19
If HTML were a compact, preparsed binary format, that would eliminate nearly all of the malformed HTML in the universe. That would also mean it would be much likely if a document were tested on only one browser, it would render properly on all of them, or at least most of them. As a side effect it would download twice as fast and render more quickly.
If you are in a browser you have to enable to console before you can see it. Avant and Chrome do not support Java, or more precisely, their support does not work. Safari does support the Java console. Browsers no longer have menu-items to engage and disengage the console. You do it in the Java Control Panel.
In Mac OS Leopard, you also have to enable the console on the Java Preferences Application.
Why would you want to view a website from your local hard disk?
If you want to view *.html files on your local hard disk, an ordinary browser will do. You start your browsing session with a local filename e.g. J:\mindprod\jgloss\jdk.html of a file url e.g. file:///E:/mindprod/jgloss/jgloss.html. From there all the links are relative.
There are a few catches. The website does to work quite the same as it would on the web:
Perhaps some day there will a configuration file to give the browser some hints about the local mirror. It would contain the name of the root directory, the extension ⇒ MIME (Multipurpose Internet Mail Extensions) type table, the URL (Uniform Resource Locator) of the web version… The configuration file is like configuring a very stripped down server implemented by the browser.
Then instead of those wretched ../../jgloss/jdk.html relative links, you could use links of the form /jgloss/jdk.html which are relative to the root of the website, in your markup. The link to a file would be identical no matter where on the website it occurred.
If you want your local copy to behave more realistically as it would on the web, you have to install a static webserver such as Tomcat. It runs on your local PC (Personal Computer) and talks only to you. This fairly complicated, almost identical to configuring and running a server on the web.
This page is posted
Optional Replicator mirror
Your face IP:[184.108.40.206]
You are visitor number|