# Discourse w/ Topic as Pinned then Banner on Chrome Incognito **URL:** \ **Category:** Support\ **Created:** [2016年十一月15日 13:03 UTC](https://meta.discourse.org/t/discourse-w-topic-as-pinned-then-banner-on-chrome-incognito/52918 "2016-11-15T13:03:01Z")\ **Posts on this page:** 17\ **Page:** 1
**Author:** ![cageycat](https://avatars.discourse-cdn.com/v4/letter/c/d6d6ee/32.png) [@cageycat](https://meta.discourse.org/u/cageycat)\ **Post date:** [2016年十一月15日 13:03 UTC](https://meta.discourse.org/t/discourse-w-topic-as-pinned-then-banner-on-chrome-incognito/52918/1 "2016-11-15T13:03:01Z")
I use Chrome Incognito to access a Forum run on Discourse. In Sept, an Admin posted a Pinned topic. In Oct, she changed the setting to: “This topic is now a banner. It will appear at the top of every page until it is dismissed by the user.” On Incognito, that means I’ve “dismissed” that post/thread every day, multiple times a day, since it was first created Sept 9th. How do I make this go away so I’m not X-ing out (dismissing the post) multiple times a day for the rest of my time on that Forum? (Regular Chrome, of course, easily dismissed the post/thread long ago and retained that information. ) I recognize it likely has to do with Incognito purposely not retaining browsing history and possibly related to info stored in a cookie? Do I need to delete the cookie? If so, will I need to look for that site’s forum cookie, or a Discourse cookie? If not a cookie, what can I do to fix this? It likely affects anyone else using Incognito on that Forum. ---
**Author:** ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)\ **Post date:** [2016年十一月15日 14:29 UTC](https://meta.discourse.org/t/discourse-w-topic-as-pinned-then-banner-on-chrome-incognito/52918/2 "2016-11-15T14:29:22Z")
This is working as intended. You browse the forum in Incognito mode, but do you log in? If you do log in, the pin status will be saved into your account. ---
**Author:** ![cageycat](https://avatars.discourse-cdn.com/v4/letter/c/d6d6ee/32.png) [@cageycat](https://meta.discourse.org/u/cageycat)\ **Post date:** [2016年十一月15日 17:43 UTC](https://meta.discourse.org/t/discourse-w-topic-as-pinned-then-banner-on-chrome-incognito/52918/3 "2016-11-15T17:43:04Z")
I log in via the company that runs the forum. You _misunderstood_ my point— The pinned post was unpinned in Oct. But in Chrome Incognito, logged into the forum, that post returns no matter how many times a day that I dismiss it. As soon as I close the browser window (effectively becoming ‘logged out’), and re-open the browser window, and re-log in, presto-magic the same post is back. If I sign in 10x a day… 20x a day… I have to RE-“dismiss” it on every visit. \*It SHOULD stay dismissed when any user dismisses the post, no matter what browser they are using. Surely, there must be a way to not nag users who use Chrome Incognito who have already dismissed one of these posts hundreds & hundreds of times, multiple times a day and every singe day since October??? ---
**Author:** ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)\ **Post date:** [2016年十一月15日 22:29 UTC](https://meta.discourse.org/t/discourse-w-topic-as-pinned-then-banner-on-chrome-incognito/52918/4 "2016-11-15T22:29:31Z")
Storing the closed state of the banner requires cookies, when you use incognito all cookies are deleted when you close the tab. So it becomes impossible. ---
**Author:** ![cageycat](https://avatars.discourse-cdn.com/v4/letter/c/d6d6ee/32.png) [@cageycat](https://meta.discourse.org/u/cageycat)\ **Post date:** [2016年十一月16日 09:05 UTC](https://meta.discourse.org/t/discourse-w-topic-as-pinned-then-banner-on-chrome-incognito/52918/5 "2016-11-16T09:05:26Z")
Is there anything you can recommend that I can do to make the regular Chrome w/ its cookie take precedence? Is there any way to override the issue showing in Incognito? Based on your premise that cookies are deleted when closing Incognito, it is illogical why the banner thread remains showing in Incognito—since it **shouldn’t** be “remembering” anything at all from any browsing session (and it is displaying correctly in Regular chrome)… but the banner thread persists since early October only in Incognito. Do you see the flaw I’m pointing out in this scenario? There must be some way to bypass this issue?? ---
**Author:** ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)\ **Post date:** [2016年十一月16日 09:22 UTC](https://meta.discourse.org/t/discourse-w-topic-as-pinned-then-banner-on-chrome-incognito/52918/6 "2016-11-16T09:22:15Z")
The “remembering” in this case is remembering that it was closed. ---
**Author:** ![cageycat](https://avatars.discourse-cdn.com/v4/letter/c/d6d6ee/32.png) [@cageycat](https://meta.discourse.org/u/cageycat)\ **Post date:** [2016年十一月16日 09:42 UTC](https://meta.discourse.org/t/discourse-w-topic-as-pinned-then-banner-on-chrome-incognito/52918/7 "2016-11-16T09:42:25Z")
What’s odder is, I used Regular Chrome during Sept. Therefore, Incognito shouldn’t have seen anything to “forget” nor need to remember it was open as a banner— or closed. There’s some oddity here that is not making sense. So does this mean if I use Regular Chrome for the next 16 wks or 16 months, and go back to using Incognito, that Incognito will still show a banner that was dismissed Oct 2016 ? ---
**Author:** ![riking](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/riking/32/170938_2.png) [@riking](https://meta.discourse.org/u/riking)\ **Post date:** [2016年十一月16日 09:46 UTC](https://meta.discourse.org/t/discourse-w-topic-as-pinned-then-banner-on-chrome-incognito/52918/8 "2016-11-16T09:46:28Z")
Banners are supposed to show for anonymous users who have never logged into the forum. Clicking the ✖ stores that you dismissed the banner in the browser storage. Closing the last open Incognito window discards all browser storage. Therefore, clearing browsing data results in the banner notice being shown again. * * * Everything involved is working as designed, and together it results in an odd user experience for you. Have you considered creating a new Chrome profile instead? ---
**Author:** ![cageycat](https://avatars.discourse-cdn.com/v4/letter/c/d6d6ee/32.png) [@cageycat](https://meta.discourse.org/u/cageycat)\ **Post date:** [2016年十一月16日 10:13 UTC](https://meta.discourse.org/t/discourse-w-topic-as-pinned-then-banner-on-chrome-incognito/52918/9 "2016-11-16T10:13:54Z")
Perhaps Discourse can tweak this so a member can use a setting that says “Do not show any banner posts older than 30 days”. Any member logged in should not have to put up with this, no matter what browser they use. I’m not going to be forced to make new accounts to avoid an issue that should never be an issue. Users (who don’t have coding experience) should not be hog-tied into seeing a banner for the rest of their lives! I’ve been on that forum for over a year; and Moderate there, so it will not be a simple matter to change my identity to override a design flaw that happens to now haunt me. Oh, and by the way—if this is a correct explanation, why don’t ALL the other past bannered threads show on my Incognito? This banner is the only one that’s an issue. We had banner posts before…and since… none of those show. The way it works, per your explanation, is that time-sensitive and expired events will show from the beginning of time of the forum to any new user— Who wants that on a rapidly changing forum? (The banners are for a “new task”, but the new tasks for users expire about every 30-60 days. Those threads would be of no use to new users, at 1 day past, 3 mos, 6 mos, 1 yr, 2 yrs after the event expires!) Rather ridiculous and viscous cycle that’s created for users, eh? 😉 ---
**Author:** ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)\ **Post date:** [2016年十一月16日 10:58 UTC](https://meta.discourse.org/t/discourse-w-topic-as-pinned-then-banner-on-chrome-incognito/52918/10 "2016-11-16T10:58:17Z")
I would take it up with the people who run the instance, which is .. not us. They have the power to remove banners or set them as they see fit. ---
**Author:** ![fefrei](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/fefrei/32/119538_2.png) [@fefrei](https://meta.discourse.org/u/fefrei)\ **Post date:** [2016年十一月16日 11:24 UTC](https://meta.discourse.org/t/discourse-w-topic-as-pinned-then-banner-on-chrome-incognito/52918/11 "2016-11-16T11:24:01Z")
We could lower the pain by remembering that the banner is closed not only in the cookie, but in the user’s account as well. It looks like this is not happening yet. ---
**Author:** ![Mittineague](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mittineague/32/114259_2.png) [@Mittineague](https://meta.discourse.org/u/Mittineague)\ **Post date:** [2016年十一月17日 01:16 UTC](https://meta.discourse.org/t/discourse-w-topic-as-pinned-then-banner-on-chrome-incognito/52918/12 "2016-11-17T01:16:34Z")
> [@fefrei](#): > > It looks like this is not happening yet. It is. It is in the `user_profiles` tables `dismissed_banner_key` field. I think the issue is that discourse/models/user.js.es6 has ```plaintext dismissBanner(bannerKey) { this.set("dismissed_banner_key", bannerKey); ajax(`/users/${this.get('username')}`, { type: 'PUT', data: { dismissed_banner_key: bannerKey } }); }, ``` and that Chrome in incognito mode doesn’t do the required AJAX stuff. ---
**Author:** ![fefrei](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/fefrei/32/119538_2.png) [@fefrei](https://meta.discourse.org/u/fefrei)\ **Post date:** [2016年十一月17日 07:03 UTC](https://meta.discourse.org/t/discourse-w-topic-as-pinned-then-banner-on-chrome-incognito/52918/13 "2016-11-17T07:03:45Z")
> [@Mittineague](#): > > It is. True that – for some reason (probably some mistake on my part), it wasn’t working when I was testing it. Sorry for the confusion. ---
**Author:** ![cageycat](https://avatars.discourse-cdn.com/v4/letter/c/d6d6ee/32.png) [@cageycat](https://meta.discourse.org/u/cageycat)\ **Post date:** [2016年十一月17日 07:17 UTC](https://meta.discourse.org/t/discourse-w-topic-as-pinned-then-banner-on-chrome-incognito/52918/14 "2016-11-17T07:17:18Z")
GMTA… I did write to them. But I also thought it needs addressed in the programming. ---
**Author:** ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)\ **Post date:** [2019年三月29日 09:38 UTC](https://meta.discourse.org/t/discourse-w-topic-as-pinned-then-banner-on-chrome-incognito/52918/15 "2019-03-29T09:38:39Z")
---
**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\ **Post date:** [2019年四月1日 01:32 UTC](https://meta.discourse.org/t/discourse-w-topic-as-pinned-then-banner-on-chrome-incognito/52918/16 "2019-04-01T01:32:39Z")
Only alternative I can think here is writing a special incognito browser plugin from chrome that would run some custom script every time you enter incognito. Maybe there is a greasmonkey option. Stuff is working as designed here. ---
**Author:** ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)\ **Post date:** [2019年五月1日 01:32 UTC](https://meta.discourse.org/t/discourse-w-topic-as-pinned-then-banner-on-chrome-incognito/52918/17 "2019-05-01T01:32:47Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.