# \[BUG?\] CSS transform with \<IMG\> tags

**URL:** <https://forums.creativeclouddeveloper.com/t/bug-css-transform-with-img-tags/9388>\
**Category:** Photoshop\
**Tags:** ui, bug, uxp, css\
**Created:** [February 15, 2025, 10:26pm UTC](https://forums.creativeclouddeveloper.com/t/bug-css-transform-with-img-tags/9388 "2025-02-15T22:26:50Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![blackRGB](https://avatars.discourse-cdn.com/v4/letter/b/58f4c7/32.png) [@blackRGB](https://forums.creativeclouddeveloper.com/u/blackRGB)\
**Post date:** [February 15, 2025, 10:26pm UTC](https://forums.creativeclouddeveloper.com/t/bug-css-transform-with-img-tags/9388/1 "2025-02-15T22:26:50Z")

</div>

Hello everyone. I enabled CSSNextSupport and noticed that the CSS property `transform: rotate()` doesn’t work with `<img>` tags. If applied to the parent, for example a `<div>` , the block rotates, but the child `<img>` stays in place. Other parameters like `scale()` , `skew()` , etc., don’t work either. Only `translate()` works, but not `translateZ` . Is this a bug or a feature? lol

---

<div class="post-metadata">

**Author:** ![Karmalakas](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.creativeclouddeveloper.com/karmalakas/32/1048_2.png) [@Karmalakas](https://forums.creativeclouddeveloper.com/u/Karmalakas)\
**Post date:** [February 15, 2025, 11:22pm UTC](https://forums.creativeclouddeveloper.com/t/bug-css-transform-with-img-tags/9388/2 "2025-02-15T23:22:54Z")

</div>

I thought none of the `transform` features were supported 🤔 I could use rotation. Need to check…

_Edit:_ Just tested `transform: rotate(45deg)` on a `div` and a `label` - still doasn’t work 🤷‍♂️ Even with enabled CSS feature flags [introduced in UXP v8.0.1](https://developer.adobe.com/photoshop/uxp/2022/ps_reference/changelog/#uxp-v801)

_Edit 2:_ It doesn’t work if `label` is in a `sp-action-button`, but kinda works, if it’s just in a regular `div`. _Kinda_, because when rotated, text inside it disappears, so pretty much useless (at least in my case)

---

<div class="post-metadata">

**Author:** ![Karmalakas](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.creativeclouddeveloper.com/karmalakas/32/1048_2.png) [@Karmalakas](https://forums.creativeclouddeveloper.com/u/Karmalakas)\
**Post date:** [February 16, 2025, 9:18am UTC](https://forums.creativeclouddeveloper.com/t/bug-css-transform-with-img-tags/9388/3 "2025-02-16T09:18:19Z")

</div>

I’ll ping @Erin_Finnegan to forward this to someone hopefully. It seem yet again the feature is added, but pretty much unusable (see also my edits in the previous post)

---

<div class="post-metadata">

**Author:** ![mykim](https://avatars.discourse-cdn.com/v4/letter/m/76d3ee/32.png) [@mykim](https://forums.creativeclouddeveloper.com/u/mykim)\
**Post date:** [February 17, 2025, 12:22am UTC](https://forums.creativeclouddeveloper.com/t/bug-css-transform-with-img-tags/9388/4 "2025-02-17T00:22:41Z")

</div>

UXP does not support CSS transform on \<img\> tag.

Not all the CSS functions/properties are supported in UXP.  
UXP supports CSS translate(), translateX(), translateY(), rotate(), scaleX(), scaleY(), scale() functions and translate property.

Not all the UI elements supports CSS transform.  
Only Border, Outline, Color background, shadow and SVG support CSS transform now.

It’s because we prioritize developing only features that are needed upon requests.

---

<div class="post-metadata">

**Author:** ![blackRGB](https://avatars.discourse-cdn.com/v4/letter/b/58f4c7/32.png) [@blackRGB](https://forums.creativeclouddeveloper.com/u/blackRGB)\
**Post date:** [February 17, 2025, 5:45am UTC](https://forums.creativeclouddeveloper.com/t/bug-css-transform-with-img-tags/9388/5 "2025-02-17T05:45:26Z")

</div>

> [@mykim](#):
>
> It’s because we prioritize developing only features that are needed upon requests.

It feels like Adobe is manually recreating CSS from scratch in assembler. They add each property with blood and sweat. 😀

---

<div class="post-metadata">

**Author:** ![Karmalakas](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.creativeclouddeveloper.com/karmalakas/32/1048_2.png) [@Karmalakas](https://forums.creativeclouddeveloper.com/u/Karmalakas)\
**Post date:** [February 17, 2025, 9:02am UTC](https://forums.creativeclouddeveloper.com/t/bug-css-transform-with-img-tags/9388/6 "2025-02-17T09:02:44Z")

</div>

> [@mykim](#):
>
> UXP does not support CSS transform on tag

Could you please explain what that means? What does it work on, when whole UI is just tags and nothing else? Or by _tag_ you mean something different than HTML tag?

* * *

> [@mykim](#):
>
> UXP supports CSS \<…\> rotate(), \<…\>

For now I personally am most interested in `rotate()` and that’s what I will focus on. As mentioned before, it doesn’t really work. How it works, is useless. After rotating a `<label>`, the text inside it simply disappears. Or is `<label>` just another _tag_ on which it won’t work? If so, then same question - what does it work on?

* * *

> [@mykim](#):
>
> Not all the UI elements supports CSS transform.  
> Only Border, Outline, Color background, shadow and SVG support CSS transform now.

What does that mean? How do you rotate a background color or a border? I honestly don’t understand what’s the purpose of the transformation in these cases…

* * *

> [@mykim](#):
>
> we prioritize developing only features that are needed upon requests

Absolutely does not look like that’s the case. Some features are requested for years and still not here. The ones that are seemingly here, don’t work. Especially the UI stuff - since UXP release nobody cares much. I mentioned this before - most of actual bugs are scrubbed under the _Known Issues_ and forgotten

* * *

> [@blackRGB](#):
>
> It feels like Adobe is manually recreating CSS from scratch

Not just CSS, but the whole browser. It was discussed multiple times before with no reaction from Adobe team. Instead of taking a normal browser and stripping it down by removing or limiting some features, it seems, as you say, they are building their own from scratch by copy-pasting from existing browsers and trying to glue up a new one. That’s really disappointing to see, when UXP is praised as the future, while still being years in the past 😞