# Weird bug with shading rendering **URL:** \ **Category:** Snap! Bugs\ **Created:** [September 8, 2026, 6:47am UTC](https://forum.snap.berkeley.edu/t/weird-bug-with-shading-rendering/22413 "2026-09-08T06:47:25Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![thegodofpalebeaks](https://forum.snap.berkeley.edu/user_avatar/forum.snap.berkeley.edu/thegodofpalebeaks/32/45912_2.png) [@thegodofpalebeaks](https://forum.snap.berkeley.edu/u/thegodofpalebeaks)\ **Post date:** [September 8, 2026, 6:47am UTC](https://forum.snap.berkeley.edu/t/weird-bug-with-shading-rendering/22413/1 "2026-09-08T06:47:25Z")
![Snap! 12.1.1 - Google Chrome 2026-09-08 16-37-33](https://cdn.forum.snap.berkeley.edu/original/3X/a/4/a47a9ad76c2af0302f681bb7c0c4a126ed77e4de.gif) The split() block’s top left shading is acting kind of weird when I hover another block over it. You don’t _have_ to fix it, it’s just something weird I found. ---
**Author:** ![dardoro](https://forum.snap.berkeley.edu/user_avatar/forum.snap.berkeley.edu/dardoro/32/14708_2.png) [@dardoro](https://forum.snap.berkeley.edu/u/dardoro)\ **Post date:** [September 8, 2026, 8:05am UTC](https://forum.snap.berkeley.edu/t/weird-bug-with-shading-rendering/22413/2 "2026-09-08T08:05:07Z")
You are talking about the first input slot being highlighted with the white semitransparent oval? There is hidden a Shift ⚙☑ \red{\text{Prefer empty slot drop}} that blocks replacing the occupied slot. ---
**Author:** ![thegodofpalebeaks](https://forum.snap.berkeley.edu/user_avatar/forum.snap.berkeley.edu/thegodofpalebeaks/32/45912_2.png) [@thegodofpalebeaks](https://forum.snap.berkeley.edu/u/thegodofpalebeaks)\ **Post date:** [September 8, 2026, 10:14am UTC](https://forum.snap.berkeley.edu/t/weird-bug-with-shading-rendering/22413/3 "2026-09-08T10:14:37Z")
No, I’m talking about how the top left corner shading of the split() reporter is disappearing when I hover the keep items reporter over it. It’s kind of hard to spot, so I would recommend opening the GIF in a new tab and zooming in. ---
**Author:** ![dardoro](https://forum.snap.berkeley.edu/user_avatar/forum.snap.berkeley.edu/dardoro/32/14708_2.png) [@dardoro](https://forum.snap.berkeley.edu/u/dardoro)\ **Post date:** [September 8, 2026, 11:09am UTC](https://forum.snap.berkeley.edu/t/weird-bug-with-shading-rendering/22413/4 "2026-09-08T11:09:13Z")
> [@thegodofpalebeaks](#): > > It’s kind of hard to spot Indeed… Chrome@Win10, 2560x1440 no sign of distortion. This highly visible dithering on your screenshot is a compression artifact or just very low color count of your display? ---
**Author:** ![codingisfun2831t](https://forum.snap.berkeley.edu/user_avatar/forum.snap.berkeley.edu/codingisfun2831t/32/42120_2.png) [@codingisfun2831t](https://forum.snap.berkeley.edu/u/codingisfun2831t)\ **Post date:** [September 8, 2026, 11:51am UTC](https://forum.snap.berkeley.edu/t/weird-bug-with-shading-rendering/22413/5 "2026-09-08T11:51:59Z")
Its a GIF, and the GIF form of compression is just losing certain colors ---
**Author:** ![mark4sisb](https://forum.snap.berkeley.edu/user_avatar/forum.snap.berkeley.edu/mark4sisb/32/32632_2.png) [@mark4sisb](https://forum.snap.berkeley.edu/u/mark4sisb)\ **Post date:** [September 8, 2026, 4:37pm UTC](https://forum.snap.berkeley.edu/t/weird-bug-with-shading-rendering/22413/6 "2026-09-08T16:37:28Z")
This is actually the same bug I reported [here](https://forum.snap.berkeley.edu/t/windows-dialogues-and-blocks-leave-residue-when-moved/22282), with the exact symptom described in this post being discovered previously here: > [@Windows (dialogues) and Blocks Leave Residue When Moved](https://forum.snap.berkeley.edu/t/windows-dialogues-and-blocks-leave-residue-when-moved/22282/6): > > ![image](https://cdn.forum.snap.berkeley.edu/original/3X/3/9/39d4261428217975c1f1b9a16008e98a15cfa329.png) > > Edit: Taking a close look at that screenshot, the black lines appear to be visible on the inputs themselves, as well as the pivots variable. This means they appear everywhere, not just on dialogues. What is going on is, when moving down or to the right with an object (window, block, etc), the input slot’s bevel get’s drawn in places it shouldn’t (on top of other block’s/windows and slightly outside of the area the bevel should be). In your case, the ring’s interior hole has a bevel which is getting “spread around” and “smudged” so to speak when you move objects over top of it. I’m on Chrome and Windows 11, and > [@Windows (dialogues) and Blocks Leave Residue When Moved](https://forum.snap.berkeley.edu/t/windows-dialogues-and-blocks-leave-residue-when-moved/22282/9): > > Turning off \text{Use graphics acceleration when available} in Chrome settings fixes the bug for me. ---
**Author:** ![thegodofpalebeaks](https://forum.snap.berkeley.edu/user_avatar/forum.snap.berkeley.edu/thegodofpalebeaks/32/45912_2.png) [@thegodofpalebeaks](https://forum.snap.berkeley.edu/u/thegodofpalebeaks)\ **Post date:** [September 8, 2026, 10:03pm UTC](https://forum.snap.berkeley.edu/t/weird-bug-with-shading-rendering/22413/7 "2026-09-08T22:03:17Z")
Damn… Alright, I’ll try that when I’m on my computer.