Skip to main content

On IE7 Upgrade

Since I really have nothing to loose at work, where I am spending my last two weeks (I gave a notice on Monday), I have upgraded to IE7. After that I have spent two hours, trying to figure out, why my website makes IE7 crash. I finally did, but damn, that was entertaining.
It looks like document.open('text/html','replace') needed to loose the replace argument, document.writeln() can not be used for writing links to external scripts, the address bar is not removable anymore, and window.resizeTo() doesn't want to work (that pretty much disables all my portfolio galleries).
Lovely. What was even more annoying, is that IE would work with .html files, if they were opened locally, but crash, when opening the exact same files from the server.
So much for the upgrade.
All other imaginable browsers do display my site correctly, with little or no problems. Even Opera.

P.S. During the fixing fit, I removed the reflection.js script---which wasn't mine anyway, I was just playing with it.

Popular posts from this blog

WordPress: How to add custom fonts to a twenty seventeen child theme.

Quick help to those who have tried to find some help and failed (as I have so I have to write the code myself). Assuming that you have your virgin child theme configured and activated: here is a function which goes into the functions.php file (of your configured and activated child theme): function childtheme_twentyseventeen_fonts_url() { $replace_original_font = true; // unless you really like Libre Franklin if ($replace_original_font !== true) { $hyph = '-custom-'; } else { $hyph = '-'; }; $font_families = array( //add your Google fonts and weights (400 and 700 are defaults for normal and bold) here: 'Oswald:200,400,700', 'Lato:200,400,700', ); $query_args = array( 'family' => urlencode( implode( '|', $font_families ) ), 'subset' => urlencode( 'latin,latin-ext' ), ); $fonts_url = add_query_arg( $query_args, 'https://fonts.googleapis.com/css' ); wp_enqueue_style( 'twentyseventeen' ....

How to Make a Website Everyone Has

On The Endless Wonders Of Internet Explorer

May be somebody will stumble upon this post and save some time for him/herself. Apparently—it only become apparent after several hours of trial, cursing and error, as it usually goes with IE—, Internet Explorer (up to version 7) throws a runtime error, if you try to modify innerHTML of the dynamically created element under certain conditions. The conditions, as it always go with IE, are significantly lacking consistent logic. For starters, if you assign innerHTML to the element before you insert it into a DOM tree, the error may not come up at all, but will surface later, when you try to modify it. So far it looks like the error mostly comes up, if you change innerHTML of the block element inserted into inline element (which is not kosher in standard-compliant HTML, so it makes sense), and some nested block elements (like DIVs inside Ps—why is that considered wrong, too?—for instance). So, if one really-really need to insert a division into a paragraph, and w...