
| Guardian | ROP: Woolwich killing: universities crack down on the preachers of hate |
0 |
| Ryan Lizza | Disturbing: How Prosecutors Fought to Keep Rosen’s Warrant Secret |
0 |
| NJ Online | Ick: Rubbing alcohol as scotch? N.J. officials release details of ‘Operation Swill’ |
0 |
| Kim Strassel | 0 | |
| WaPo | 0 |
I’m doing a little tweaking tonight to try and fix a few minor bugs, and will probably head to bed after that. Catch ya’ll tomorrow.
Update: After trying to fix it tonight with no success, I’ve emailed the creator of the comments editor plug-in and let him know that the plug-in is not functioning right in IE (it works fine in Firefox). Hopefully I’ll hear back from him soon.
Also, I’m interested in hearing from any bloggers out there who use font size changers on their blogs. I’m getting mostly positive comments about the font size, but a few people have told me it’s showing up very small on their screens. I tried installing one tonight but could not get it to show up directly on the blog. I suspect the issue I was having had something to do with not knowing what to put in the “DIV” and “interval” sections of the plug-in settings. Any advice would be appreciated ![]()
Fri AM Update – 9:21 AM: I have disabled the comment editor feature for the time being. It was being very buggy this morning. If I can’t get the issues we were having with it resolved via the creator of the plug-in, I’ll see about finding and installing another one, as I know that was a popular function on the blog.
RSS feed for comments on this post.
File this under “Bringing us altogether”:
And he says it with such eloquence. So this is apparently Barack working with the opposition party. Them trying to hold him to his campaign “promise”, and his response is to basically tell them to deal with it. Nice. – Lorica
I am using that one from Rodenas, there is some trick to it, I think it has to do with how the sizes are used. If I remember correctly, you have to use em instead of pxl. Most of the other lines in my Stylesheet use pxl, but, I changed just the one for text in the entries to
h1.entry {
font-size:1.02em;
color:#000;
font-weight:normal;
}
Which works well for me, the size never gets as big as it shows in the comments here. Had to play with the sizing a bit to get it jussssst right for the default, which I have as the smallest size, which I like, while others like a bit bigger.
Then have something in the Main Index and Single Post files for that, like
[h1 class="entry"?] [php the_content('Read the rest of this entry »'); ?] [/h1] (changed all the to [ and ], so you could see.)
I’m really hoping that code doesn’t hose you comments in this post beyond what I see in the preview
Have no idea about editing.
But fonts – well….
In IE the font on the main page shows up at a decent size: I checked and it is the same size using Firefox.
In comments, typing in a new comment also uses a good sized font. But in IE comments already posted show up in the tiny font size I dislike so vrulently on so many blogs. Firefox seems to use the same font sizes for both as the main page. Weird… CSS handling?
- – - –
Some may wonder why I still use IE in preference to Firefox.
In a word: bookmarks.
I have over two thousand of them. I break them into folders and sub-folders, mostly under eighty each.
IE remembers the last bookmark clicked (per window) and repositions to that place (saving my having to drill down from folder to subfolder to subsubfolder to [next] single entry) when I open bookmarks to click on a new one. Firefox starts from scratch every time. And Firefox does not even distinguish between folders and plain bookmarks i.e. does not put folders at top but rather intersperses them.
teqjack, the differences in browsers can driva ya crazy! I know it does me, especially when it comes to wanting to make sure everything works right.
The funnest part is developing a theme. One time, I spent about 5 hours tearing a really cool one up and putting it back together. I do all my WordPress stuff using IE, usually find it easier. But, I was looking at the developed site in Firefox, which acts just a wee bit different. Got it all done, and realized it was really slow in IE. Sigh.