syncfusion-react-notifications

v2026.09.24

Comprehensive guide for implementing Syncfusion React Notification components including Badge, Message, Skeleton, Toast, and Spinner. Use this when applying status indicators and badges with color variants and shapes; showing informational, success, warning, or error messages; configuring severity levels and display variants (Text, Outlined, Filled); handling message dismissal; toast positioning, toast templates, toast animations; displaying skeleton loading placeholders with shimmer animations (Wave, Pulse, Fade) and shapes (Circle, Rectangle, Text); or customizing notification appearance and accessibility.

GitHub
Install command
npx skhub add syncfusion/syncfusion-react-notifications
Markdown
SKILL.md

Implementing Syncfusion React Notifications

Toast

The Syncfusion React Toast component displays brief, non-intrusive notifications that auto-dismiss after a configurable timeout. Toasts support rich content through templates, action buttons, animated entry/exit, precise positioning, and programmatic control via ToastUtility.

πŸ›‘ Agentic use: Do not execute multiple steps autonomously. Confirm with the user before each action (install, run, file creation).

Package and Setup

πŸ“„ Read: references/getting-started.md

  • Installing @syncfusion/ej2-react-notifications πŸ›‘ STOP β€” Do not install packages autonomously. Ask the user to run: npm install @syncfusion/ej2-react-notifications@33.x.x --save. Verify with npm audit
  • CSS imports for all required themes
  • Basic ToastComponent usage (class and functional patterns)
  • Rendering toast in a custom target container
  • Triggering show in the created event

Documentation and Navigation Guide

Configuration and Layout

πŸ“„ Read: references/configuration.md

  • Setting title and content (plain text, HTML, elements)
  • Custom target container for scoped notifications
  • showCloseButton for manual dismissal
  • showProgressBar and progressDirection (Ltr / Rtl)
  • newestOnTop stacking order
  • width and height dimensions (px, %, auto)

Positioning

πŸ“„ Read: references/position.md

  • Nine predefined X/Y positions (Left, Center, Right / Top, Bottom)
  • Custom pixel and percentage coordinates
  • Targeting a container element for relative positioning
  • Multiple Toast instances at different screen positions

Timeout and Dismissal

πŸ“„ Read: references/timeout-and-dismissal.md

  • timeOut property (default 5000 ms)
  • extendedTimeout on hover (default 1000 ms)
  • Static persistent toasts with timeOut: 0
  • Click-to-close via clickToClose in the click event
  • Preventing mobile swipe dismissal with beforeClose

Templates and Styling

πŸ“„ Read: references/templates-and-styling.md

  • template property with HTML strings and DOM selectors
  • Dynamic templates passed at show() call time
  • Semantic CSS classes: e-toast-success, e-toast-info, e-toast-warning, e-toast-danger
  • CSS selectors for title, content, icon, and background customization

Animation

πŸ“„ Read: references/animation.md

  • animation property with show and hide effect settings
  • Available effects: FadeIn, FadeZoomIn, SlideBottomIn, ZoomIn, FlipLeftUpIn, and more
  • Default: FadeIn / FadeOut
  • Accessibility: reduced-motion considerations

Toast Services and Advanced Patterns

πŸ“„ Read: references/toast-services.md

  • ToastUtility.show() for quick toasts without component instantiation
  • Four predefined types: Information, Success, Error, Warning
  • Passing a full ToastModel to ToastUtility.show()
  • Playing audio on beforeOpen
  • Restricting maximum simultaneous toasts with beforeOpen
  • Preventing duplicate toasts using beforeOpen + close

Accessibility

πŸ“„ Read: references/accessibility.md

  • WAI-ARIA: role="alert", aria-live="assertive", aria-label
  • WCAG 2.2, Section 508, ADA compliance
  • Screen reader support (JAWS, NVDA, VoiceOver)
  • RTL support via enableRtl
  • Mobile and accessibility checker validation

API Reference

πŸ“„ Read: references/api.md

  • All properties with types, defaults, and descriptions
  • show() and hide() method signatures
  • All events: beforeOpen, open, click, beforeClose, close, created, destroyed, beforeSanitizeHtml

Quick Start Example

πŸ›‘ STOP β€” Do not start the dev server autonomously. Ask the user to run: npm run dev after setup.

import { ToastComponent } from '@syncfusion/ej2-react-notifications';
import '@syncfusion/ej2-base/styles/tailwind3.css';
import '@syncfusion/ej2-react-notifications/styles/tailwind3.css';
import { useRef } from 'react';

