Queuing Issue with Notify Plugin in Quasar v2.6.0

[Sgeonwoo]

Hello. I'm running into an issue with the Notify plugin's behavior in Quasar v2.6.0 and would like to ask a question.

📝 Problem Description

The behavior of the Notify plugin is different from what's described in the official documentation.

Expected Behavior: According to the Quasar documentation, when a new notification is triggered, it should be displayed on the screen simultaneously with existing notifications (e.g., by stacking or grouping).

2025-07-14.10.32.48.mov

Actual Behavior (Queuing): In my project, the notifications act like a queue. The next notification only appears after the first one has completely disappeared due to its timeout.

2025-07-14.10.25.24.mov

---

⚙️ Environment

• Quasar Version: 2.6.0
• @quasar/app-vite: ^1.3.0
• Vue Version: ^3.3.4

---

📄 Current Code

The issue occurs regardless of the implementation method. I am currently using the direct import method with Notify.create as shown below, but the queuing behavior still persists.

// src/utils/notify-helpers.js
import { Notify } from 'quasar';

export const pushNotify = (message) => {
  Notify.create({
    message,
    color: 'black',
    textColor: 'white',
    position: 'bottom',
    timeout: 1000,
  });
};

And use like this:

// In a Vue component
import { pushNotify } from 'src/utils/notify-helpers';

// Triggered multiple times in quick succession (e.g., on button click)
pushNotify('message1');

---

What I've Tried

Tested Both Methods: I tested both the useQuasar() hook and the direct Notify.create() import. Both result in the same queuing behavior.

Checked Global Config: I confirmed there are no special global notify settings in quasar.config.js.

Tested in Isolation: I created a new test page to test without interference from other code, but the issue was identical.

---

Question

I'm wondering why the Notify plugin is behaving like a queue. Since the problem occurs with all implementation methods, including the recommended Notify.create, could this be a known bug? Or is there another environmental factor I should be investigating?
Please Let me know what I'm missing.

[Sgeonwoo]

just because of custom styling ,,,,