"Notify me" answers when tapped
- fixed The Notify me button on the chat page did nothing when tapped: no question about notifications, no explanation, nothing. It was broken on every device, but it showed most on iPhone, where the button is meant to open a short note about adding the chat to your Home Screen first. Both copies of the button (the one in the header and the one in the slim bar once the header is folded away) now respond.
Tapping "Notify me" on the chat page is supposed to do one of a few things: ask whether this device may receive notifications, quietly switch itself off if you'd already said yes, or (on an iPhone, where notifications only work from a Home Screen app) open a short note explaining the Add to Home Screen step. For a little while, the button did none of them. It looked perfectly tappable, and nothing happened.
The cause was a small wiring slip from when the chat header learned to fold away. The page carries two copies of the button, one in the open header and one in the slim bar that replaces it, and the code that makes the button work had been attached to only one of them. The wrong one, as it happens: the copy you normally see. So the visible button absorbed your tap and did nothing with it, while the hidden copy held all the behavior.
Both copies now carry the full behavior, and they stay in step: subscribing from either marks both as on, and the inline "get notified" nudge that appears under your first message clicks through the same wiring. This is fixed on the chat page you open from a link and on the one you return to from your saved bookmark.
← All changes