DEV Community: Ben Evans

CodePen TV secrets

Ben Evans — Sun, 29 Mar 2026 23:23:50 +0000

Those seven deadly things you always wanted to know about creating a CRT TV in CSS.

A behind the scenes candid deep dive.

(1) My first vanilla CSS Art project! 😮
Can you actually believe it? Yes. But anyway, I got so into SASS that it wasn't until... Well I explained it all in my last post but yeah, I guess this is my first actual pure CSS art! I did really want to add white noise and channel clicks, but that would have involved JavaScript, so you shall have to imagine that yourselves. It's also my first use of corner-shape: squircle. Firefox doesn't support me on this yet, but oh well! I think squircle is necessary usage for a CRT!

(2) Lighting the CodePen logo. 🌅
The spinny cube thing has actual three dimensional light coming from the left, which took blumming ages to do, and it's barely even noticeable. So I would just like to point that out here 😅

The lighting within the TV image is also the opposite, to the TV, as I thought this might help represent a TV broadcast. But I also think this isn't noticeable :)

(3) The volume control distorts the scanlines. 🔊
I thought this would kind of represent the increase in volume interfering with the tuning, as it would if you didn't have ground loop isolation.

(4) Rotating knobs. 🛞
Getting the knobs look like they rotate when the shine stays top right. It was a tricky one. But the dashed border works hard here.

(5) The glass reflections could not be square! 😎
To replicate the distortion of a cathode ray tube's shape. The window reflection is made entirely of repeated right dashed borders. These look very different depending on the browser engine. Blink's dash size is almost perfect for the real window panes. But it's a strange way to draw windows.

 &, &:before, &:after {
     width: 31rem;
     height: 100rem;
     border: solid 7rem transparent;
     border-right: dashed 7rem hsla( var(--wht-hsl),.05);
     background: transparent;
     border-radius: 50%;
 }

(6) It's responsive! 📱
The TV changes layout depending on your screen size. I used rems and aspect ratios hard!

(7) The CodePen 2.0 logo. 🖋️
The rotating 2.0 makes no sense in reality. It does transform:scaleX(-1) exactly at 90 degrees so that 2.0 reads left to right on both the front and back.

Just one more thing... 🕵️
The YouTube's video intro is made entirely of CSS! I adapted two of my older projects to introduce it. As well as this one. And the music was written by me and Robert Frogley especially for the video.

Keep this on the QT 🤫 but I also lost most of the screenshots for creating this video because my laptop died and the drive got wiped when trying to fix it. So annoyingly I had to undo everything I did and screenshot it, and then play it forwards! 😮

Desassing, unsassing.

Ben Evans — Thu, 13 Nov 2025 23:28:17 +0000

Unsassifying is very satisfying.

Remember when you could create a website in a few minutes?

A web development folder 10 years ago:

index.html
styles.css
Setup time = 3mins.
Server load including a few images: ~100–500 KB

A web development folder in 2025:

index.html
plus 16,942 files bought in by NPM
Setup time = 1 day.
Server load including a few images: ~150–250 MB

So much bloat!

So much waste!

I pretended to myself that none of this was happening outside of work. When I say Sass - I actually mean SCSS - did anyone actually use Sass? And in terms of desassing, I’m probably including LESS in the general theme of it all. Anyway, CSS was growing, websites were doing more, and Sass came along to make things easier. For personal projects I skipped NPM for speed and used Koala.exe to compile, and even though Koala.exe stopped being supported about 5 years ago, I carried on. That was until I reluctantly started to use @use. So Sass became a pain. I would like very much to make code as short and as fast as possible, selfishly I would not like to reference everything with the partial it came from. I would not like to be told off about how I should code my stylesheets via Prettier. This was becoming unfun. I think it might be time to unsass!

Sass is now faff.

It’s a revelation! It feels strange not to have to wait for anything to compile. How did I become so conditioned by Sass!? From where I was with Sass, it was pretty easy to make the leap back to native CSS. And probably obvious to most, but here is the lowdown:

