Haxe

OK, so the scrollbars work, but my guess is that you havent implemented handleClipRect correctly for cermic... you might need to move the component up / down

handlecliprect returned a rectanglee with a static left/right of 0,0

```hx
    override function handleClipRect(value:Rectangle):Void {
        if (value == null) {
            this.clipQuad = null;
        } else {
            if (this.clipQuad == null) {
                this.clipQuad = new Quad();
                this.clipQuad.visible = false;
            }
            
            this.clipQuad.x = surface.x + parentComponent.surface.x;
            this.clipQuad.y = surface.y + parentComponent.surface.y;
            this.clipQuad.width = value.width;
            this.clipQuad.height = value.height;
        }
    }
```

when its scrolling, for example, down, i would expect value.x (or .top) to change

i think you have the clip right tbh, you might just need to move the surface up or something

you'll probably need to play a little - clip rects can be a pain since most frameworks seem to do "their own thing"... so cant help that much

I noticed on some other backends you create a clip quad every frame

is that intentional/does the backend have it's own way to handle that?

```hx
    private override function handleClipRect(value:Rectangle):Void {
        if (value == null) {
            this.scrollRect = null;
        } else {
            this.scrollRect = new openfl.geom.Rectangle(Math.fround(value.left),
                                                        Math.fround(value.top),
                                                        Math.fround(value.width),
                                                        Math.fround(value.height));
        }
```

so every frame a new rectangle is being created, rather than just reusing the existing one

seems quite bad cause cliprect is being called every frame idly

`(17709) haxe\ui\backend\ComponentImpl.hx:80: here`

you mean if you trace on handleClipRect it just sits there tracing?

some of the things i tried, once i let go of the mouse button

the clip/surface would infinitely keep moving

its certainly not called over and over again... nor should it... so its something off in your backend

I never manually call handlecliprect tho o_o