Contents tagged “progressive enhancement”

There are 12 contents with this tag:

  1. screenshot of Please disable JavaScript to view this site

    Remy Sharp avatar Remy Sharp

    Please disable JavaScript to view this site

    Most of the web sites I visit on an average day require JavaScript to allow me to navigate the site fully. At least once a week there will be a web site that fails to fully load JavaScript for me and I'll (rage) quit the site and usually committing it to a bank of "web sites I can't be arsed to ever visit again because they messed up".

  2. screenshot of Hydration

    Jeremy Keith avatar Jeremy Keith

    Hydration

    The layered approach of progressive enhancement echoes the separation of concerns in the front-end stack: HTML, CSS, and JavaScript—each layer expressing more power. But while these concepts are related, they’re not interchangable. Separating out the layers of your tech stack isn’t necessarily progressive enhancement. If you have some HTML that relies on JavaScript to be useful, then there’s no benefit in separating that HTML into a separate payload. The HTML that you initially send down the wire needs to be functional (at least at a basic level) before the JavaScript arrives.

  3. screenshot of Why Is CSS So Weird?

    Miriam Suzanne avatar Miriam Suzanne

    Why Is CSS So Weird?

    If you don't understand why CSS is one of the great strengths of the Web, even if you've been using it for a while, you really have to spend these 15 minutes to watch Miriam Suzanne explain how it came to be, and why it is what it is.

  4. screenshot of What if?

    Harry Roberts avatar Harry Roberts

    What if?

    If you’re going to build an image loader that hides the whole page until all images are ready, you must also ask yourself what if the images don’t arrive?

See all tags.