Instead of Sass variables, use root variables or ‘Custom Properties’. (not the most catchy name)
Instead of my most favourite simple but probably bad: rgba(#000,.5); for transparencies, use (and I agree this is slightly more convoluted but you get used to it) hsla(var(--hslcolor),.5), so yeah, you do need to convert your faithful HEX to a HSL and store it as a ‘custom property’, but that’s fine, we can do that, it’s 2025, there are websites out there that convert. Maybe even AI could tell you 🫢
If you do use proper full fat Visual Studio, like me, and not VS Code, then you do have to update to Visual Studio 2026, because Microsoft. I’m not sure why their full featured paid for product model is massively lagging behind their free lighter version, and I’m not here to judge, but yeah native CSS support in Visual Studio 2022 is abominably terrible, so don’t even try!
In native CSS, @import feels slightly old fashioned. Not sure why, but it’s like @import url('css.css'); so an index CSS file is cool. The cool weird part is: If you still live in Dickensian times and FTP things up, like me, then you were probably used to FTPing the whole style folder, because it needed the compiled CSS version. But with native CSS you can just upload the single file! Lol, am I writing this as the last person to catch up? Let me know in the comments.

So desassing is cool, it’s super fast, it’s easy, there is no compilation, all the colours are better and dynamic, and this makes creating a dark-mode option super easy. I’m now going to work my way through all my websites, desassing them, but this is my first:

SAlimer Dark sci-fi electro pop

One thing I did note that native CSS needs is @mixins, and I think that’s in the pipeline, so yeah, so long Sass and thanks for all the pish!

😮 It's me and other cool people!

Ben Evans — Tue, 08 Jul 2025 08:38:51 +0000

Alvaro Montoro

Jul 8 '25

10 Cool CodePen Demos (June 2025) + A talk with Ben Evans

#showdev #html #css #javascript

Comments 3

10 min read

CSS Backrooms

Ben Evans — Sun, 29 Jun 2025 21:20:22 +0000

No Images - No JavaScript - Only HTML and too much CSS!

In January, I watched the very cool YouTube documentary about how The Backrooms came to exist: https://www.youtube.com/watch?v=o3cTIn2Z_Ck

The original 4Chan post that started the sensation 👆

Because of this, I fell in love with The Backrooms' origin story and had the idea of building on my previous 3D maze, mapping out the rooms to fit the photograph, and, this time, with the determination to make it work on Safari!

Original 3D maze

So I set to work.

As a proof of concept, I expanded the maze from a 7x7 grid to a 12x12, made everything beige, adding a ceiling and some wallpaper to the walls. Then I lined up the camera angle with the original 4Chan post's image. All looked good; it was probably possible! But knowing full well that I'd made it even less likely to work on Safari, the next step was to try and solve that issue.

From trying to fix the original, I knew that Safari didn't like the sheer size in pixels of the old maze. If I made the rooms tiny and if not too much went out of view, then it almost worked. So this time I scaled everything down. I made each 'room', or square of the grid, only 3x3rem; this helped, but it still crashed. Only when I narrowed down the path from a 12x12 grid to a 4x12 grid did things start to work.

I then spent the next three months working on a formula (I'm not very good at maths) to work out the position of the camera on the grid and remove cells that were not in view.

This is the formula to mark the position, not actually required for the final thing:

    %test {
        background: rgba( magenta,.9);
    }

    @for $x from 1 through $grid {
        &:has(#x-#{$x}:checked) {
            @for $y from 1 through $grid {
                &:has(#z-#{$y}:checked) {
                    $yn1: ($y - 1);
                    $sum: ($yn1 * $grid + $x);

                    floor:nth-of-type(1) tile:nth-of-type(#{$sum}) {
                        @extend %test;
                    }
                }
            }
        }
    }

And it worked on Safari! 🥳

I then tidied everything up, and in doing so, learned a few useful things. Because of the size of these grids, I needed to make everything more efficient. When it came to mapping out the levels, I got this down to a fine art. I created @each loops, so I could easily just add a batch of coordinates from the map.

$east: ( 16: 4 2, 20: 8 2, 28: 4 3, 31: 7 3, 33: 9 3, 40: 4 4, 43: 7 4, 46: 10 4, 47: 11 4, 49: 1 5, 59: 11 5, 61: 1 6, 64: 4 6, 67: 7 6, 73: 1 7, 76: 4 7, 79: 7 7, 82: 10 7, 83: 11 7, 88: 4 8, 94: 10 8, 95: 11 8, 106: 10 9, 107: 11 9, 109: 1 10, 112: 4 10, 118: 10 10, 119: 11 10, 121: 1 11, 124: 4 11, 129: 9 11, 131: 11 11 );

@each $key, $values in $east {
    $first-value: nth($values, 1);
    $second-value: nth($values, 2);

    body:has(#level-1:checked):has(#x-#{$first-value}:checked):has(#z-#{$second-value}:checked):has(.x-rotation:checked) {
        .downb {
            @extend %d-none-i;
        }

        .downb[for="x-0"] {
            @extend %d-block-i;
        }
    }
}

Getting the first and second values was super handy and simpler than I had imagined.

I also had to pay attention to how the SASS compiled the output and discovered the beautiful benefit of @extend. I probably should have already known this, but now I really understand.

And if, like me, you don't already know:

A loop would normally compile to each loop listing one after the other, for example, this:

z floor tile{
    $short-wood-right: 1, 2, 3;

    @each $i in $short-wood-right {
        &:nth-of-type(#{$i}) span:before {
            transform: translate3d(2.97rem, .5rem, 5.5rem);
        }
    }
}

Would output like this:

z floor tile:nth-of-type(1) span:before {
    transform: translate3d(2.97rem, .5rem, 5.5rem);
}
z floor tile:nth-of-type(2) span:before {
    transform: translate3d(2.97rem, .5rem, 5.5rem);
}
z floor tile:nth-of-type(3) span:before {
    transform: translate3d(2.97rem, .5rem, 5.5rem);
}

Whereas by using @extend, this:

%wood {transform: translate3d(2.97rem, .5rem, 5.5rem);}
z floor tile{
    $short-wood-right: 1, 2, 3;
    @each $i in $short-wood-right {
        &:nth-of-type(#{$i}) span:before {
            @extend %wood;
        }
    }
}

Would output like this:

z floor tile:nth-of-type(1) span:before, z floor tile:nth-of-type(2) span:before, z floor tile:nth-of-type(3) span:before {
    transform: translate3d(2.97rem, .5rem, 5.5rem);
}

Which is much lighter to load, especially with as many loops as I am using.

So I tidied everything up, improved the wallpaper, added two floors, put some wall furnishings in, created some kind of storyline with a beginning and end, and added some scary elements. It didn't seem quite complete without any sound, so I threw together some atmospheric loops and, much as it goes against the whole CSS only thing, I had to use a tiny bit to play the sounds 😬 but I made this the absolute bare minimum:

<script>t = i => document.querySelectorAll('audio').forEach(a => { a.id == i ? (a.paused && a.play()) : (a.pause(), a.currentTime = 0) })</script>

If anyone can get that to be any smaller, then please let me know.

In the end, the CSS was so big that I couldn't fit the uncompiled SASS version into CodePen, so it's just the outputted CSS. And I think I added back in so much detail that it probably doesn't work on iPhones anymore. But, anyway, here it is; please let me know what you think I could do to improve the gameplay or the code, and the first person to share a screenshot of the end wins! Good luck in there 😱

CSS Music Video - No Images - Pure Code.

Ben Evans — Fri, 27 Sep 2024 11:36:53 +0000

Yep. Still third person. 🤦‍♂️

About this time last year, Ben Evans set to work on a full music video built using only CSS. This attempt was quite optimistic, to say the least.

Ben wanted to see how far he could take CSS in this direction. The song was written by the fantastic SAlimer about the Earth's moon. Ben decided it would be fun if his 'video' started by travelling around the solar system, to eventually land on the earth's surface and take the story from there. So, first step, create a planet in CSS...

Three-dimensional spheres have always been a goal of Ben's to create in CSS, as they are so very difficult to achieve. Ana Tudor has managed to achieve this with her amazing mathematical brain. But Ivorjetski tries his hardest to avoid thinking too much and constructs things in a more structural way.

Ana has also done more planetary creations but they are heavy on the browser, so we kept this example lite :)

But anyway... You can see Ben's first attempts on CodePen if you are interested and there is also a video which shows how he created his attempt. If nothing else it definitely works as the best intro to any of his videos:

It became clear to Ben that his computer will never cope with this approach and the only way he could figure out how to do the animation timing would be painful with this length of track.

And so to the present day!

Ivorjetski and his friend Froggy, wrote a short song, and with the lessons learnt, Ben thought this would be ideal to make a much shorter and simpler video in CSS to go alongside it. It features the same character that appeared in an earlier Table Tennis CSS game of Ben's. Mainly due to Ben's laziness and his awesome ability to copy and paste.

Could it be the first responsive music video?

It made Ben very sad but he had to use the teeny-tiniest amount of JavaScript required to initiate the sound 😭 Please don't judge him too harshly 🙃

Video and track by Ben Evans. Lyrics and vocals by Rob Frogley.

A like to the video of the video would be very much appreciated. And I'm sure SAlimer, the inspiration for this, would appreciate one too. If you would be so kind. Because let's be honest, it's utterly brilliant! :)

Happy MusiCSS-ing 👋

Creating a CV in 2024

Ben Evans — Wed, 10 Jul 2024 20:05:56 +0000

A third person blog.

Back by unpopular demand!

Ben was thinking he should probably update his CV. He hadn't done this for... Ben, how long has it been? He doesn't know 🙄 but he says the format has not really changed since 2010 😬😮

So it's about time for a change!

Ben had been putting off updating his CV (for 15 years), but when thinking about how to put it off even longer, he came up with two solutions:

Writing this blog about it and not actually do it.
Make it a fun thing to do!

He wasn't going to ask his chatty mate; Gary Pon-Tovi (ChatGPT), this time!
To make it fun and less of a chore, he thought he would start from scratch in the only way that Ben loves the most to start from scratch... A nice, empty, HTML document! 🤩

This was quite interesting as he thought he would have to make it the most accessible, most perfectly semantic web page he had ever produced. To be easily found and also demonstrate his skill level to future employers. A daunting prospect! But Ben loves nothing more than a seemingly impossible challenge, so he set to work, full of vim and vigor*.

*Wow! Vim & vigor broke my spellcheck! Ben's going off down a vim & vigor word-origin rabbit hole now. Gosh does anyone still use Vim? The most user-unfriendly text editor ever used!

That aside... Ben's ultimate CV would of course be only HTML and CSS, and have a link through to his reasonably up-to-date (CSS only) portfolio:

(This is an older version. The real version is here )

So... Ben has built a basic semantic layout of the page and designed the left side of the header. Everything is pretty dull so far. It needs a link to Ben's portfolio in the header. He doesn't really want to add a profile picture. 🤔 So what about his logo? The CSS version of his painting signature? And when you hover over it... It could rotate!? As a hint to his portfolio!!? Great ideas!!!
But a card is now boring to Ben, and a cube is so basic! 🤔 What about a three-sided shape? A three-sided shape that has proper lighting? Like the Moka pot he did?! Yes!! These are all great ideas! Ben thought. Much more fun than writing a CV!

After the moka pot, Ben made a room with a ceiling fan, which had realistic lighting. The lighting from the window is barely noticeable, but Ben thinks it makes it look so much more three-dimensional.

The lighting effect is actually quite simple to do. Unlike background colours, CSS filters blend from one state to another. So it's just a case of timing when to add brightness or shade along with the rotation.

  @keyframes light {
    50% {
      filter: brightness(0.5);
    }
  }

And after all this procrastination... Ben didn't do any of that! He instead put in a profile pic, like he didn't want to do 🙃 And then spent far too long styling the link underlines and YouTube hover effects.

So anyway, here it is, let him know what you think:

BEN EVANS - WEB DESIGNER - LONDON

animation-timeline: WIN!

Ben Evans — Thu, 13 Jun 2024 13:28:35 +0000

Scroll Buckets

Third persona style!

Ivorjetski (aka Ben Evans) was becoming increasingly aware that a lot of new CSS capabilities we being released and he had mainly been ignoring them 😬

He'd seen a lot of cool new demos using the new scroll features and thought it was about bloody time he tried something himself.

Talking of cool new CSS scroll demos, you can't much better than this one, by Adam Kuhn 😍

Anyway... Ben ain't go no time for doing something quite that amazing! He was far too busy procrastinating over how to put off making a game of Snake with CSS.
So instead, he came up with the idea of seeing if he could retro-fit a scroll based animation into an older CSS art piece: Pure CSS Playing Card - King of Hearts - This used to animate on hover, but he was never happy with it, it was a bit jittery. So Ben thought he could fix it with a bit scroll based magic! Hogwarts style!📜🧙‍♂️

And... Oh my god! Animation-timeline is so simple and so powerful!! It was an absolute breeze! Actually a little disappointing, in a way... How can Ben have fun trying to create impossible things with CSS, if CSS is now this powerful and easy! This should be banned from Hogwarts! Banned and thrown straight into the scroll bucket! 🗑️

All the animations were already in place. Ben simply needed to remove the trigger by hover and replace the trigger with: animation-timeline: scroll(); And that was pretty much that! - Apart from giving the page a bit of extra height and fixing the card in place, so it didn't move on scroll. Ben thought: "Where is the fun in that!" But he has to admit, it is quite fun and it works so well. He thinks he will be using this feature a lot more in future... Perhaps to make a PlayDate style game, but using scroll, instead of the fun little crank.

Oh and by-the-way, everything is CSS, including the card face, there is a video of Ben creating it:

There was also a little writeup on how it was made in frontend.horse

Would be cool to know what you think?

See ya x

guYs I cANt deCide – a Or B?

Ben Evans — Tue, 11 Jun 2024 15:45:11 +0000

Still rocking the third person vibe 🤷‍

Ben was doom scrolling, as he does most mornings, when he stumbled across this post from Tyler Nickerson:

Ben simply couldn't resist this challenge! He took a day off from doing nothing and set to work...

Four hours later... Here is the result:

So, how was this done?

    box-shadow: 1em 0 0 $g, //
    45em .6em 0 $g, //
    46em .6em 0 $g, //
    47em .7em 0 $g, //
    48em .8em 0 $g, //
    49em .9em 0 $g, //

Ben set the image from Twitter as a background, and traced it by coding one box-shadow at a time. A few years ago he found a technique of putting // comment marks after every comma to make it easier to code. It was pretty essential at the time for attempting to draw the thousands of lines for this:

But this time he basically added a tiny round shadow every 1rem, tracing along the lines of 'text'. His best idea of the morning was to ask his chatty mate, Gary Pon-Tovi (ChatGPT) to "Add an extra step between each value, please." Ben always likes to be polite to Gary... But he forgot this morning, probably because it was before his coffee...

Ben had also previously traced the words of Magritte, in a similar method, to recreate his work 'The Treachery of Images' in only CSS. Ben thought this famous work was quite apt because CSS art is all about not being an image. Ben also added a touch of 3D magic to the recreation of the pipe, when the user hovers.

Ben finds it funny to use the word 'user'. Isn't this the term for a drug addict? He might write a separate blog about this.

P.s. This 3rd person thing is driving him nuts!

CSS animation and interaction delay.

Ben Evans — Tue, 11 Jun 2024 13:55:30 +0000

Tap tap tapping.

A blog written in 3rd person. For no reason.

For this game Ben Evans wanted some very simple controls. Basically a single tap anywhere to control it. And you can't get much simpler than that!

From a coding perspective, this will involve putting a stack of labels as invisible layers on top of everything. The label will be linked to a checkbox or radio button, which will control what is displayed.

So: Display a label > user taps label > label's 'for' attribute is connected with ID of input > if input is checked then animate the snake the appropriate way.

<label for="right-start"></label>
<input id="right-start" name="start" type="radio" />

#right-start:checked ~ .start-right {
  display: block;
}

