Wednesday, November 12
Firefox and my bad coding habits.
I've been using target="_new" in my Links to Monitor. I've been noticing that if I left click one of those links especially in a different window, it was overwriting a window. Turns out I have been cheating. _new used to work like that, but Firefox 3 has tightened the screws down a bit. _new isn't a generic name, it's now one specific name. What I needed to be using was the _blank, which opens up a new blank window/tab. I'd love to be able to also force a tab or a new window, but I guess that's asking too much. It may be possible with javascript, but I don't feel like going that route.
So today I got my Links to Monitor fixed and should (note should) have every _new replaced with _blank. I thought I had everything covered, but I still had a couple to modify in my template. So I'll let Google index everything and then I'll see if I'm still using it on the bryanlprice.com site, and then once I'm sure I've got it fixed, I'll go after bytehead.org, which will be much more work.
Update: More work on my template and including files. Including Blogger directives doesn't work unless they're in the template, not the included files. And a few more &s get translated to &s. And publishing this will at least fix the front page. Permanent link posted by bytehead @ 11/12/2008 04:02:00 PM
1 comments
Links to this post
1 Comments:
I'm down to warnings, most of which are generated by Blogger's code that I can't touch (comment link needs to have the &s &ed.) And something about empty br's and p's. Which I get in my Links to Monitor. That might be an option to kill in the HTML Tidy.
