You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This works, but opens the menu event when clicking on "Another element" (or any other element in the row). To prevent that, we set the prop "no-parent-event".
But the correct way to use a QMenu is to wrap it with the trigger button:
This makes the "no-parent-event" prop ineffective and it can be removed.
Removing "no-parent-event", i.e. activating the parent event for ui.menu even allows removing the button click handler. A button click will automatically open the menu. In short:
I think this is very nice. And it's closer to how Quasar works by default. Therefore we want to remove the "no-parent-event" prop. Since it is a braking change, we schedule it for the 1.3.0 release.
The text was updated successfully, but these errors were encountered:
Description
Originally we misunderstood the QMenu API and placed the menu element next to its trigger button:
This works, but opens the menu event when clicking on "Another element" (or any other element in the row). To prevent that, we set the prop "no-parent-event".
But the correct way to use a QMenu is to wrap it with the trigger button:
This makes the "no-parent-event" prop ineffective and it can be removed.
Removing "no-parent-event", i.e. activating the parent event for
ui.menu
even allows removing the button click handler. A button click will automatically open the menu. In short:I think this is very nice. And it's closer to how Quasar works by default. Therefore we want to remove the "no-parent-event" prop. Since it is a braking change, we schedule it for the 1.3.0 release.
The text was updated successfully, but these errors were encountered: