ACID3 Browser Test

You browse the web. There are several browsers to choose from. Everyone has his/her own taste. I like Opera. Someone likes FireFox. Someone else loves the shiny new Google Chrome. Someone sitting elsewhere likes sticking with the good old IE. The availability of myriads of browsers make it difficult for the web developers to code sites because different browsers differ at some part or the another of standards support. So, the geeks, the leaders of the web technology decided to unify web standards and Web Standards Project was born. They worked and designed tests for the browsers to measure the extent of standards supported. ACID3 is the latest in the series. Click the link to benchmark your browser. Following are the scores of some top browsers tested by me on my PC and phone.

Desktop Browsers

Opera 9.63 - 85/100
IE6 - 13/100
Firefox 3.0.0.5 - 71/100
Opera Kestrel Beta2 - 100/100
Opera WinGogi - 99/100

Mobile Browsers

Opera 8.65 on P1i - 38/100
Opera Mobile 9.50 beta2 fingertouch - 73/100
Ozone - 93/100

I'm attaching some screenshots at the end of this blog post.
By the way, Opera have released a specially designed browser codenamed WinGogi that they claim, passes ACID3 by 100/100. It can be downloaded here . I tested on my PC, but it scored 99/100. May be, due to some connection blues. They claim WinGogi to be the first browser that passed ACID3 by 100/100. Source is here. On the other hand Apple claims that WebKit is the first browser engine to pass ACID3 by 100/100. Source is here. lol Whatever... By the way, Opera 10 Kestrel Beta 2 on my PC reached 100/100.

Ok, here are the screenshots.

Ozone on P1i

Opera Mobile 8.65 on P1i

Opera 10 Kestrel

Opera WinGogi

Firefox 3.0.0.5

IE6

Opera 9.63

nl2br() function in PHP

While working with the RW/LL WAP community script, I noticed a bug(???), better say unexpected behaviour in nl2br() PHP library function. I had a function for processing bbcodes. I added the nl2br() in it to convert all the enter/return presses into the xhtml <br /> tags. But I noticed, in the forum posts all other bbcodes didn't work whenever a call to nl2br() occured due to enter presses. After fiddling with a lot of sequences(which I later found to be illogical on my part) of the processing lines of codes for bbcodes and the nl2br() function, I figured out that the problem is not with my code but PHP's implementation of the nl2br() function. So, with the help of the nl2br() manual comments on php.net I wrote my own nl2br() function as follows:

function nl2br1($text){
$text=str_replace(array("\r\n", "\r", "\n"), "[br/]", $text);
return $text;
}

Well, the above function takes into concern that:
On Windows the enter key press means "\r\n",
On Linux/UNIX/BSD and other UNIX derivatives the enter key press means "\n"
and on a Mac, it is "\r\".
Probably the built in nl2br() in PHP is implemented differently, so the glitch appeared.

P1i - Opera Mobile 9.50 - SMS glitch

After the release of Opera Mobile 9.50 beta 2 Fingertouch, I've been using it a lot on my P1i for browsing for hours. I notice a strange behaviour in my P1i when I've browsed the web for long through it. My phone doesn't notify me of any SMS sent to me. Neither with the tone, nor with the icon in status bar. When I restart the phone, the new SMS is displayed. I wouldn't have noticed if I hadn't turned my phone off one night before going to bed when I was too tired. In the morning when I booted the phone back I got two SMSes that were sent to me three days ago. lol! I generally didn't use to turn the phone off for weeks. Whenever necessary I used to set it in flight mode. But now I do that every night before going to bed.
Well, a probable reason I guess is that the new Opera Mobile is a RAM hog, and when the RAM goes too low while web browsing, the phone shuts down the SMS client process that listens for SMSes, in order to free up some RAM. Whatever may be the exact reason, it should be fixed by Opera.

Opera Mobile Finfertouch for UIQ3

On 6th of this month Opera released the second beta of Opera Mobile9.50 for us UIQ users!!! Contrary to the popular feeling that UIQ is dead and Opera too will ditch it. The new beta is great! I felt some improvement in stability issues and speed in loading large pages. They also changed the logo. Earlier it looked like the power key!! And the best thing of the new beta is the new Fingertouch technology. According to Opera's official blog:

Today we introduce Opera Fingertouch, a technology designed to make interacting with the Web easier and simpler on touch-based devices. Opera Fingertouch provides visual feedback when you hit a Web link, and assists you when you come across multiple links or other selectable elements in close proximity to one another.

Here's a video released by Opera officially about the new jargon:


I tried capturing the screenshot os fingertouch in action on my P1i but it didn't work. The screen capture apps weren't able to capture the display area of the browser. Only the address bar came. I tried two different apps TOSC(the Open Screen Capture) and CS(Capture Screen), but same result. I'm attaching a screenshot anyways.