# marquee Published articles for marquee. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Building an Infinite Loom: Unravelling Images into Threads with Three.js DevFeed: [Building an Infinite Loom: Unravelling Images into Threads with Three.js]() Original publisher: [Read original article]() Author: Clément Grellier Published: 2026-09-05T12:50:25Z Content type: tutorial Language: en Sources: [Codrops]() Topics: [Web Development]() Tags: [creative-coding](), [creative-web-experiments](), [digital-art](), [frontend-animation](), [generative-art](), [glsl-shaders](), [gsap](), [html](), [image-animation](), [image-distortion](), [image-effects](), [image-slider](), [images](), [infinite-slider](), [interactive-images](), [interactive-web-design](), [javascript-animation](), [marquee](), [playground](), [ribbon-animation](), [shader-effects](), [shaders](), [thread-animation](), [three-js](), [three-js-demo](), [three-js-shaders](), [unraveling-effect](), [webgl](), [webgl-animation](), [webgl-demo]() ### AI overview A Three.js tutorial for an infinite image strip whose cards are split into independently animated horizontal ribbons. It explains how separate geometry and shaders create weaving, unraveling, gaps, fading, and varied thread motion. ### Source excerpt An experimental Three.js demo that transforms images into flowing ribbons, weaving them together and unraveling them as they move across the screen. ## Making basicMarquee-Modifier More Accessible DevFeed: [Making basicMarquee-Modifier More Accessible]() Original publisher: [Read original article]() Author: Eevis Panula Published: 2025-02-20T10:38:55.771000Z Content type: tutorial Language: en Sources: [Eevis Blog]() Topics: [Accessibility](), [Android](), [marquee](), [Code]() Tags: [accessibility](), [accessible](), [android](), [animations](), [code](), [how-to](), [marquee](), [technical]() ### AI overview This tutorial explains how to make Android's basicMarquee modifier respect the system "Remove animations" accessibility setting. It proposes reading the setting and exposing its value through composition locals to conditionally enable the marquee animation. ### Source excerpt I have this "Remove animations"-setting turned on on my phone because different kinds of movement make me feel physically sick. When the setting is on, animations are usually removed from native Android apps. And when there are some animations, I notice them. I've started seeing more and more of some horizontally scrolling texts, and I have been wondering why. Then I came across this basicMarquee-modifier. And it doesn't respect the "Remove animations" accessibility setting. And that's bad - many users (me included) rely on that setting to not see animations. Marquee-styled animations are one of the worst triggers of my motion sickness symptoms. If you want to learn more about my symptoms and why animations can be super problematic for some, I've written two blog posts, one from Android and one from a web point of view: Android, Animations and Reduced Motion You Make My Head Spin - Reducing the Motion on Web But since bringing up solutions is often better received than bringing up problems, this blog post will demonstrate one idea on how to improve the situation for us who rely on that "Remove animations" setting. The main idea is to read the value of this setting and then use it to decide if the basicMarquee-modifier is used. In this blog post, I'm using composition locals to accomplish it. Remove Animations Setting Before we dive into the code, a couple of words about the "Remove animations" setting. It's a global setting, which you can find from the accessibility settings. In my Pixel phone, "Remove animations" is under the "Color and motion"-section. From a technical perspective, the setting changes the animator duration scale to 0, so, in other words, the animations end right after they start. This accessibility setting is not exposed via accessibility services the same way as, for example, screen reader availability, so we'll need to be a bit creative. The following section explains how we can read the value of this setting. Composition Local for Remove Animat ## onwebkitplaybacktargetavailabilitychanged?! New exotic events in the XSS cheat sheet DevFeed: [onwebkitplaybacktargetavailabilitychanged?! New exotic events in the XSS cheat sheet]() Original publisher: [Read original article]() Author: Gareth Heyes Published: 2024-06-11T14:58:29Z Content type: article Language: en Sources: [PortSwigger Research]() Topics: [Cheat sheet](), [Security](), [Web](), [Mozilla](), [marquee]() Tags: [audio](), [cheat-sheet](), [code](), [community](), [contribute](), [firefox](), [marquee](), [mozilla](), [security](), [tool](), [update](), [video](), [web]() ### AI overview An update to PortSwigger's XSS cheat sheet adds and documents exotic browser event vectors, including Safari audio and video behavior, pointer interaction, autofocus usage, and WebKit trackpad events. The article also credits community contributions and Mozilla's help removing obsolete marquee events from Firefox. ### Source excerpt The power of our XSS cheat sheet is we get fantastic contributions from the web security community and this update is no exception. We had valuable contributions from Mozilla to remove events that no