Solo Technology

Uh oh, are my Opera fan-boi days over soon? I noticed an odd rendering bug of some sort recently while navigating through my blog. When using Opera, the prev/next links at the bottom of my pages don't work. Yet in FF and IE they do. If I edit source and copy the url from the links into the address bar, things work fine. Wierd. Here's an example of what is rendered:

Looks normal, eh? The pages validate too. You'll see the link. It'll even be the proper link color. But noooo clickie. Can't click at all. Far out.

I'll have to surf some other blogs and look for similar examples. Maybe something is not quite right with my theme here? Or maybe it truly is an odd bug. Boy, Rich is going to enjoy reading this one...

7 Responses to “Opera rendering bug?”

1. Rich G. on June 29th, 2006 11:25 pm
   

   Not that I’m counting, but the last 4 of 5 Opera posts by you were all about how it doesn’t work for sites.

   http://www.solo-technology.com/blog/tag/opera

   Is the source of my tally, and until you blog a positive about Opera it’s only going to get worse. Statistically speaking I mean.

2. Joe on July 7th, 2006 3:50 pm
   

   Well, as far as I can tell your still using Opera(http://wordpress.org/support/topic/78636?replies=4#post-406760) and Firefox and Opera are having the same bug. But any way what plugin did you use for your view script box? Thanks…

3. chris on July 7th, 2006 4:30 pm
   

   Hey Joe. Right now I’m pretty much one-third each for FF, IE7 and Opera. Decisive, I’m not!

4. Joe on July 8th, 2006 5:46 pm
   

   What were you using to display the code. Yesterday it showed the view text or view html option. I was wondering what you used to do that. Thanks…

5. chris on July 8th, 2006 6:24 pm
   

   Ah, I gotcha. Misunderstood the question.
   That plugin is iG:SyntaxHiliter and you can find it at: http://blog.igeek.info/wp-plugins/igsyntax-hiliter/

6. Joe on July 17th, 2006 5:33 pm
   

   Bolth questions were asked.

7. Chris on September 22nd, 2006 9:46 pm
   

   I’m pleased to say this has been resolved with a bit of CSS adjustment. See this WordPress support thread for details.

Leave a Reply