Skip to main content
All CollectionsSettings & How Tos
Adjusting the Z-Index in ProveSource to Prevent Overlapping Issues
Adjusting the Z-Index in ProveSource to Prevent Overlapping Issues

Learn how to adjust the z-index in ProveSource to prevent notifications from blocking important elements like chat widgets or floating carts

Yosi Dahan avatar
Written by Yosi Dahan
Updated over 2 weeks ago

Overview

Suppose you notice that ProveSource notifications are blocking other important elements on your website, such as a floating cart, chat widget, or other pop-ups. In that case, you can adjust the z-index value to control their stacking order.

The z-index is a CSS property that determines the vertical stacking order of elements on a web page. An element with a higher z-index appears in front of elements with lower values.

Configuring the Z-Index in ProveSource

ProveSource allows you to customize the z-index for notifications separately on desktop and mobile devices. You can adjust these settings under:

Settings > Notifications > Behavior


Steps to Adjust the Z-Index:

  1. Navigate to Settings in the left-hand menu.

  2. Click the Notifications tab.

  3. Locate the fields for Z-Index (Desktop) and Z-Index (Mobile).

  4. Enter a custom z-index value:

    • Higher values (e.g., 99) bring the notification to the front.

    • Lower values (e.g., 10) push the notification behind other elements.

  5. Click Save Changes to apply your settings.

Best Practices

  • If notifications are blocking important elements like a floating cart or chat widget, try lowering the z-index value (e.g., setting it to 1000 or lower).

  • If notifications are hidden behind other elements, increase the z-index (e.g., 9999 or higher).

  • Test the changes on both desktop and mobile to ensure notifications display correctly without interfering with other website components.

By fine-tuning the z-index settings, you can ensure ProveSource notifications integrate smoothly with your website’s layout, providing a seamless experience for visitors.

Did this answer your question?