It could be, it’s included in extension version 2025.5.1 now:
Then wait for the update.
Unfortunately, it is not working in version 2025.5.1 on Edge… 
1 Like
Holy moly…
It was posted just a month ago. It might take even longer to get adopted.
Have any of you heard anything about it?
… I never noticed until now, that this “Update notification design” was obviously removed from the Release Notes 2025.5.2…
… as it has now reappeared in the Release Notes 2025.6.2:
PS: Also @mutilator
1 Like
That sounds very interesting. Thanks for the link and the information.
I can’t see a new version of the browser extension here yet.
Patience, young Skywalker.
1 Like
Now it is listed. But it doesn’t say anything about the redesign.
It’s a bit complicated.
As written above, the Release Notes 2025.6.2 mention the “browser extension notification redesign”. – And the Release Notes state, that (among others) browser extensions 2025.6.0 are meant by it:
But I’m not sure, who had the idea, that the Release Notes 2025.6.2 are also meant for app versions 2025.6.0 and 2025.6.1… 
All right.
Then I can test it in 5 days.
1 Like
The update has just arrived. Very fast.
Unfortunately, it has not been implemented, which is a great shame.
I personally hope, nobody should feel “ashamed”.
Most of all, that would be confusing, as it was announced in the Release Notes. 
@mutilator I moved our side-discussion about the “notifications redesign” now out of Enable specifying org/collection while adding new entry.
Thank you. I’m a bit disappointed right now.
1 Like
The new design looks very good and clean. I don’t know why I’m just seeing it now.
I just learned, that initially a “feature flag” was turned off - and it now was turned on, so that we now see the feature. 
1 Like
Please for the love of everything possible, tell me you have not changed the layout to this Huge box!
(It seems you even have to click it away before you can interact with the page again 
)
Whatever happened to being subtle yet clear, and don’t fix what ain’t broken?!
I think you should report that as a separate GitHub issue. (I can’t because I haven’t experienced this yet)