function App() {
  const toastRef = useRef<ToastComponent>(null);

  return (
    <>
      <button onClick={() => toastRef.current?.show()}>Show Toast</button>
      <ToastComponent
        ref={toastRef}
        title="Success!"
        content="Your changes have been saved."
        cssClass="e-toast-success"
        position={{ X: 'Right', Y: 'Bottom' }}
        timeOut={4000}
        showProgressBar={true}
        showCloseButton={true}
      />
    </>
  );
}

Quick Utility Toast (No Component Needed)

import { ToastUtility } from '@syncfusion/ej2-react-notifications';

// Show a success toast instantly
ToastUtility.show('File saved successfully', 'Success', 3000);

// Show an error toast
ToastUtility.show('Connection failed', 'Error', 5000);

Common Patterns

Semantic type toasts

Use cssClass with e-toast-success, e-toast-info, e-toast-warning, e-toast-danger for visual differentiation β€” see references/templates-and-styling.md.

Static/persistent toasts

Set timeOut: 0 with showCloseButton: true for notifications users must explicitly dismiss β€” see references/timeout-and-dismissal.md.

Action-required toasts

Use the buttons property to add Ignore/Confirm/Undo buttons β€” see references/configuration.md.

Prevent duplicates

Use the beforeOpen event to cancel duplicate toasts already on screen β€” see references/toast-services.md.

Limit max visible toasts

Cap simultaneous toasts at N using beforeOpen and element.childElementCount β€” see references/toast-services.md.

Message

The Syncfusion MessageComponent displays contextual messages with visual severity indicatorsβ€”icons and colorsβ€”to communicate importance and context to end users. It supports five severity levels, three visual variants, close-icon dismissal, custom templates, and full accessibility compliance.

πŸ›‘ Agentic use: Do not execute multiple steps autonomously. Confirm with the user before each action (install, run, file creation).

Navigation Guide

Getting Started

πŸ“„ Read: references/message-getting-started.md

  • Installation of @syncfusion/ej2-react-notifications πŸ›‘ STOP β€” Do not install packages autonomously. Ask the user to run: npm install @syncfusion/ej2-react-notifications@33.x.x --save. Verify with npm audit
  • CSS imports and theme configuration
  • Rendering the first MessageComponent
  • Content via content prop or JSX children
  • Running the Vite development server

Severity Levels

πŸ“„ Read: references/message-severities.md

  • Five severity levels: Normal, Success, Info, Warning, Error
  • severity prop usage and valid values
  • Visual distinctions (icons and colors per severity)
  • Choosing the right severity for your use case

Display Variants

πŸ“„ Read: references/message-variants.md

  • Three variants: Text (default), Outlined, Filled
  • variant prop usage
  • Combining variant with severity
  • Visual trade-offs and when to use each

Icons and Close Icon

πŸ“„ Read: references/message-icons-and-close.md

  • Severity icon visibility: showIcon prop (default true)
  • Disabling severity icons
  • Custom severity icons via cssClass CSS overrides
  • Close icon: showCloseIcon prop (default false)
  • closed event handler for dismiss callbacks
  • Toggling visibility with the visible prop

Customization and Templates

πŸ“„ Read: references/message-customization.md

  • Content alignment: left (default), center (e-content-center), right (e-content-right)
  • Custom appearance with cssClass
  • CSS-only message rendering (no JS, pure HTML + CSS)
  • Content templates: JSX element or render function via content prop
  • RTL support via enableRtl
  • Persistence with enablePersistence

Accessibility

πŸ“„ Read: references/message-accessibility.md

  • WCAG 2.2, Section 508, ADA compliance
  • WAI-ARIA attributes (role=alert, aria-label)
  • Keyboard navigation (Tab, Enter/Space)
  • Screen reader support

API Reference

πŸ“„ Read: references/message-api.md

  • All properties with types, defaults, and descriptions
  • Methods: destroy, getPersistData
  • Events: closed, created, destroyed
  • MessageCloseEventArgs interface
  • Severity and Variant enum values

Quick Start

πŸ›‘ STOP β€” Do not start the dev server autonomously. Ask the user to run: npm run dev after setup.

npm install @syncfusion/ej2-react-notifications@33.x.x --save
npm audit
/* src/App.css */
@import '../node_modules/@syncfusion/ej2-base/styles/tailwind3.css';
@import '../node_modules/@syncfusion/ej2-react-notifications/styles/tailwind3.css';
import { MessageComponent } from '@syncfusion/ej2-react-notifications';
import './App.css';

