Lemmings 404 page

503 (Unavailable) is more suitable for that I guess.

2) I made an assumption, based on the context, that this page was serving a role that is used when the server is overloaded or otherwise unavailable. In that case, this page should not be serving a 200 status, it should be serving a 50X response.

Now, it's possible that this page is just a demonstration of the error that would normally be produced when the website is unavailable. In that case, sure, 200 status is proper since it's not meant to actually be the literal error page which is served when the site has gone down. It's also possible the page has logic in it to serve 200 error when requested directly and 50X when the server is down.

In really, I bet this page is served as-is when the website is unavailable and sends a 200 error. It's difficult to know whether or not this is true until we see a real problem with the server.

I read it as the first, and had this immediate reaction:

- I'd rather write the 1 line of jQuery over the 6 in vanilla javascript

- I'd rather read the 1 line of jQuery to understand what is going on instead of the 6 in vanilla javascript

- jQuery didn't actually impact your experience much... as you didn't realize it might even be available.

    var event = document.createEvent("MouseEvent");
    event.initMouseEvent("mouseover", true, true, window);

    function save_them_prontos(){
        var ims = document.getElementsByTagName('img');

        for(var i=0;i<ims.length; i++){
            if(ims[i].id == ''){
               ims[i].id = i;
               ims[i].dispatchEvent(event);
            }
        }
        time_dem();
    }


    function time_dem(){
        window.setTimeout(function(){
            save_them_prontos();
        },100)
    }

    save_them_prontos();

Same, but nicer, listens to mouseover events on img elements that may not exist yet. Then again, this will - if I understand correctly - cause the event to bubble up in the DOM until it reaches the root element, where jquery's live callback handler will check what element the event took place on and invoke that callback.

    var evt = document.createEvent("MouseEvent");
    evt.initMouseEvent("mouseover", true, true, window,
      0, 0, 0, 0, 0, false, false, false, false, 0, null);

    function isALemming(node) {
      return node.nodeName === 'IMG';
    }
    function fakeMouseover(node) {
      node.dispatchEvent(evt);
    }
    
    function saveLemmings(possibleLemmings) {
      possibleLemmings.filter(isALemming).forEach(fakeMouseover);
    }
    
    var observer = new MutationObserver(function(mutations) {
      mutations.forEach(function(record) {
        saveLemmings(Array.prototype.slice.call(record.addedNodes || []));
      });
    });
    saveLemmings(Array.prototype.slice.call(document.getElementsByTagName('img')));
    observer.observe(document.body, { childList: true });