Linked by Eugenia Loli on Tue 28th Nov 2006 19:25 UTC, submitted by JATF
Opera Software Opera Mini 3.0 was released today (get it here). Major new features include camera support, RSS feed reader, SSL and https support, content folding, and speed improvements. Screenshot here. Today we also celebrate here at OSNews the first hits of the Opera-based Wii browser (via a proxy hack to allow generic web browsing) and the Sony PS3 browser. We would be grateful if you could snap a picture of your TV with your gaming console rendering OSNews and send us an email with it or post a link below.
Thread beginning with comment 186316
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: W3C?
by Sphinx on Tue 28th Nov 2006 23:22 UTC in reply to "RE: W3C?"
Sphinx
Member since:
2005-07-09

Try http://gp2x.fullsack.com

Looks like it reads the processor directives and thinks the browser has to perform the server side xsl transformation.

Reply Parent Score: 1

RE[3]: W3C?
by Eugenia on Tue 28th Nov 2006 23:27 in reply to "RE[2]: W3C?"
Eugenia Member since:
2005-06-28

It does not work. It doesn't give an XSLT error as Opera Desktop does, but the kind of rendering Mini does is equally useless. The error says that this page uses Ajax and JS and therefore it can't work on this browser.

I also tried your page with Openwave's mobile browser and that also failed in a similar way Opera Desktop did. It gave a full screen error of "unsupported content type".

Maybe you want to code your pages using more conventional methods so all browsers are compatible.

Reply Parent Score: 1

RE[4]: W3C?
by Sphinx on Wed 29th Nov 2006 00:37 in reply to "RE[3]: W3C?"
Sphinx Member since:
2005-07-09

Thanks but I think it's better to wait for browsers to catch up. Dumbing down sites rips the fun right out of building them. Haven't you ever heard, "If you build it they will come."? Hey somebody has to build it.
No commercial interest and way more than a bit on the experimental side anyway, still evolving.

Reply Parent Score: 1

RE[3]: W3C?
by brain on Wed 29th Nov 2006 00:51 in reply to "RE[2]: W3C?"
brain Member since:
2006-11-07

Well, the W3C reports "This page is not Valid XML!". So don't be surprised when it doesn't work in all browsers. Follow the standards.

Reply Parent Score: 2

RE[4]: W3C?
by grfgguvf on Wed 29th Nov 2006 07:20 in reply to "RE[3]: W3C?"
grfgguvf Member since:
2006-09-25

Actually if you look at that page's code, it's totally correct.

The W3C validator has a lots of bugs so you shouldn't rely on it to determine if sites are standards-compliant or not.

Reply Parent Score: 2

RE[4]: W3C?
by fignew on Wed 29th Nov 2006 05:47 in reply to "RE[2]: W3C?"
fignew Member since:
2006-09-06

Also does not work in Konqueror. I don't think Konq. supports XSLT at all yet. ;)

Reply Parent Score: 2

RE[5]: W3C?
by ValiantSoul on Wed 29th Nov 2006 07:42 in reply to "RE[4]: W3C?"
ValiantSoul Member since:
2005-07-20

It slightly works in Safari (but the content says it uses AJAX and JS and doesn't show) however the latest build of WebKit does work. As long as people are merging changes back to Konquerer, it should work soon.

Reply Parent Score: 2

RE[3]: W3C?
by grfgguvf on Wed 29th Nov 2006 07:22 in reply to "RE[2]: W3C?"
grfgguvf Member since:
2006-09-25

Even if your site works in Firefox 2, it still breaks basic user expectations about the interface.

For example pages on a site should be linkable. Usually the trick is to modify location.hash and check it on load.

Reply Parent Score: 2

RE[4]: W3C?
by Sphinx on Wed 29th Nov 2006 14:41 in reply to "RE[3]: W3C?"
Sphinx Member since:
2005-07-09

I will play around with that, was just thinking on how to make that work last night, thanks again.

Reply Parent Score: 2