function App() {
  return (
    <MessageComponent content="Please read the comments carefully" />
  );
}
export default App;

Common Patterns

Severity Messages

<MessageComponent content="Editing is restricted" />
<MessageComponent content="Operation completed" severity="Success" />
<MessageComponent content="Read these notes" severity="Info" />
<MessageComponent content="Check your connection" severity="Warning" />
<MessageComponent content="Submission failed" severity="Error" />

Variant + Severity Combo

<MessageComponent content="Editing is restricted" variant="Filled" />
<MessageComponent content="Operation completed" severity="Success" variant="Outlined" />
<MessageComponent content="Submission failed" severity="Error" variant="Filled" />

Dismissible Message

import { useState } from 'react';

function App() {
  const [visible, setVisible] = useState(true);
  return (
    <MessageComponent
      content="Your session will expire soon"
      severity="Warning"
      showCloseIcon={true}
      visible={visible}
      closed={() => setVisible(false)}
    />
  );
}

Content Template

const contentTemplate = () => (
  <div>
    <h4>Build succeeded</h4>
    <p>All 42 tests passed.</p>
  </div>
);

<MessageComponent content={contentTemplate} severity="Success" />

Skeleton

The Syncfusion React SkeletonComponent renders animated placeholder shapes that mimic the layout of loading content. It reduces perceived load time and communicates progress to users with configurable shapes, shimmer animations, and full accessibility support.

Package: @syncfusion/ej2-react-notifications

πŸ›‘ Agentic use: Do not execute multiple steps autonomously. Confirm with the user before each action (install, run, file creation).


Navigation Guide

Getting Started

πŸ“„ Read: references/skeleton-getting-started.md

  • Installing @syncfusion/ej2-react-notifications πŸ›‘ STOP β€” Do not install packages autonomously. Ask the user to run: npm install @syncfusion/ej2-react-notifications@33.x.x --save. Verify with npm audit
  • CSS theme imports (tailwind3)
  • Minimal SkeletonComponent setup with height and width
  • Running the Vite/React app

Shapes

πŸ“„ Read: references/skeleton-shapes.md

  • shape prop: "Circle", "Square", "Rectangle", "Text" (default)
  • Dimension rules: width required for Circle/Square; width + height for Rectangle/Text
  • Building multi-shape card skeleton layouts
  • Choosing the right shape for avatar, image, text, and icon placeholders

Shimmer Effects

πŸ“„ Read: references/skeleton-shimmer-effect.md

  • shimmerEffect prop: "Wave" (default), "Pulse", "Fade"
  • Visual behavior of each effect type
  • List skeleton example with Pulse effect
  • Selecting an effect to match UI context

Styles and Visibility

πŸ“„ Read: references/skeleton-styles.md

  • cssClass prop for custom CSS overrides (wave color, background, animation speed)
  • visible prop to toggle skeleton on/off based on loading state
  • Transition pattern: skeleton β†’ actual content
  • CSS variable customization

Accessibility

πŸ“„ Read: references/skeleton-accessibility.md

  • WCAG 2.2, Section 508, ADA compliance
  • WAI-ARIA attributes: role="status", aria-label, aria-live, aria-busy
  • label prop for accessible skeleton names
  • RTL support via enableRtl
  • prefers-reduced-motion respect

API Reference

πŸ“„ Read: references/skeleton-api.md

  • All properties: cssClass, enablePersistence, enableRtl, height, label, locale, shape, shimmerEffect, visible, width
  • Methods: destroy()
  • SkeletonType and ShimmerEffect enum values

Quick Start

πŸ›‘ STOP β€” Do not start the dev server autonomously. Ask the user to run: npm run dev after setup.

npm install @syncfusion/ej2-react-notifications@33.x.x --save
npm audit
/* src/App.css */
@import "../node_modules/@syncfusion/ej2-base/styles/tailwind3.css";
@import "../node_modules/@syncfusion/ej2-notifications/styles/tailwind3.css";
import { SkeletonComponent } from '@syncfusion/ej2-react-notifications';
import * as React from 'react';
import './App.css';

function App() {
  return (
    <SkeletonComponent height="15px" width="100%" />
  );
}
export default App;

Common Patterns

Profile Card Skeleton

import { SkeletonComponent } from '@syncfusion/ej2-react-notifications';
import * as React from 'react';