So that's all good. The next problem Ben needed to solve is how to bring these labels in fast. He wanted them to animate in sequence; up, right, down, left. On a timer. So that when the user taps the screen, it could go in the direction currently displaying, as it cycles through the loop.

The trouble is, it seems, is that there is a delay in when something is shown and when it is clickable.

Ben had previously built a table tennis game, using a similar timing device and this seemed to work fine. But he didn't notice the lag. Possible because it wasn't super fast.

But this time Ben requires it to happen faster, and the lag seems very noticeable. Sad Face ☹

He has built a simple example of it on CodePen for you to see for yourself. If you tap 'Edit on CodePen' then you can adjust the timings:

It actually seems very usable on a two second repeat. If you change $t to one then it only responds on double taps. But this is based on Ben's laptop. It probably depends on the GPU and CPU speed. And probably also on how complex the future CSS will be.

Ben would be interested to find out how it behaves for you. Please leave a comment on whether the appropriate radio is checked when you tap the screen. He would be very much appreciative 🙏

CSS Snake.

Ben Evans — Mon, 10 Jun 2024 22:03:12 +0000

A blog written in 3rd person. Well, why not...

London based CSS Artist, Ben Evans, has had some lofty ideas in the past and this one follows that trend... His current aim is to make, or even remake, some form of the Nokia classic: Snake. Using only CSS. He's not currently sure if this is possible but he would love you to join him on his journey to finding out...

