Saturday, July 16, 2011

IE's Developer's Toolbar Has Serious Problems

After spending hours and hours on debugging Prototype / Script.aculo.us "In Place Editor", I the last resort was to think that there was a conflict between IE and Prototype or Script.aculo.us.

I was relying on the Internet Explorer's Developer's toolbar, but why would it tell me that there is an error in character one on a line that starts with "<dt>"? Backing up to previous code didn't reveal a bug upstream.

So, I found "Estelle Weyl’s Blog of quirks, random thoughts and funky finds discovered in day-to-day coding" that saved any more wasted time.

Imagine if we programmers can sue M$ for wasted time... We'd each get about $1 in the settlement.


What was the answer?
"IE8 JavaScript Bug: Apparently IE8 doesn’t much care for prototype and prototip. I think it’s an issue with className that causes IE8 to choke. In the meantime, if you are using Ruby on Rails, then you’re probably using prototype.js. And, if you’re using prototype.js, then IE8 chokes, so you have to use the meta tag. And, if you use the
<meta http-equiv="X-UA-Compatible" content="IE=7" /> tag, make sure it’s the FIRST thing on your page, because IE8 suck ass, just like IE7 and IE6."

Thank you, Estelle! I'll donate my $1 settlement to your cause.

Whoever figures out these things are good at "trial-and-error" programming. I tried several directions to fix the IPE after foolishily relying on the "IE Developer's Toolbar".

I remember Bill Gates when he first started out way back then. It's too bad that such a long-lived company can't accommodate programmer's. Think about all the companies that started after his and how much better they are at providing us with what we need to program rather than chasing red herrings.


You'd think that by now M$ would wake up and give us what we need to smoothly program code for everyone, including his IE platform. Just think about it - IE is losing users while the younger ones consume the audience. If IE were to make it easier for us, maybe they wouldn't loose such a big share of the market.

W3C reports that in 2002, IE had around 83% of the market. Now, in 2011 it's a measley 23%. Of course those are mostly developers. My own site shows in 2007 that consumers 54% of visitors were on IE and in 2007, it was 74%. I recall a long time ago when over 90% of visitors had IE.

Think about that, Microsoft! Rather,
           JUST THINK!

Tuesday, June 21, 2011

Jumping BlindDown in Prototype Scriptaculous

Have a jumping blinddown?

The answer lies in the "padding" css style. I don't know if other styles interfere, but padding does.

Do not us a padding for the element that is called to blinddown. Instead, place an inner element with the padding.

Tuesday, June 14, 2011

CSS Z-INDEX - Did You Know?

Did you know that for the css style z-index to behave the element should have a position set _before the z-index is defined?
Go figure.

Wednesday, June 8, 2011

Who Says Microsoft Browsers Can Keep Up With Technology?

Okay, I've been developing the css style sheet for a new website and you know, IE is the most difficult critter. I just don't understand why Microsoft doesn't keep up with the current style sheets. I would have thought that they would be the first ones implementing CSS3 and CSS4. But no way.

First off, why doesn't IE8 have curved corners and apply transparency settings?

I've been using the good old (albeit frustrating) method of trial and error to make some discoveries, at least discoveries within my mind.

1. If you place text atop a transparent or partially transparent background, the fonts pixelate. You may not be interested in the steps I got to know that, but I first thought the fonts were not MS fonts, so they purposefully pixelate them.

Sure, I can change browser settings, but this IE8 is set to the default, and most users do not venture in to change their browser settings, at least for Clear Type and other display settings.

Then, I searched and searched the Net for answers. It annoys me when people, in their kind heart, suggest solutions without testing it themselves. So, there I went testing untested solutions that didn't work.

Now, I find out that the fonts were pixelated because I had them on a transparent backgroud - the div with the fonts were within another parent div whose background had CSS a transparency setting.

Even when the parent div had the transparency setting, the transparency carried over to the child divs  even if you use the "!important" command in the child divs.

Now, I'm onto to figure out why in tarnation some styles in an external style sheet just won't be applied. One such example is the z-index - Firefox just doesn't obey the z-index unless it's inline.

Thursday, May 26, 2011

CSS Opacity

Who said that CSS Opacity was nice? It is until you have to overlay another div tag outside the one with the opacity style to get the overlaying elements with no transparency. What a waste of coding to have so many div tags! Adding so many div tags not only increases your file size, but also makes coding even more confusing.

I use Dreamweaver to help organize the div tags, but the numerous indentations from the Source Formatting can be hard to get through. Besides, all those spaces/tabs inserted for the source formatting makes for a larger file size (slower page load).

I am strict about file size because the more space I save, the more code and nicer page I can develop.

CSS: overflow:visible Doesn't Always Work IE8 and maybe less than IE8

As most of you reading this know, browsers are pretty picky about how they display style sheets. I just found out, through trial and error, that there was a conflict with styles that was disrupting my layout.

I wanted to have an image within a div tag. The image was to extend beyond the div and be visible. (This was for AJAX reasons).

The encompassing div tag had a translucent background, shadow and curved corners.

This was working on FF4 and IE9. But IE8 cut off the image that extended beyond the div, even with "overflow:visible !important;"

The conflicting style was "filter:alpha(opacity=85);". So I had to remove that from the main CSS and put it in one of those stupid tags specifically for IE8 and less.

<!--
[if gt IE 8]>
<style>
.featured {filter:alpha(opacity=85) !important;}
</style>
<![endif]

[if !IE]>
<style>
.featured {filter:alpha(opacity=85) !important;}
</style>
<![endif]
-->


Why can't everybody play nice together? Isn't that what W3C is for?


Wednesday, February 2, 2011

Javascript, jQuery, Prototype, and the rest.

Who says that jQuery and Prototype, although both Javascript higher languages, have to get along? Look up jQuery "noConflict".

Tuesday, February 1, 2011

Who Says?

Who said that when I upgraded to the recent version of Prototype that the Accordion would quit playing?
Sigh...