I do understand that message “Custom attributes will be added to the most relevant HTML node.” but in this case the most relevant node should be img tag.
Attributes like fetchpriority=“high” or data-no-lazy=“1” can’t be used this way as it’s added to the wrapper. And I think what most people would want to modify with attributes is img.
Hi Dominik,
Thanks so much for your report!
We’re in a bit of a bind with this element: what if you want to assign an attribute to the link? Then you have the same problem, just the other way around…
However, since the logo element is simply an image/SVG within a link, the solution is more than simple: build your own logo element as a component (add an image or SVG, wrap it in a div, and turn it into a link). Then you can specifically control both the link and the image/SVG.
Best regards,
timmse
Hi Stefan,
thank you for this perspective, makes sense now.
I’ll use an image element for this instead.
I wanted to use options available within logo element like a logo inverse with sticky header.
But this should be possible if I structure my “component logo” the same way bricks logo is and assign appropriate classes to it, right?
Will also create a feature request for adding a fetchpriority control for the logo element image, similar to what’s available in the image gallery.
Thanks
In theory, yes. State classes such as “scrolling” and others are assigned to the header, which you can use.