function ProfileCardSkeleton() {
  return (
    <div style={{ display: 'flex', alignItems: 'center', gap: '12px', padding: '16px' }}>
      {/* Avatar placeholder */}
      <SkeletonComponent shape="Circle" width="48px" />
      {/* Name and subtitle placeholders */}
      <div style={{ flex: 1 }}>
        <SkeletonComponent width="60%" height="15px" />
        <br />
        <SkeletonComponent width="40%" height="12px" />
      </div>
    </div>
  );
}
export default ProfileCardSkeleton;

Toggle Skeleton on Data Load

import { SkeletonComponent } from '@syncfusion/ej2-react-notifications';
import * as React from 'react';

function DataCard() {
  const [loading, setLoading] = React.useState(true);
  const [content, setContent] = React.useState('');

  React.useEffect(() => {
    setTimeout(() => {
      setContent('Data loaded successfully');
      setLoading(false);
    }, 2000);
  }, []);

  return (
    <div>
      {loading ? (
        <SkeletonComponent width="80%" height="20px" />
      ) : (
        <p>{content}</p>
      )}
    </div>
  );
}
export default DataCard;

Shimmer List with Pulse Effect

import { SkeletonComponent } from '@syncfusion/ej2-react-notifications';
import * as React from 'react';

function ListSkeleton() {
  return (
    <ul style={{ listStyle: 'none', padding: 0 }}>
      {[1, 2, 3].map((i) => (
        <li key={i} style={{ display: 'flex', gap: '10px', marginBottom: '12px' }}>
          <SkeletonComponent shape="Circle" width="40px" shimmerEffect="Pulse" />
          <div style={{ flex: 1 }}>
            <SkeletonComponent width="70%" height="14px" shimmerEffect="Pulse" />
            <br />
            <SkeletonComponent width="45%" height="12px" shimmerEffect="Pulse" />
          </div>
        </li>
      ))}
    </ul>
  );
}
export default ListSkeleton;

Key Props at a Glance

PropTypeDefaultPurpose
shape'Text' | 'Circle' | 'Square' | 'Rectangle''Text'Skeleton shape variant
widthstring | number''Width; required for Circle/Square
heightstring | number''Height; used for Rectangle/Text
shimmerEffect'Wave' | 'Pulse' | 'Fade''Wave'Animation style
visiblebooleantrueShow/hide skeleton
cssClassstring''Custom CSS class(es)
labelstring'Loading…'ARIA label for accessibility
enableRtlbooleanfalseRight-to-left rendering
enablePersistencebooleanfalsePersist state across reloads

Spinner

A skill for implementing the Syncfusion React Spinner β€” a load indicator that blocks user interaction with a target element while an operation is in progress.

πŸ›‘ Agentic use: Do not execute multiple steps autonomously. Confirm with the user before each action (install, run, file creation).

Documentation

Getting Started

πŸ“„ Read: references/spinner-getting-started.md

  • Installation: πŸ›‘ STOP β€” Do not install packages autonomously. Ask the user to run: npm install @syncfusion/ej2-react-popups@33.x.x --save. Verify with npm audit
  • CSS theme imports (ej2-base + ej2-react-popups)
  • Basic functional and class component patterns
  • createSpinner β†’ showSpinner workflow
  • Show/hide control
  • Full-page overlay spinner
  • Troubleshooting missing styles and TypeScript errors

Spinner Features

πŸ“„ Read: references/spinner-features.md

  • Global spinner configuration with setSpinner
  • All SpinnerType values (Material, Bootstrap5, Fluent2, etc.)
  • Spinner size via width property
  • Label text alongside spinner
  • Custom HTML template support
  • Show/hide toggle patterns
  • Multiple spinners on one page
  • Async data fetching with finally cleanup
  • React state + spinner synchronization
  • Spinner inside cards and modals

API Reference

πŸ“„ Read: references/spinner-api.md

  • createSpinner(args: SpinnerArgs) β€” full signature and params
  • showSpinner(container: HTMLElement) β€” signature
  • hideSpinner(container: HTMLElement) β€” signature
  • setSpinner(args: SetSpinnerArgs) β€” signature
  • SpinnerArgs interface (target, width, label, cssClass, template, type)
  • SetSpinnerArgs interface (template, cssClass, type)
  • All 11 SpinnerType values
  • CSS import paths per theme
  • Common invalid API gotchas

Customization

πŸ“„ Read: references/spinner-customization.md

  • cssClass for CSS hook customization
  • width for spinner icon sizing
  • template for custom HTML animations
  • setSpinner for global defaults
  • Overriding spinner colors via CSS
  • Label positioning with CSS
  • Overlay backdrop customization
  • Theme-specific type mapping
  • Responsive spinner patterns