Ben has previously built CSS concepts with movement grids, the peak of this in-devour being a 3D maze game (which unfortunately doesn't like Safari, or any iOS browser, because they are all Safari really):

Like most of Ben's CodePen's, there is also a video detailing the creation process on his YouTube Channel. This one can be found here:

Ben, also known as ivorjetski, has already set to work on Snake. So far he's spent far too long drawing the background entirely with CSS:

He thought it would be fun to recreate the old Windows 10 default lockscreen in CSS. He was probably wrong about this.

He tried to keep the background down to a fewer lines of CSS as possible. It's about 1000. Which isn't bad considering the crazy amount of texture that he needed to do for the rocks.

Ben realised he could create the texture using text! 😮 Surely this is where the word TEXTure comes from, he thought to himself, not silly enough to write it in a blog. Little did he know his thoughts could be heard by the alter-ego journalist.

Ben exclaimed: "It's pseudo classes, with the content declaration filled with random ascii shapes. Like this:"



   &:after, &:before {
            content: '●◖●  ●◖●  .● ●  ◖●◖●  ●  ◖-●  ●◖◖● ●◖ ●.●  ●◖●◖● ●●  ●.●◖●●';
            }

He has also designed a super simple movement grid for it. And then, for some reason, converted it into this pointless chess like thing. Perhaps so it would make sense when sharing it on CodePen:

This does everything Ben requires for a good basis to build from, and he has managed to get the code down to about 100 lines (not including his CSS drawn initials). He is pretty pleased with how this works. The directional buttons are actually all the same, but rotate themselves, putting themselves in the required position for left, right, up and down. Depending on what ID is shown in relation to what grid square the user is in. There is also a basic boundary detection in place, that Ben would need for the Snake game to work.

Stay tuned for more...

A Pure CSS 3D Maze! - Chrome only

Ben Evans — Thu, 13 Jul 2023 12:55:17 +0000

🌎 100% Natural ingredients!
🚳 No images
📵 No JavaScript
👨‍💻 Just CSS - And a sprinkling of HTML

Like most CSS projects of mine, I had no idea whether this was possible before I started, and learnt some things along the way. I tried to keep the graphics a simple as possible to help with the animations and to fit with the retro vibe of the original 3D mazes from the 1990's. If you watch the YouTube about making it you can see the style to begin with was very different. I was thinking more like the style of Legend of Grimrock.
I'm happy with the familiar controls, the elevators (to make it more interesting), and the subtle depth shading... I'm not sure I've seen this done in 3D CSS Art before.

Anyway I hope you like it :)

