Skip navigation.

My Opera News

Behind the scenes at My Opera community

HTML changes

, , ,

We're about to release a new version of My Opera. The release contains some HTML changes. This might affect you if you have written your own custom CSS, but the changes are moderate and it should be fairly easy to adjust the CSS.

The first thing we did was to switch from XHTML to HTML. Yes, we believe that HTML is the way to go and we finally got rid of that xml prologue that caused "some old browsers" to go into quirks mode. You will also notice that it's now somewhat easier to read the code when you view the source.

You do not need to edit any XHTML content that you might have included in your old posts - it will automatically be transformed to HTML when the page is rendered.

For most blog themes we have also moved the #myo menu div inside the #wrap3 div. This means that the My Opera top menu will be as wide as your page, instead of stretching over the entire browser window. (there are a few blog themes that still have the #myo div outside the wrapping div's)

Blog sidebar

For the new My Opera we wanted to standardize the image sizes. We used to have 29 different sizes for each user photo! This was way too much and we now have only 4. This made us update the HTML/CSS to fit better with the new images.

The standard width for the sidebar is now 240 px.

The image sizes for the friends list in the sidebar used to be 102x77. It's now 104x78.

The images sizes for the latest comments used to be 45x43. It's now 40x30.

The images sizes for the recent visitors used to be 64x48. It's now 68x51.

Friends

The image sizes for the friends page used to be 169x127. It's now 104x78. The location field was also removed to simplify the page.

Photo albums

Changes have been made to the photo albums code. In essence we have made it into a list rather than just div's.

Photo albums overview. OLD code:

  1. <div class="albums">
  2. <div class="album1">
  3. <div class="albumthumb1">
  4. <a href="#">
  5. <img src="#" width="160" height="120" alt="" class="albumimage" />
  6. </a>
  7. </div>
  8. <div class="albumnfo">
  9. <h3><a href="#">Title</a></h3>
  10. <p class="imagecount"><b>Images:</b> xx</p>
  11. <div class="albdesc">Description</div>
  12. </div>
  13. <div class="clear"> </div>
  14. </div>
  15. <div class="album2">
  16. <div class="albumthumb2">
  17. <a href="#">
  18. <img src="#" width="160" height="120" alt="" class="albumimage" />
  19. </a>
  20. </div>
  21. <div class="albumnfo">
  22. <h3><a href="#">Title</a></h3>
  23. <p class="imagecount"><b>Images:</b> xx</p>
  24. <div class="albdesc">Description</div>
  25. </div>
  26. <div class="clear"> </div>
  27. </div>
  28. </div>

Photo albums overview. NEW code:

  1. <ul class="nobullets" id="albums">
  2. <li class="album1">
  3. <a href="#" class="albumimage">
  4. <img src="#" width="280" height="210" alt="">
  5. </a>
  6. <h3><a href="#">Description</a></h3>
  7. <p class="imagecount"><b>Images:</b> xx</p>
  8. <div class="albdesc">Description</div>
  9. </li>
  10. <li class="album2">
  11. <a href="#" class="albumimage">
  12. <img src="#" width="280" height="210" alt="">
  13. </a>
  14. <h3><a href="#">Description</a></h3>
  15. <p class="imagecount"><b>Images:</b> xx</p>
  16. <div class="albdesc">Description</div>
  17. </li>
  18. </ul>

Photo album view. OLD code:

  1. <div id="mypix">
  2. <div class="thumb1">
  3. <div>
  4. <a href="#"><img src="#" alt="" width="320" height="240" /></a>
  5. </div>
  6. <p class="photoinfo right photocomments">
  7. <a href="#">x comments</a>
  8. </p>
  9. <p class="photoinfo photoviews">
  10. xx views
  11. </p>
  12. </div>
  13. </div>
  14. <div class="thumb2">
  15. <div>
  16. <a href="#"><img src="#" alt="" width="320" height="240" /></a>
  17. </div>
  18. <p class="photoinfo right photocomments">
  19. <a href="#">x comments</a>
  20. </p>
  21. <p class="photoinfo photoviews">
  22. xx views
  23. </p>
  24. </div>
  25. </div>
  26. </div>

