Issues   

If you’ve any clues about these issues, have a suggestion or a workaround.. feel free to chime in.

1. IE (in)compatibility. Who’da thunk it?

Unfortunately Internet Explorer, both 7,8, just fails to work (more like: dies silently without a blip or error message, doh!). I haven’t fiddled with the code or taken extra steps to accommodate the other major browsers, it just worked.

If you are patient enough and have debugging tools for IE or know how or why this tool fails, you’re more than welcome to leave a comment.

2. Whacha doing, Flickr?

I don’t know exactly what’s going on, but Flickr seems to be doing some magic stuff. Go to a photo stream (this), fire up FireBug and paste this in :

query="sort=asc&q=Hallo+World&page=2";
query.replace(/([^=&]+)=([^&]*)/g, function(m, key, value){
    console.log(key+":"+value);
});

Click to see image in full size

Under normal circumstances the above code prints the variable pairs in the query [shown to the right ], but as seen on the screenshot, the output at Flickr is entirely different. Everything works fine on their blog without all the javascript libraries. So, am I doing it wrong or is something amiss with Flickr?..

3. Sites with outdated jQuery versions

If jQuery is already embedded into page, there’s no need to load it again, but what if that version is outdated.. then you ran into missings functions and troubles like e[prop[p]] is not a function.. so how do you compare versions?

4. Sites embedding Prototype

I’ve never used jQuery before this project. I’m using it for the sliding effect[sparsely after a rewrite] (that’s hardly any use, given it’s capabilities), but it keeps conflicting with Prototype, even tough I’am using jQuery.noConflict();


The following ones are for the CSS ninjas out there.. feel free to swoop-in in total invisibility, your mighty CSS powers will be appreciated by many.


5. Sites with absolute positioned containers

Absolute positioned top-most block elements with position:absolute, can not, to my knowledge, be forced to float and you can’t override that absolute positioning without breaking your fingers. I’ve seen few sites where the content just piles up at the center of the screen.

Why anyone would use absolute positioning instead of floating is just
beyond my comprehension… case in point.

6. Override this div.someclass{display:block}

Am using this bit of CSS to hide parent elements (direct descendants of BODY ) on the page body > div{display:none;}.., but it fails if the page contains a rule like div.foo{display:block}, which has a higher specifity, and thus overrides the newly inserted one. As a result, that container would be visible and float around.

edit: This won’t help either body > div{display:none !important}


Return to the main page or leave a comment.


RSS feed for comments on this post. TrackBack URL

What's on your mind?

Memento mori ˴.-˴.♥---   © Copyright Small labs Inc. 2009. All rights reserved.