💥 CHROME ONLY!!

Firefox is okay but very slow.

Sorry Safari people 🥺
💀 I've tried but it's just not going to happen :(

The making of:
📺 youtu.be/Z0VHM4KcMFQ

First person to send me a screen shot of the end screen wins...
Your time starts now!!! 🏁

P.S. If you have any ideas how to help with Safari then please let me know x

🔗 linktr.ee/ivorjetski

CTRL ALT ELITE --- A homage to 1984 Elite (Pure CSS Game)

Ben Evans — Mon, 12 Aug 2019 16:04:10 +0000

Hello.

For no reason other than a CSS addiction, I am creating a Pure CSS version of a 1984 BBC Micro computer game Elite which inspired a number of subsequent games, like GTA, No Man's Sky, etc.

The original game squeezed into the 32k memory of a BBC. My Compiled CSS is about 12k so far so I don't have much left to recreate the entire universe like the original (not that I am going to).

https://codepen.io/ivorjetski/pen/MNPqex

I have used the checkbox accesskey attribute to make some of the original keys work but you need to hold down Alt, hence the name.

If anyone has any ideas of how I can make it better, please let me know...

Should I stick to authentically recreating the original graphics where possible or bring it a bit more up-to-date in a stylish retro way?
I'm probably going to put the keyboard controls instructions in the page rather than in the javascript box comments.
Is the actual 3D laser a step too far? As in it uses to much GPU.

Oh yeah and it only works on Chrome at the moment.

Please let me know what you think.

Many thanks,

Ben.