---
name: ".up-revalidating"
area: "API"
kind: "CSS class"
parent: "up.status module"
visibility: "experimental"
url: "https://unpoly.com/api/up-revalidating"
---
<nav aria-label="Unpoly docs">[All docs](https://unpoly.com/index.md) · [up.status module](https://unpoly.com/api/up.status.md)</nav>

# .up-revalidating

**This feature is experimental**. Please [share](https://github.com/unpoly/unpoly/discussions) your experiences so we know what to keep or change.

While [revalidating](https://unpoly.com/learn/caching.md#revalidation) content rendered from a stale cache entry, all [targeted fragments](https://unpoly.com/learn/targeting-fragments.md) are assigned the `.up-revalidating` class.

The class remains set while the revalidation request is loading. It is removed when the request [ends](https://unpoly.com/api/up.Request.prototype.ended.md) for any reason.

<nav aria-label="Guides">

- [Learn: Feedback classes](https://unpoly.com/learn/feedback-classes.md)

</nav>

## Example {#example}

This fragment has been rendered from an older cache entry. Unpoly will automatically send a revalidation request and marks the fragment as `.up-revalidating`:

```html
<div id="target" class="up-revalidating">
  Possibly stale content
</div>
```

You can style revalidating fragments to convey that content might be stale:

```css
.up-revalidating {
  filter: grayscale(80%);
  opacity: 0.5;
}
```