Sep 07 2007

Json.test() for mootools

Tag: Javascript, Mootools, Web developmentJens @ 11:25 am

I wrote a small extension to the Json class in mootools, to check if a string is valid Json format.
Continue reading “Json.test() for mootools”


Sep 05 2007

$get() for mootools, reading get variables

Tag: Javascript, Mootools, Web developmentJens @ 6:21 pm

In a project at work we had the need for tampering with href’s and other url’s with JavaScript.
And beeing a mootools fanatic, I chose mootools as the framework to build my sollution on.

My general idea was to create a generic function to read the get variables from any given url, with the current location.href as default. And also be able to return the element anchor if set. This would come in handy if we ever needed to rewrite url’s before opening them with ajax or in an iframe, and to read get variables in javascript.
Continue reading “$get() for mootools, reading get variables”


Sep 05 2007

Empty src attribute on <img> is the devil!

Tag: (X)HTML, Web developmentJens @ 5:57 pm

.. at least when combined with Firefox.

To make a short story long, here’s the full story :p
The last few days at work has been a battle of the rare and unpredictable.
A weird bug in our latest project made my team go crazy (you know, the BAD kind of crazy),
and it was a Firefox only bug. oO

It started off when our “report this” feature returned double reports, one with the POST based (non-required) input, and then another one with only the GET variables (id, required value).

This got us all fuzzed and put our brains to the test. Loading our favourite Web debugger tool (firebug anyone?), we saw that Firefox added another GET request for each and every page on our site. That was odd, very odd.

Searching for an answear, we started checking all the pages, each and every one, and it appeared that the double requests happened on all pages, but only when the user was logged in.
So naturaly, we started looking at the login process. Session management anyone?

And if you read the title right, the session road was a dead end road.. a long and tidious dead end road that is..

And after a few hours with firebug, http header monitor, calling the hosting company, and all that fuzz… I updated our user-navigation menu, adding an icon where the src attribute was empty, and guess what.. Suddenly, NO MORE DOUBLE GET REQUESTS!

So that was it, an empty src=”" made calls back to the same page (much like a missing action attribute for forms or empty action=”" loads the same page on submit).

[ratings]





Warning: stristr() [function.stristr]: Empty delimiter in /home/asocialp/public_html/wp-content/plugins/wassup/wassup.php on line 2093