STICKY POST
Saturday, 10. June 2006, 10:44:48
psychological warfare, opera, browsers, incompatibilities
...
This blog is dedicated to identifying and (perhaps if god willing) finding resolution to the varitable amount of problems that Opera has with the latest web technologies.
As a web developer currently working with creating websites that are cross-browser compatible, I am convinced that through Opera's inability to properly render code reliably, to properly parse javascript or other Web 2.0 technologies, that the makers are playing a sick demented form of Psychological Warfare on us developers.
Truth be told, it's just a way to vent about the ulcer's I get when my client, who loves opera, says "it doesn't work in opera."
Thursday, 20. July 2006, 10:39:10
opera, font, Rendering, incompatiblity
So, as we were working with em based fonts and relative percentages, we came across the interesting little fact that Opera does not render fonts the same way IE or FF does.
In the end just one more thing to drive developers up the wall with cross browser inconsistencies.
Example:
<style>
body { font-size: 1em; font-family: arial; }
</style>
<span style="background: #eee; font-size: 110%;">testing</span>
<span style="background: #eee; font-size: 120%;">testing</span>
<span style="background: #eee; font-size: 130%;">testing</span>
<span style="background: #eee; font-size: 140%;">testing</span>
<span style="background: #eee; font-size: 150%;">testing</span>
<span style="background: #eee; font-size: 160%;">testing</span>
will return the following:
(View at:
http://dev.phoenixnetworks.net/explorer/homes/guest/browser-fonts.png)Update for clarification: These were taken from three browsers on the same system, on the same resolution, at standard/default font settings in the browser.
Friday, 16. June 2006, 10:54:19
opera, browser, fails at life, table-cell
...
Apparently, Opera does not like to play nice. If you attempt to hide a
row, and then show it by setting the display to either 'block' or 'table-cell''table-row' (which are the two methods of implementation between IE and FF/Safari/Netscape) Opera will render the row incorrectly!
Chalk one up to the opera devs for screwing that up too 
Update: So we checked it out in Opera 9. 'table-cell''table-row' works for displaying hidden content, however if you attempt to display:none; it is completely screwed up.
So what this means is that the opera dev's realized that in Opera 8, they screwed up their implementation of css2.1 and the 'table-cell''table-row' property, fixed it in opera 9, but in doing so, destroyed a css1.0 display: none; property. Hurrah.
For conclusion and upon further investigation, it seems that opera has a bug with tables that arent defined a width, and as a result will shrink the table, (and not hide the row).
Saturday, 10. June 2006, 10:56:38
opera, Rendering, nightmare, CurveyCorners
It seems that developers cannot escape the nightmare that Opera engulfs them in when it comes to CSS rendering.
My latest escapades brought me to a clever and effective js utility which will allow developers to create dynamically generated rounded corners -- with backgrounds, borders, aliasing, and alpha transparency! CurveyCorners (www.curveycorners.net) is compatible with Mozilla, Firefox, and Safari.
Today, testing it with opera drove me literally insane. It seems thats whimsically and based on the alignment of the stars and spacial time anomolies, that it would render it properly. Opera would, at times render it properly, and then upon refresh render it half way.
If opera could make up it's damn mind whether or not it was going to be compatible would be nice. If it could make up it's damn mind whether or not it'd work or exhibit the same issues, would be nice for debugging.
On a side note, this is exhibited on a page that has 8 identical other boxes. 7/8 of these boxes are properly rendered, however Opera decides that just one of them must not work.
WIDGETIZE