Skip to main content

Another Day At The Office

How come the emergency fire drill always starts when you (quite unexpectedly) feel like working?
I just figured out that "page contains both secure and insecure items" warning only pops up on the pages, where I have dynamically generated <iframe> with the src attribute set to "about:blank". The idiot browser (IE|Win) thinks that it is a reference to something outside the secure server domain.
The nastiest part of the "procedure" is the siren, which never stops, followed by the incredible annoying male voice, repeating over and over "...you are in a safe area... prepair to receive evacuees......you are in a safe area... prepair to receive evacuees...".
What a splendid word: "evacuee".
There went my inspiration for today. Well, I did fix the security bug...
Oh, yea: zeldman.com is now blocked by the Smart Filter as well.

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' ....
Read more

How to Make a Website Everyone Has

Read more

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...
Read more