We now support Chromium as a secondary Web rendering engine! It is faster than our standard web viewer and can optionally provide limited support for Flash.

Only restriction is that Chromium cannot be rendered on top of video Playlists or other overlays. We plan to change that really soon.

Keep in mind that Chromium is much heavier and resource-hungry than standard Web Viewer. You should always try the standard web viewer first, if possible. Having multiple Playlist on screen using Chromium can place a lot of load on your Player and can cause trouble in the long-run.

We use the standard Raspbian web engine (Webkit) which has been optimized for the Pi. We have integrating a second web engine (Chromium). It Is on beta now. Only restriction is that Chromium cannot be placed on top of video Playlists.

Note that sites with heavy animations will always suffer. Some sites are just too heavy for the Pi’s CPU.

Here is a video running NorseCorp map posted on the original request: https://www.youtube.com/watch?v=Tt_DOM1sSKQ

We use the standard Raspbian web engine (Webkit) which has been optimized for the Pi. We are integrating a second web engine (Chromium). It is under development now.

Note that sites with heavy animations will always suffer. Some sites are just too heavy for the Pi’s CPU.

Here is a video running NorseCorp map posted on the original request: https://www.youtube.com/watch?v=Tt_DOM1sSKQ

We use the standard Raspbian web engine (Webkit) which has been optimized for the Pi. We will look into integrating a second web engine (possibly, Chromium). We need to do more testing though.

Note that sites with heavy animations will always suffer. The example you provide won’t be rendered correctly with any web browser on the Pi, because it is just too heavy for the Pi’s CPU.