Fixes #48 - Better handling of background images#141
Fixes #48 - Better handling of background images#141mabolek wants to merge 6 commits intot3kit:masterfrom mabolek:feature48
Conversation
MattiasNilsson
left a comment
There was a problem hiding this comment.
This looks good to me, just some smaller nitpicks! 👍
| } | ||
|
|
||
| page.cssInline { | ||
| # Debug related output |
There was a problem hiding this comment.
Remove commented code.
|
It is a great feature to be able to have different images for different devices, but this commit will affect all GridElement CE:s (f.ex. Parallax), not just the advanced grid. We need to have a way to enable it per CE. Maybe there is a way to implement it using the new "cropVariant"? |
|
@pixelmatseriks cropVariant support would probably be good in any case (I haven't looked too closely at it yet), but regarding the feature affecting other grid element CEs: Wouldn't it be good to have responsive images for parallax as well? Have I missed your point? 🙂 |
|
@mabolek Not all of the gridelements CE:s uses the image as a background image. |
|
@pixelmatseriks Hmm... In that case, the current implementation has the same problem. All GridElements have a |
|
@mabolek hmm, you are right. The Default layout always include a background-image if there's a file referenced in the content element, but the Empty layout doesn't. There is a condition in Collapsible, SimpleAccordion and Tab to use Default or Empty, but all of the other templates uses Default. The Parallax also includes file.0 if present in the template itself, but maybe it is a "fallback". |
|
@pixelmatseriks I suggest we use the current implementation and open separate feature requests for 1) implementing cropVariant and 2) improving the way layouts work, so files are only included in CEs that need them. |
No description provided.