Photo album view. NEW code:

  1. <ul class="nobullets" id="mypix">
  2. <li class="pic1">
  3. <a href="#" class="thumb"><img src="#" alt="" width="320" height="240"></a>
  4. <p class="photoinfo right photocomments">
  5. <a href="#">x comments</a>
  6. </p>
  7. <p class="photoinfo photoviews">
  8. xx views
  9. </p>
  10. </li>
  11. <li class="pic2">
  12. <a href="#" class="thumb"><img src="#" alt="" width="320" height="240"></a>
  13. <p class="photoinfo right photocomments">
  14. <a href="#">x comments</a>
  15. </p>
  16. <p class="photoinfo photoviews">
  17. xx views
  18. </p>
  19. </li>
  20. </ul>

Testing, testing, ...The new My Opera

Comments

coxy 17. November 2008, 13:11

Informative. This is going to come in useful for when you break my blog code! :D I guess the update just gives me an excuse to do the CSS on my blog properly, for once!

Chas4 17. November 2008, 13:53

new MyOpera soon :smile:

Tamil 17. November 2008, 14:31

Thanks.

Furie 17. November 2008, 14:52

Cheers for the heads up.

Quinnuendo 17. November 2008, 17:19

usefull indeed. there are a few blogs I customized, and they will maybe need some tuning.

LorenzoCelsi 17. November 2008, 18:18

What kind of HTML are you using and why?

fred 17. November 2008, 18:44

HTML 4.01 Strict at the moment because our current parser did not allow us to just use HTML as doctype, but we want to go with HTML 5 in a while of course.

LorenzoCelsi 17. November 2008, 18:52

I thought that.
Besides the "new" tags introduced in HTML5, I don't get the purpose of it or maybe I should say I don't get why the W3C made us move to XHTML (with a strict syntax, which is good) and then go back to HTML (no XML, no mudules, tags omitted, commas omitted, etc). Did you get the master plan I am missing? :smile:

fred 17. November 2008, 19:10

I guess they just realised that XHTML did not take off, that most sites still don't validate, and that it's better to go with HTML 5. :smile:

Tabmartel 17. November 2008, 21:08

I can't wait!

Khadgar 17. November 2008, 21:41

:faint: :coffee:

Ick thought I'd have a bit longer to work on N+! Coding spree tonight!

Chas4 17. November 2008, 22:11

Khadgar I send you a digital pizza to help you get you thru the Coding spree :wink:

Khadgar 17. November 2008, 23:10

Haha. As the test server's password has been changed I won't get to do it until it's broken when the new My Opera rolls out.

DBabbit 18. November 2008, 04:24

Thanks for the heads up! :up:

kembangp3t3 18. November 2008, 05:12

Hmm... :cool:

SouthernCross 19. November 2008, 02:49

:sherlock: So, is the new banner width 961 now? :eyes:

fred 19. November 2008, 09:41

Southern Cross, that's only for the red Opera design.

SouthernCross 19. November 2008, 13:39

:wizard: Ah, OK. Thanks for the info.

hzr 20. November 2008, 12:14

@fred, I guess you can output the HTML 5 doctype with

<xsl:text disable-output-escaping="yes">&lt;doctype html></xsl:text>

instead of using <xsl:output/> (if your XSLT processor supports that).

infinity-1 29. November 2008, 18:10

I agree with ditching XHTML since it's a dead end and most sites that claim XHTML either don't validate or are rendered in quirks mode or both. However as usual I'm going to have to fix my blog CSS which is broken by the changes! If only we had backwards compatibility!

Ugh, well I've done my best, my blog looks crappy but at least it doesn't look like total shit, these changes are why people move to other blogging sites frankly, it would be easier to start over than to deal with the carnage that the updates cause to your carefully crafted CSS!

DBabbit 4. December 2008, 10:49

I noticed my CSS had changed and after about a week, it went back exactly as I'd had written it, and I didn't change it. I think we just had to wait on a few minor bugs to be worked out. I am :happy: ! :hat:

Furie 4. December 2008, 10:51

May have to reupload my own. :sherlock: When did it change back?

DBabbit 4. December 2008, 11:26

About a week after the new version came out.

Write a comment

You must be logged in to write a comment. If you're not a registered member, please sign up.