I haven't been doing much web stuff lately but there is this...

Pretty much sums it all up...

Not too shiny...

Ok we all know how I feel about IE right? Well in a close second is Chrome. When it first came out it was nigh-useless for someone who does webdesign. It was missing some basic stuff like oh I dunno.. view source. (Which I think they fixed.) This put me off Chrome instantly.

To this day I continue to not like it. Chrome is like that kid in your school who you just didn't like. For no real reason. You just... didn't.

Well there is a damn good reason for me to want to give Chrome a big ol' wedgie. It seems to render some things a few pixels off. I discovered this after getting something to look and work fine in Fire Fox and, anubis help me, IE9. (I'm afraid to look at 7 or 8 right now. As for anyone using IE6 you can suck it and hard.) Anywho, in Safari (Grrr) and Chrome the div layer was 2 pixels off which was totally obvious because of the way a certain layer needed to be made.

As usual I turn to the intertubes for an answer. Also, as usual, it took me at LEAST an hour to find an answer that didn't take a translator in technical speak to decipher. My usual gripe is the fact that someone has to get mad enough to write a script that fixes something that shouldn't exist in the first place. Thankfully someone did.

So, I'm sorry Chrome, but we can't be friends. I just don't like you.

Easy Ease

So I have been toying with the Fancybox overlay lightbox clone. (personally I prefer shadowbox but it performs less than stellar on a mobile device right now)

I updated to the newest version for a little tweaking I am doing on my store site. I always try new stuff in a temp folder just in case. I copy and pasted the code exactly how they tell you to off the website. It looks the same as the old version save for one folder in the paths and the version number. However IT WOULD NOT WORK! No matter what I tried. It worked fine with the old version. (I say old it's 2.0.3 to 2.0.5)

Finally after getting some donuts from that crazy Cambodian place and an hour of wanting to stab my monitor with a pizza cutter I thought "Hey let's delete this backslash (/) in front of the paths because I am out of options and sanity". Guess what. IT FUCKING WORKED AFTER THAT!

The old version it worked fine with the "/" in front of the path. That is exactly what they show on the examples on the website AND the instructions. However as soon as it got on my server all logic went out the damn window.

What possible functionality BS change is this? I don't get it at all. Just don't get me started on the easing in animation. I needed extra code to make that work.

Hey Developers: when you "improve" something it's supposed to be an IMPROVEMENT!

I'm gonna eat more jungle donuts now...

HTML Fuuuuuuuuuuuuu......

Does anyone else think it's ridiculous you have to have THREE video formats to get html5 to work on everything. Two of the formats are nothing you have heard of (unless you have had to deal with it already) and the third, which is .h264, you better hope you encode it right or else IE will just laugh at you.

Miro converter is suggested to make an .mp4 that will work as a flash fallback but hey guess what... it doesn't seem to.

It's all so damn frustrating.

I promise...

This will not turn into Tumblr. This however is funny and true.

Doing lines...

I find it so very odd that hours of frustration can pass without notice in the pursuit of that one tiny string of alphanumeric bliss.

One tiny thing can be out of place and NOTHING works. It then takes an hour or more to realize... that's not a semi-colon. Damn.

Today's frustration is brought to you by the letter .PNG click thru transparency and the letter ARRRRGH!!!

Closed captioning provided by fluid layouts are not for artistic sites.