We often think of background images as texture or something that provides contrast for legible content — in other words, not really content. If it was content, you’d probably reach for an
<img> anyway, accessibility and whatnot.
But there are times when the position or scale of a background image might sit somewhere between the poles of content and decoration. Context is king, right? If we change the background image’s position, it may convey a bit more context or experience.
How so? Let’s look at a few examples I’ve seen floating around.
Chris Coyier has this neat little demo from several years back.
The demo is super practical in lots of ways because it’s a neat approach for displaying ads in content. You have the sales pitch and an enticing image to supplement it.
The big limitation for most ads, I’d wager, is the limited real estate. I don’t know if you’ve ever had to drop an ad onto a page, but I have and typically ask the advertiser for an image that meets exact pixel dimensions, so the asset fits the space.
But Chris’s demo alleviates the space issue. Hover the image and watch it both move and scale. The user actually gets more context for the product than they would have when the image was in its original position. That’s a win-win, right? The advertiser gets to create an eye-catching image without compromising context. Meanwhile, the user gets a little extra value from the newly revealed portions of the image.
If you peek at the demo’s markup, you’ll notice it’s pretty much what you’d expect. Here’s an abridged version:
We could probably quibble over the semantics a bit, but that’s not the point. We have a container with a linked-up
<div> for the background image and another
<div> to hold the content.
As far as styling goes, the important pieces are here:
Not bad, right? We give the container some dimensions and set a background image on it that doesn’t repeat and is positioned by its bottom-left edge.
background-position. First, let’s listen for mouse movements on the
From here, we can use the container’s
offsetY properties. But we won’t use these values directly, as the value for the X coordinate is smaller than what we need, and the Y coordinate is larger. We will have to play around a bit to find a constant that we can use as a multiplier.
It’s a bit touch-and-feel, but I’ve found that
0.455 work perfectly for the X and Y coordinates, respectively. We multiply the offsets by those values, append a
px unit on the result, then apply it to the
Lastly, we can also reset the background positions back to the original if the user leaves the image container.
Since we’re on CSS-Tricks, I’ll offer that we could have done a much cheaper version of this with a little hover transition in vanilla CSS:
No doubt you’ve been to some online clothing store or whatever and encountered the ol’ zoom-on-hover feature.
There’s two pieces to this: the container and the magnifier. The container is the only thing we need in the markup, as we’ll inject the magnifier element during the user’s interaction. So, behold our HTML!
In the CSS, we will create
height variables to store the dimensions of the of the magnifier glass itself. Then we’ll give that
.container some shape and a
There are some things we already know about the magnifier before we even see it, and we can define those styles up-front, specifically the previously defined variables for the
It’s an absolutely-positioned little square that uses the same background image file as the
.container. Do note that the calc function is solely used here to convert the unit-less value in the variable to pixels. Feel free to arrange that however you see fit as far as eliminating repetition in your code.
What we need is basically a
mousemove event listener on the
.container. Then, we will use the
getBoundingClientRect(), which returns the size of an element and its position relative to the viewport.
Notice how I’m taking scrolling into account. If there is overflow, subtracting the window
pageY offsets will ensure the effect runs as expected.
We will first create the magnifier div. Next, we will create a
mousemove function and add it to the image container. In this function, we will give the magnifier a class attribute. We will also calculate the mouse position and give the magnifier the left and top values we calculated earlier.
Let’s go ahead and build the
magnifier when we hear a
mousemove event on the
Now we need to make sure it has a class name we can scope to the CSS:
The example video I showed earlier positions the magnifier outside of the container. We’re gonna keep this simple and overlay it on top of the container instead as the mouse moves. We will use
if statements to set the magnifier’s position only if the X and Y values are greater or equal to zero, and less than the container’s width or height. That should keep it in bounds. Just be sure to subtract the width and height of the magnifier from the X and Y values.
Last, but certainly not least… we need to play with the magnifier’s background image a bit. The whole point is that the user gets a BIGGER view of the background image based on where the hover is taking place. So, let’s define a magnifier we can use to scale things up. Then we’ll define variables for the background image’s width and height so we have something to base that scale on, and set all of those values on the
Let’s take the X and Y coordinates of the magnifier’s image and apply them to the
background-position. As before with the magnifier position, we need to subtract the width and height of the magnifier from the X and Y values using the CSS variables.
We could spice things up a bit using multiple backgrounds rather than one. Or, better yet, if we expand the rules to use elements instead of background images, we can apply the same animation to all of the backgrounds and use a dash of
animation-delay to stagger the effect.
Lots of ways to do this, of course! It can certainly be optimized with Sass and/or CSS variables. Heck, maybe you can pull it off with a single
<div> If so, share it in the comments!
GSAP is the main driver there, but I imagine we could make a boiled-down version that simply translates each background layer from left to right at different speeds. Not as cool, of course, but certainly the baseline experience. Gotta make sure the start and end of each background image is consistent so it repeats seamlessly when the animation repeats.
If you need help creating a digital marketing strategy for your business, don’t hesitate to contact one of Digidude’s consultants.