When I visit a page, I get annoyed when I try to interact with elements while the website is still loading. Often stuff is moving around, fonts aren’t quite loaded, and it feels broken.
I know nowadays we’re obsessed in this industry with gaining every millisecond in page performance. But in a couple of projects that I recently overhauled, I added a subtle and clean loading mechanism that I think makes the experience nicer, even if it does ultimately slightly delay the time that the user is able to start interacting with my page.
The two websites I’m talking about are Web Tools Weekly and CSS Values. Visit each of those home pages and you’ll notice in each case the content fades in rather than loading up in a clunky fashion. It’s more noticeable on CSS Values because there’s a lot more content on there and some JavaScript that has to load. Also, it happens on every “page” for CSS Values, but only on the home page for Web Tools Weekly (though technically the CSS Values pages are more like “states”).
I’m sure there are a few ways to accomplish this but I think my method is clean and easy to understand. I’m basically doing two things:
<body> element is ready, set it to opacity: 0 in CSS.<body> element back to opacity: 1, animating it so it comes in gracefully.I’m also ensuring that the page is fully visible and accessible to anyone viewing with JavaScript turned off. Those users shouldn’t notice anything wrong. This means I have to set the opacity using JavaScript.
The concept here is basically the same as if I was adding a loading spinner to the page, but because the page shouldn’t be loading for long, I don’t care about indicating what’s happening to the user. In other cases, a loading spinner might be more appropriate, but here I’m happy with a simple fade-in.
I could have used classes in my HTML that are pulled in from my stylesheet. But the stylesheet is external and I’m not inlining it. So if I’m trying to interact with the page before the stylesheet finishes loading, this might not work as well. Because of this, I opted for adding some CSS in the <head> of the document.
Here’s what my HTML looks like:
<style>
.hidden {
opacity: 0;
}
.visible {
opacity: 1;
transition: opacity 1s ease-out;
}
</style>
</head>
<body>
<script>
document.body.className = 'hidden';
</script>
Notice what’s happening above:
<style> element, just above the opening <body> tag<script> element right after the opening <body> taghidden class, which removes the body’s contentI’m doing this right at the top of the body element because I want the content to disappear as soon as possible. If I wait for this to happen in my external JavaScript, then it’s not going to happen quickly enough.
In my external JavaScript, I have something like the following:
function doStuff (callback) {
// do all app scripts here...
callback();
}
doStuff(function () {
document.body.className = 'visible';
});
In this instance I’m using a simple callback structure. I suppose you could also use Promises for this, but I didn’t really look into that much since I’m not yet that familiar with Promises. I believe the concept would be the same.
I’m basically ensuring all the app or website code that initializes any functionality is completely loaded before I set the <body> element back to visible.
To enhance it a little more, I could also wrap the whole thing in a jQuery-like document.ready handler:
window.addEventListener('DOMContentLoaded', function () {
// do everything here...
});
This means I’d be waiting for the DOM to be ready before running my scripts. Then the scripts run and after they finish I make the page visible. I can alternatively use the load event, which means I’d be waiting for the full page resources to load, rather than just the DOM to be ready.
If you want a stripped down demo version of this, you can check out this page. Note that it’s intentionally a very large page, so maybe avoid it on mobile. I’m also running some useless JavaScript (adding a bunch of classes to the HTML) just to pretend something’s happening to give the appearance of a pause before the fade-in happens.
As mentioned, you can also see how this works on Web Tools Weekly and CSS Values.
You could easily switch this up and put a loading spinner in place instead while the page is “getting ready”. I chose to do the fade-in because I think it looks good and I’m not concerned that either website is going to take a long time to load.
If you know of a way to improve on this, I’m glad to hear your feedback.
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。