yGuy's public fiddles
-
IE Edge SVG Foreign Object Rendering Bug
Edge has problems repainting Foreign Objects when the transform changes. This results in misplaced and badly scaled html rendering. Press the Bug button - the SVG along with the foreign object HTML Text should scale. Pressing the "Fix" button changes some unrelated CSS class in the SVG which somehow triggers a repaint that corrects the problem.
-
IE Edge SVG Text rendering Bug
Edge has problems repainting texts when the transform changes. This results in text disappearing, not being rendered at the right location, etc. Press the test button - all tree text lines should move equally to the right. The lowest disappears after a few presses and resizing the test window will sometimes result in the top line not moving anymore and flickering.
-
Testing node removal through innerHTML assignment
No-Library (pure JS), HTML, CSS, JavaScript
-
Chrome 38 bug with backface-visibilty
This regression in Chrome 38 prevents certain render layers from being rendered correctly in some cases. In order to reproduce, be sure to clear the browser cache first. After "run" you should see the text "You can see me", but above of it, there is just a single underline - the text of the link is not visible until after you force a repaint.
-
IE memory leak in setInterval
On IE10 setInterval does not seem to free the function after the interval has been cleared. In the test code, the closure of the function contains big data - the function is not referenced anymore by code after the interval was cleared, however the Memory usage stays high. using setTimeout the problem does not seem to exist. Also other browsers seem to work correctly.
-
IE memory leak in setInterval
On IE10 setInterval does not seem to free the function after the interval has been cleared. In the test code, the closure of the function contains big data - the function is not referenced anymore by code after the interval was cleared, however the Memory usage stays high. using setTimeout the problem does not seem to exist. Also other browsers seem to work correctly.
-
Test for Safari 6 bug
The code does not work in recent (Safari 6.0) versions of Safari on mobile iOS devices like iPad 2. It seems the JIT has a bug when optimizing post-increment operations in tight loops. Pressing click me multiple times in mobile Safari 6 yields different results after a while.