Is it possible to reproduce the behavior of the “tag” attribute in local notifications?
Following the documentation, the "tag" attribute can:
If specified and a notification with the same tag is already being shown, the new notification replaces the existing one in the notification drawer

add a comment |
Following the documentation, the "tag" attribute can:
If specified and a notification with the same tag is already being shown, the new notification replaces the existing one in the notification drawer

add a comment |
Following the documentation, the "tag" attribute can:
If specified and a notification with the same tag is already being shown, the new notification replaces the existing one in the notification drawer

Following the documentation, the "tag" attribute can:
If specified and a notification with the same tag is already being shown, the new notification replaces the existing one in the notification drawer


edited Jan 5 at 13:29
Douglas Moreira
asked Jan 3 at 1:48


Douglas MoreiraDouglas Moreira
313
313
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Well, there is the NotificationManager.notify()
that has the tag
parameter:
Post a notification to be shown in the status bar. If a notification with the same tag and id has already been posted by your application and has not yet been canceled, it will be replaced by the updated information.
But even if you don't use the one with tag
, simply notifying the NotifsManager with a notification with the same id
would replace it:
Post a notification to be shown in the status bar. If a notification with the same id has already been posted by your application and has not yet been canceled, it will be replaced by the updated information.
I figured that passing the "tag" by itself would already replace the notification, but if the id is different it has no effect whatsoever. I thought it best to use the second approach and use the "id" to replace the notification. Thanks @al
– Douglas Moreira
Jan 5 at 13:33
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54015386%2fis-it-possible-to-reproduce-the-behavior-of-the-tag-attribute-in-local-notific%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Well, there is the NotificationManager.notify()
that has the tag
parameter:
Post a notification to be shown in the status bar. If a notification with the same tag and id has already been posted by your application and has not yet been canceled, it will be replaced by the updated information.
But even if you don't use the one with tag
, simply notifying the NotifsManager with a notification with the same id
would replace it:
Post a notification to be shown in the status bar. If a notification with the same id has already been posted by your application and has not yet been canceled, it will be replaced by the updated information.
I figured that passing the "tag" by itself would already replace the notification, but if the id is different it has no effect whatsoever. I thought it best to use the second approach and use the "id" to replace the notification. Thanks @al
– Douglas Moreira
Jan 5 at 13:33
add a comment |
Well, there is the NotificationManager.notify()
that has the tag
parameter:
Post a notification to be shown in the status bar. If a notification with the same tag and id has already been posted by your application and has not yet been canceled, it will be replaced by the updated information.
But even if you don't use the one with tag
, simply notifying the NotifsManager with a notification with the same id
would replace it:
Post a notification to be shown in the status bar. If a notification with the same id has already been posted by your application and has not yet been canceled, it will be replaced by the updated information.
I figured that passing the "tag" by itself would already replace the notification, but if the id is different it has no effect whatsoever. I thought it best to use the second approach and use the "id" to replace the notification. Thanks @al
– Douglas Moreira
Jan 5 at 13:33
add a comment |
Well, there is the NotificationManager.notify()
that has the tag
parameter:
Post a notification to be shown in the status bar. If a notification with the same tag and id has already been posted by your application and has not yet been canceled, it will be replaced by the updated information.
But even if you don't use the one with tag
, simply notifying the NotifsManager with a notification with the same id
would replace it:
Post a notification to be shown in the status bar. If a notification with the same id has already been posted by your application and has not yet been canceled, it will be replaced by the updated information.
Well, there is the NotificationManager.notify()
that has the tag
parameter:
Post a notification to be shown in the status bar. If a notification with the same tag and id has already been posted by your application and has not yet been canceled, it will be replaced by the updated information.
But even if you don't use the one with tag
, simply notifying the NotifsManager with a notification with the same id
would replace it:
Post a notification to be shown in the status bar. If a notification with the same id has already been posted by your application and has not yet been canceled, it will be replaced by the updated information.
answered Jan 3 at 4:30


AL.AL.
24.8k858193
24.8k858193
I figured that passing the "tag" by itself would already replace the notification, but if the id is different it has no effect whatsoever. I thought it best to use the second approach and use the "id" to replace the notification. Thanks @al
– Douglas Moreira
Jan 5 at 13:33
add a comment |
I figured that passing the "tag" by itself would already replace the notification, but if the id is different it has no effect whatsoever. I thought it best to use the second approach and use the "id" to replace the notification. Thanks @al
– Douglas Moreira
Jan 5 at 13:33
I figured that passing the "tag" by itself would already replace the notification, but if the id is different it has no effect whatsoever. I thought it best to use the second approach and use the "id" to replace the notification. Thanks @al
– Douglas Moreira
Jan 5 at 13:33
I figured that passing the "tag" by itself would already replace the notification, but if the id is different it has no effect whatsoever. I thought it best to use the second approach and use the "id" to replace the notification. Thanks @al
– Douglas Moreira
Jan 5 at 13:33
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54015386%2fis-it-possible-to-reproduce-the-behavior-of-the-tag-attribute-in-local-notific%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown