Hi everyone, this is my first post outside DeadMenRacing section..
Recently i have moved (life forced me to it) to an area where any kind of broadband internet connection is unavailable. Before i was using Vodafone mobile connection, worked like charm on HSDPA network, d'l speed of ~3Mbit and u'l was ~satisfying :)
Now i'm still using it, but in this area only EDGE is available, d'l speed of ~200kbit. Which is...pathetic.
So i found out about latest beta build of Opera (been using firefox so far) which has this new feature called "Opera Turbo" (yeah it's name is...hmmm). Basically, all pages first go onto opera server, images are compressed to lower but acceptable quality, which effectively increases connection speed, also you have indication of how much increased the speed is, eg. 2x 3x and so on... And it REALLY IS FASTER!
But then we come to this problem, with DMW forum, regarding the way how the avatar icons are positioned... check the picture below. Anyone has an idea could this be corrected? If not, i'll live with it...
picture tells more then 1000 words of bad english (http://www.imagesforme.com/show.php/649440_deadmenracingoperapagerender.JPG)
EDIT. Sorry if i have put this into wrong section...
hi lovretta
Welcome to the 'bigger' bit of the forum :thumb:
I've just tried it in Opera 9.6.4 and the images do not wrap as you point out. :sad:
I've had a quick look in the options but can't see anything to change there to make it work. :sad: :sad:
Any Opera users out there with a working solution?
I'm going to download Opera 9 now, see if it happens for me there. Now i think it is due to this 10.00 beta build, if it turns out to be so, gonna report it to opera dev's.
About Opera
Version information
Version
10.00 Beta 3
Build
1699
/snip/
EDIT. Sorry guys for seeing this post. When i posted it, and then when i reloaded the thread few times in the next few minutes, it didn't show up. Thats why i posted the another one, the one right after this - post #4.
Then it could easily be down to this BETA version. V10.0 beta 3 build 1699.
I'm just downloading 9.6.4 and will see how that one renders DMW forum...
And if it's fine report comparison to the Opera devs :ranting2:
I can replicate the issue in Opera 9.6.4. Have tried several options but can't get it to display properly.
Will post back if I can find a solution.
I also did test with 9.6.4 (http://www.imagesforme.com/show.php/649484_deadmenracingopera964pagerender.JPG) and it is same as in 10.0 beta.
Did you find a solution? It's annoying me now... :P
FWIW - When I browse to the site using my phone, which uses Opera 4.2 mini (same server+compression approach), I have no problems...
It looks that way in Opera because the site is using non-breaking spaces ( ) to seperate the icons. Non-breaking spaces by definition should not be counted as whitespace by the browser for the purposes of deciding where to wrap content. That all other browsers do in this case is frankly unusual, but I imagine that new versions of Opera are behaving this way because they changed something in an effort to be more strict in complying to standards. So in that sense, Opera is displaying the page correctly. :)
I made this page for you test it on your browser:
http://www.facemelt.com/operatest.html
Let me know how it looks as I'm too lazy to install Opera. :)
Edit: as for a fix, switching the non-breaking spaces for actual spaces should do it.. I think.
Edit2: actually now I think about it, most browsers probably consider the end of an img tag an appropriate place to wrap content. This could well be the correct behaviour, but I can't be bothered trying to find the standard that defines this (if such a thing exists).
You are quite right boon, image looks right.
Guess it's a coding issue for Gandalf? Or just strip half a dozen badges off OldBloke and problem sorted! :D
Quote from: delanvital;287553FWIW - When I browse to the site using my phone, which uses Opera 4.2 mini (same server+compression approach), I have no problems...
I'm currently writing this with Opera Mini 4.2, compression enabled. And i got same behaviour as i do at home.
@b00n
I checked the test page, everything works as it should.
User javascripts could fix it? - http://www.opera.com/browser/tutorials/userjs/using/
QuoteTo enable user JavaScript, use Tools > Preferences > Advanced > Content > JavaScript options, and select the directory where you will put your User JavaScript files. Opera will load all files in the specified directory whose names end with .js and will use them as User JavaScript files. If a file name ends with .user.js it will be assumed to use Greasemonkey notation.
I made up a little js that might help, haven't tested it on Opera though. Copy paste the following url into your browser bar (forum doesn't like linking .js files apparently):
//www.facemelt.com/dmwoperafix.user.js
Save the file and stick it in the User Javascript folder found in the Opera Preferences above, then come back to the forums, reload the page and see if it's worked. :)
Quote from: b00n;288474User javascripts could fix it? - http://www.opera.com/browser/tutorials/userjs/using/
I made up a little js that might help, haven't tested it on Opera though. Copy paste the following url into your browser bar (forum doesn't like linking .js files apparently):
http:/www.facemelt.com/dmwoperafix.user.js
Save the file and stick it in the User Javascript folder found in the Opera Preferences above, then come back to the forums, reload the page and see if it's worked. :)
Will try it on sunday or even monday when i get back home.. I'm on a trip curently, browsing net via mobile phone with opera mini..
Thanks alot for your help!
PS. Me thinks forum does not want to link .js file because there is one '/' missing behind 'http' :norty:
Quote from: lovretta;288478Will try it on sunday or even monday when i get back home.. I'm on a trip curently, browsing net via mobile phone with opera mini..
Thanks alot for your help!
PS. Me thinks forum does not want to link .js file because there is one '/' missing behind 'http' :norty:
Yeah, that was the forum's shenannigans trying to break my links. :ranting2:
You can just right-click and save this one:
//www.facemelt.com/dmwoperafix.user.js
Btw, I just rembered...
Quoteis the entity used to represent a non-breaking space. It is essentially a standard space, the primary difference being that a browser should not break (or wrap) a line of text at the point that this occupies.
Opera actually does what it is suppose to do... Maybe replace the non-breaking space with a normal space? Or perhaps add a normal space every fourth award? Just a thought.
Oth
EDIT: Oh, an btw, didn't get your script working boon, might be just me, but this shouldn't be the way the problem is fixed... It is IMHO a error in the page, and should be treated as such. (No offense ment!)
Quote from: Othbarty;288906Btw, I just rembered...
Opera actually does what it is suppose to do... Maybe replace the non-breaking space with a normal space? Or perhaps add a normal space every fourth award? Just a thought.
Oth
EDIT: Oh, an btw, didn't get your script working boon, might be just me, but this shouldn't be the way the problem is fixed... It is IMHO a error in the page, and should be treated as such. (No offense ment!)
None taken, you are absolutely correct. :) All the script does (or is meant to do) is exactly what you have suggested - it scans the page and replaces the non-breaking spaces used to separate the awards with normal spaces (actually, it uses a different kind of space since I ran into a problem with normal spaces too, but the point is it doesn't use non-breaking ones.) It wasn't intended as a proper fix for the issue.
I am still not certain that Opera is correct in its display of the awards, although it's a very grey area. You're right that the browser shouldn't count as a place to wrap content, but in this case the content is contained within a fixed-width table cell - so is it okay to just ignore the fixed width and expand the cell like Opera does? Given that browsers have historically treated table dimensions as suggestions at best this is probably correct behaviour, but it seems clear that the other browsers choose the lesser of two evils in this case and just wrap the content.