When visiting my profile on the mobile app, my hat scrolls with the page:

hat scroll

It doesn't stay linked to my icon at the top. I'm on an iPhone 6+ running iOS 9.2 and version 1.4.1 of the SE app.


Update Actually it shipped the next day!

This will be fixed either next week or in December 2016.

I am so sad about this. Like, really, really sad.

WinterBash hats are on a separate overlay view which updates its content offset on scroll as follows:

- (void)scrollViewDidScroll:(UIScrollView *)scrollView
    self.winterBashOverlayView.contentOffset = scrollView.contentOffset;

Unfortunately, I inserted this method inside a #ifdef DEBUG block so it worked perfectly during development but is completely excluded from the release.

  • 1
    Ow. That's probably worth an expedited review request, it's somewhat time sensitive and we're going into the holidays. – Undo Dec 14 '15 at 17:07
  • Meh, why not use swift? – bjb568 Dec 14 '15 at 17:27
  • 3
    @bjb568 Because SENetworkViewController.m was created Feb 21, 2014 and Swift 1.0 was announced on June 2, 2014. – Brian Nickel Dec 14 '15 at 17:34
  • Scrolling due to toggling comment menu causes similar problem. Should I post a new question about it? – unarist Dec 14 '15 at 18:38
  • @unarist I see what you mean. It only happens if you toggle the menu when scrolled near the bottom. You can add a new issue if you want but I'm fixing it now. – Brian Nickel Dec 14 '15 at 18:41
  • Well, I will forget this until next build :-) – unarist Dec 14 '15 at 18:48
  • @unarist That will be fixed in the next build, but the animation won't be great. UITableView does confusing things when it scrolls during an animation. – Brian Nickel Dec 14 '15 at 19:17
  • Thanks for being honest! But, this is not status-completed then. status-planned perhaps. – Shadow Wizard is Vaccinating Dec 15 '15 at 15:59
  • @ShadowWizard This bug seems to be fixed in beta release. – unarist Dec 15 '15 at 17:13
  • @unarist but these days, most people are using the official release, not beta. So I think it's more proper to mark completed only when the fix is pushed to the release channel, otherwise it will be quite confusing. Brian, what do you think? – Shadow Wizard is Vaccinating Dec 15 '15 at 17:39
  • 1
    @ShadowWizard my practice is to mark status complete when I've committed the change to git. None of the other statuses seem appropriate and this helps me process the queue. As for this feature, it's actually in the review queue with an expedited review request. – Brian Nickel Dec 15 '15 at 17:43
  • Thanks @Brian, guess after all it doesn't really matter - we can still close the new reports as duplicate of this, regardless of the status. – Shadow Wizard is Vaccinating Dec 15 '15 at 21:15
  • @odnU The expedited review was a great idea. We got a one day turn around. – Brian Nickel Dec 16 '15 at 4:13
  • @BrianNickel That's great! I haven't had great luck with them, but that could be because none of my apps are terribly critical, and, by extension, none of my fixes. – Undo Dec 16 '15 at 4:14
  • @BrianNickel The table jumps around a lot when I scroll down slowly and hold. Is it related somehow to this? – Caleb Dec 19 '15 at 21:34

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .