It doesn't even support inline SVG, which is The crux of Rigby's argument - that Sony would be using SVG for everything. Kind of difficult when your SVG support is worse than IE9's.
The Xperia Play's browser is better than this, leagues better.
Sony on the PS3 and Vita is using OpenVG (SVG) for almost everything (Pixman is being used too), Flash 9 support is using OpenVG (SVG) for rendering.
The Vita and PS3 browser backends are a modified version of GTKwebkit2 version 1.7 (Jan 2012) and the Webkit2 APIs for SVG and many other features are not done.
Yes the Xperia browser on Android does have more features and it was rewritten by Sony-Erricson to support WebGL, Androids browser did not support WebGL and was not in strict compliance with webkit.
I've explained my guess as to why Sony went with GTKwebkit2 as the basis for the browser in the Vita and PS3....it's because they can
manipulate Gstreamer VIDEO with Cairo (Augmented Reality coming Sept 2012) and it's a standard across multiple platforms including their TVs and Blu-ray players. This is why Cairo was disclosed at the same time as the browser Feb 2011 but it appears as though they are not using Cairo YET for the browser.
Again, I've stated this is not a finished browser on the PS3 or Vita; SVG, HTML5 <video> and WebGL are coming. From message 438
The current implementation of the PS3 browser is not OpenGL accelerated! ; CairoGL is not being used. Cairo-Pixman as in the combined library to support webkit is OpenGL accelerated, Pixman listed by it'self is apparently not accelerated and is using PPU code only.
If Sony's PS3 disclosures are accurate, Sony is using the AVM+ Open Source (they can only use it for non-commercial applications) Adobe flash player (with OpenVG) to support DASH IPTV player functionality for Home. This would explain Sony not using IPTV for commercial use till either Gstreamer 1.0 is done, PROVED secure and they disclose it or they decide to pay Adobe for the commercial use of AVM+. That Sony has a DASH player as seen with Home on the PS3 but is not using it for commercial IPTV themselves makes me believe that Gstreamer is the first choice, a choice so critical that they will delay implementing their entire ecosystem and the money to be made from it until Gstreamer 1.0 is finished.
I assume they want WebGL, accelerated codecs and video manipulation with CairoGL (Cairo-Pixman) which is necessary for zooming into video streams (Playmemories Studio). So it's Gstreamer and Cairo SPU-RSX accelerated support or Something they will have to write themselves and constantly upgrade. (can't use AVM+ without disclosing to Adobe or Pay Adobe for it's use).
Read
http://www.neogaf.com/forum/showpost.php?p=37023526&postcount=1309 then
http://www.neogaf.com/forum/showpost.php?p=37062140&postcount=1319
My guess is PS Suite's player will be Gstreamer with Cairo bindings to support AR (a PS Suite developer mentioned that codec support is coming, probably via OpenMax, which implies a native player is coming); that is unless Google provides a better player for Android ICS but then Codecs would not be needed.
Edit: "From a brief look at OpenVG, there seeem to be chips that support hardware OpenVG and not hardware OpenGL. That seems to be much of the point of OpenVG: So low-end devices can accelerate graphics, without being powerful GL-capable GPUs. As far as I can tell, those chips are used only in phones, not desktops." OpenVG is simpler, like a subset of Cairo and requires fewer resources while giving SVG benefits to the XMB. CairoGL (as used in GTKwebkit is Pixman-Cairo-Glitz) with Gstreamer bindings will be needed by Augmented Reality, a WebGL browser and can be used to manipulate pictures and video.
So the version of webkit we have now is probably the smallest and requires the least support (native libraries). Some form of this version may be seen intact as a basis for in-game browser support on both Vita and PS3. There is no CairoGL, no modified GTK toolkit and Gstreamer which require Glib. OpenVG is already being used by the XMB and can be used to support this version of webkit without using more in game memory. OpenVG can not be used to support WebGL, W3C SVG or Gstreamer with Cairo bindings for HTML5 <video>. Edit:
OpenVG in the application side would be used to create pixel version of fonts and graphics as cached bitmapped images and then Pixman would be used to display and manipulate the graphics images
Utako; does this now make sense to you?
This version of webkit for a game console (Vita and PS3) was in hind sight predictable. It is not (now debatable point again) the final Browser version but might be the final in-game version. My opinion is that W3C SVG support is coming as we have seen PSN SVG menus, WebGL and HTML5 <video> support for the ability to view 3-D video which we were told is coming.
The big difference to come IN MY OPINION is in-game XMB will be OpenVG (no change) and the application side XMB will be CairoGL (Changed from OpenVG and Pixman) with webkit and support libraries always loaded or partially loaded with some, FAST and easily swapped via a special reserved portion of the Hard disk on the PS3.
The above would then support what Gnome desktop, Chrome OS and other OS are doing; Browser desktops with RIAs. Maximum use of the same libraries allowing for Zero copy and resource efficiency.
Oh, one of the reasons the current browser appears to load so fast and does not require the XMB to reboot on exit is that the XMB is already using OpenVG and Pixman so the browser NOW does not require they be reloaded. When we move to SVG or WebGL or a more full featured HTML5 the application side XMB will probably be CairoGL.
Why is a game warning message now seen for the first time on the application side XMB after 4.10? Games and active screens that might cause the same issues will be seen shortly in the application side of the XMB. Games already have warning messages so the first post boot warning is redundant for current games. Coming to the application side XMB; 3-D for the XMB, WebGL games, 3-D viewing from the browser, 3-D picture and video including home video, Augmented Reality including on-line Web etc. which, to be safe, would require a warning message for the entire Application side XMB.
To this point I've duplicated some of
http://www.neogaf.com/forum/showthread.php?t=402172 in this thread. In the future I'll post simple conclusions in this thread and supporting information in the other thread. I hope this will keep people from thinking I'm trying to " hijack" threads.
Again, I have no insider information and what I am posting is obvious for the most part and is now partially hindsight. We are over the hump as a Webkit browser has been released though it's a very minimal version with few advanced features. From this point forward it gets exciting.
This OpenMax 2007 Powerpoint gives an overview of 1.1 and what's coming with OpenMax 1.2 (Clicking downloads a PPT file). It sets the stage with support for middleware for PS3 firmware releases from 2007, what's been released in 3.0 (2009) - 3.5 (Sept 2010) - 4.0 and this year with the recently released OpenMax 1.2 through 5.0 (Sept 2012 Augmented reality coming Sept of this year).