Google has released an open source browser based on Apple’s Safari rendering engine. The current version is 23.0.1271.97 Last revised/verified: 2012-12-13.
|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: 2014-03-06
Something is rotten in the state of Denmark.
~ William Shakespear (born: 1564-04-23 died: 1616-04-23 at age: 52) Marcellus in Hamlet Act I scene iv
There is something a little fishy about Google. First they discontinued support for Java Applets, but maintained the fiction they were by having a button to turn it on. It does not work in beta either. They have fiddled with Java Web Start to make it clumsy to use, rather than a one-click as intended. Why are they trying to ruin Java Applets while simultaneously promoting Java for use inside Android cellphones?
Chrome’s support of Java is incompetent to the point of malice. Nether Java nor Java Web start work when you first install Chrome.
You can coax Java Applets to partially work by installing a special Chrome version of Java including a complete JRE version 1.6.0_29 and plug-in DLL (Dynamic Link Library) for Chrome. Once that is done, Chrome will start using your 32-bit 1.7.0_51. You can then uninstall the obsolete JRE version 1.6.0_29. However, even then Chrome keeps asking permission over and over to run an unsigned Applet as if there were something dangerous about it. It re-asks even for the same page and even if you have previously told to it accept Applets from this website before, especially if you load from local hard disk. Further, Chrome randomly fails to render some of the Applets on a page. Every time you reload the page a different set of them will render. Further, it keeps reloading pages for no reason at all, sometimes with Java, sometimes without. This is too incompetent for words. A student who handed in a program in a first year programming course would get failing grade for this sort of half-assed effort.
Once you have Applets working, you can tackle making Java Web Start work, using this easter egg.
available on the web at:
optional Replicator mirror
Please email your feedback for publication, letters to the editor, errors, omissions, typos, formatting errors, ambiguities, unclear wording, broken/redirected link reports, suggestions to improve this page or comments to Roedy Green : . If you want your message, your name or email kept confidential, not considered for public posting, please explicitly specify that. Unless you state otherwise, I will treat your message as a letter to the editor that I may or may not publish in the feedback section. After that, it will be too late to retract it. If you disagree with something I said, especially when sending an ad-hominem attack, a rant composed mainly of obscenities or a death threat, please quote the offending passage and cite the web page where you found it, tell me why you think it is wrong, and, if possible, provide some supporting evidence. I can’t very well fix erroneous or ambiguous text if I can’t find it.
Your face IP:[188.8.131.52]
|Feedback||You are visitor number 11.|