Accessibility

πŸ“„ Read: references/spinner-accessibility.md

  • aria-busy on the loading region
  • aria-live region for screen reader announcements
  • type: 'HighContrast' for high contrast displays
  • Keyboard accessibility (trigger focus, return focus)
  • Focus management patterns
  • Complete accessible spinner pattern
  • WCAG 2.1 compliance checklist

Quick Start

Minimal Spinner (Functional Component)

πŸ›‘ STOP β€” Do not start the dev server autonomously. Ask the user to run: npm run dev after setup.

import { createSpinner, showSpinner } from '@syncfusion/ej2-react-popups';
import * as React from 'react';
import { useEffect } from 'react';
import './App.css';

function App() {
  useEffect(() => {
    createSpinner({
      target: document.getElementById('container') as HTMLElement
    });
    showSpinner(document.getElementById('container') as HTMLElement);
  }, []);

  return (
    <div id="container" style={{ height: '200px' }} />
  );
}

export default App;

Spinner with Show/Hide Toggle

import { createSpinner, showSpinner, hideSpinner } from '@syncfusion/ej2-react-popups';
import { useEffect, useRef, useState } from 'react';

function DataLoader() {
  const ref = useRef<HTMLDivElement>(null);
  const [loading, setLoading] = useState(false);

  useEffect(() => {
    if (ref.current) {
      createSpinner({ target: ref.current, label: 'Loading...' });
    }
  }, []);

  const load = async () => {
    setLoading(true);
    showSpinner(ref.current as HTMLElement);
    try {
      await fetchData();
    } finally {
      hideSpinner(ref.current as HTMLElement);
      setLoading(false);
    }
  };

  return (
    <div>
      <button onClick={load} disabled={loading}>Load Data</button>
      <div ref={ref} style={{ height: '200px', position: 'relative' }} />
    </div>
  );
}

Global Spinner Type

import { setSpinner } from '@syncfusion/ej2-react-popups';

// Call BEFORE any createSpinner β€” sets global default type
setSpinner({ type: 'Bootstrap5' });

Common Patterns

Pattern 1: Async Fetch with Cleanup

const fetchWithSpinner = async (container: HTMLElement) => {
  showSpinner(container);
  try {
    const data = await fetch('/api/data').then(r => r.json());
    return data;
  } finally {
    hideSpinner(container); // Always hide, even on error
  }
};

Pattern 2: React State Sync

useEffect(() => {
  if (!ref.current) return;
  if (isLoading) {
    showSpinner(ref.current);
  } else {
    hideSpinner(ref.current);
  }
}, [isLoading]);

Pattern 3: Full-Page Loading

useEffect(() => {
  createSpinner({ target: document.body, label: 'Initializing...' });
  showSpinner(document.body);

  initializeApp().finally(() => hideSpinner(document.body));
}, []);

Pattern 4: Spinner with Custom Type

createSpinner({
  target: el,
  type: 'Fluent2',
  width: '40px',
  label: 'Processing...',
  cssClass: 'my-overlay'
});

Key API Quick Reference

FunctionSignaturePurpose
createSpinner(args: SpinnerArgs) => voidInitialize spinner on DOM element
showSpinner(el: HTMLElement) => voidShow an existing spinner
hideSpinner(el: HTMLElement) => voidHide a visible spinner
setSpinner(args: SetSpinnerArgs) => voidSet global defaults for all spinners

SpinnerArgs properties: target (required), width, label, cssClass, template, type

SpinnerType values: 'Material' | 'Material3' | 'Fabric' | 'Bootstrap' | 'Bootstrap4' | 'Bootstrap5' | 'HighContrast' | 'Tailwind' | 'Tailwind3' | 'Fluent' | 'Fluent2'

Critical Rules

  • ❌ No SpinnerComponent class β€” import { SpinnerComponent } does NOT exist
  • βœ… Only use: createSpinner, showSpinner, hideSpinner, setSpinner
  • ❌ Do NOT use: color, size, visible, isLoading as SpinnerArgs β€” they don't exist
  • βœ… Valid SpinnerArgs: target, width, label, cssClass, template, type
  • ⚠️ Call createSpinner BEFORE showSpinner β€” order matters
  • ⚠️ Put spinner logic in useEffect β€” the DOM element must exist before calling createSpinner
  • βœ… Always call hideSpinner in finally β€” prevents stuck loading states

Troubleshooting

IssueSolution
Spinner not showingEnsure createSpinner is called before showSpinner; check DOM element exists
Spinner stays visibleCall hideSpinner in finally block; check for unhandled promise rejections
No animationVerify both ej2-base and ej2-react-popups CSS imported; ej2-base must come first
TypeScript errorCast: document.getElementById('id') as HTMLElement or use useRef<HTMLDivElement>
Spinner outside boundsAdd position: relative to target element
Wrong themeSet type to match your app's CSS theme (e.g., 'Fluent2' for Fluent 2 CSS)

Related Components

  • Progress Bar β€” For determinate progress with a percentage
  • Skeleton β€” For content placeholder/shimmer loading patterns
  • Toast β€” For non-blocking loading notifications
  • Dialog β€” For modal loading states that require user acknowledgment

Resources

Badge

The Syncfusion React Badge is a pure CSS component β€” no React component class to import. Badges are applied by adding CSS modifier classes to a <span> (or <a>) element nested inside the target UI element.

Package: @syncfusion/ej2-react-notifications

πŸ›‘ Agentic use: Do not execute multiple steps autonomously. Confirm with the user before each action (install, run, file creation).

Key Features

  • 8 color variants β€” primary, secondary, success, danger, warning, info, light, dark
  • Shape types β€” circle, pill, link, notification, dot, overlap
  • Positioning β€” top (default) and bottom placement on parent elements
  • Customization β€” custom colors, sizes, and arbitrary positions via CSS
  • ListView integration β€” embed badges in list items with dynamic content

Navigation Guide

Getting Started

πŸ“„ Read: references/getting-started.md

  • Package installation: πŸ›‘ STOP β€” Do not install packages autonomously. Ask the user to run: npm install @syncfusion/ej2-react-notifications@33.x.x --save. Verify with npm audit
  • Adding the first badge to a React component
  • Minimal working example
  • Running the application

Badge Types and Shapes

πŸ“„ Read: references/types-and-shapes.md

  • 8 predefined color variants and their semantic purpose
  • Circle, pill, link, notification, dot, overlap shape types
  • Badge positioning (top vs bottom)
  • When to combine modifier classes (e.g., overlap + notification + circle)

Customization

πŸ“„ Read: references/customization.md

  • Custom color overrides with CSS classes
  • Adjusting badge size via font-size
  • Custom positioning (left-top, left-bottom) with CSS overrides
  • When to use custom CSS vs built-in modifier classes

How-To Guides

πŸ“„ Read: references/how-to.md

  • Integrate badges into a ListView component
  • Update badge content dynamically (increment counts)
  • React pattern for badge state management using DOM updates

Quick Start

1. Install the package:

npm install @syncfusion/ej2-react-notifications@33.x.x --save
npm audit

2. Add CSS to src/App.css:

@import "../node_modules/@syncfusion/ej2-base/styles/tailwind3.css";
@import "../node_modules/@syncfusion/ej2-notifications/styles/tailwind3.css";

3. Add a badge in your component:

import * as React from 'react';
import './App.css';

function App() {
  return (
    <h1>Badge Component <span className="e-badge e-badge-primary">New</span></h1>
  );
}
export default App;

Common Patterns

Notification badge on an icon

// Parent must have position: relative
<div className="badge-block">
  <div className="skype svg_icons"></div>
  <span className="e-badge e-badge-success e-badge-overlap e-badge-notification">99+</span>
</div>

Dot status indicator (bottom position)

<div className="badge-block">
  <div className="firefox svg_icons"></div>
  <span className="e-badge e-badge-success e-badge-overlap e-badge-dot e-badge-bottom"></span>
</div>

Pill-shaped label

<h1>Messages <span className="e-badge e-badge-primary e-badge-pill">New</span></h1>

CSS Class Reference

ClassPurpose
e-badgeRequired base class for all badges
e-badge-primary / e-badge-{color}Color variant
e-badge-pillPill (rounded rectangle) shape
e-badge-circleCircle shape
e-badge-notificationNotification counter badge
e-badge-dotMinimalist dot badge (no text)
e-badge-overlapOverlaps the parent element edge
e-badge-bottomPositions badge at bottom instead of top
Discovery
Tags

No tags published for this skill.

Version
Latest version metadata

Version

v2026.09.24

Published

Sep 24, 2026

Category

Uncategorized

License

Not specified

Source path

skills/syncfusion-react-notifications

Default branch

master

Latest commit

b6f4882

Tree SHA

ffab56b