1

I recently tried to flag a question for moderator attention, and noticed that the guide text saying "Be specific and detailed!" is wrapped inside two not evaluated <i> HTML tags for the italic style (which is therefore not rendered).

Here's a screenshot from my phone:

screenshot

(from the StackOverflow site)


Additional details: I'm using an iPhone 4S running iOS 7.1.2 with the Stack Exchange app v1.4.0 v1.3.2.

6
  • On what site is that? The wording is different than mine. Maybe a site-specific issue. Oct 22, 2015 at 8:48
  • I'll add that to the question Oct 22, 2015 at 9:07
  • @Pat the bug is with the flag dialog, not flags or flagging process itself. (so if going that extra mile, at least make it as accurate mile as possible :)) Oct 22, 2015 at 18:48
  • Indeed, I was looking for that one but missed it somehow @Sha Oct 22, 2015 at 18:49
  • Can you double check your version in Menu -> About? v1.4.0 dropped support for iOS7 so I would expect you to have 1.3.2.1, which had this bug. Nov 4, 2015 at 1:44
  • @BrianNickel Thank you for making me notice this, I was looking on the AppStore page of the app, but not on my phone. Nov 4, 2015 at 1:53

2 Answers 2

1

Can't reproduce it on the latest beta. It seems to be fixed already. Recently there were some other bug reports related to the replacing of special characters on notifications and others, so probably it is solved already.

Screen shot

9
  • Thanks for the quick response! Oct 22, 2015 at 8:43
  • 1
    By the way, that is on version 1.4.0.239. Oct 22, 2015 at 8:44
  • See here for my original bug report. That one was fixed on 1.3.2.224. Not sure why your 1.4 fails. Oct 22, 2015 at 8:45
  • You may be right Oct 22, 2015 at 8:50
  • Note that I also see the same issue
    – Braiam
    Oct 22, 2015 at 13:49
  • What device and version @Braiam? Are you using the beta? Oct 22, 2015 at 14:06
  • Mmm, I remember I saw it somewhere... iPhone 4s, 1.4.0, no.
    – Braiam
    Oct 22, 2015 at 15:19
  • My device is mentioned in the last comment.
    – Braiam
    Oct 22, 2015 at 15:25
  • Ah, that is exactly the setup of OP. :) Oct 22, 2015 at 15:26
1

I'm actually running v1.3.2 instead of v1.4.0 (latest) because of my iOS version (7.1.2), so the bug has actually been fixed, but I didn't notice it on my device.


I'm a bit sad for the iOS 7 support drop, but that's a common upgrade side effect... got to deal with it.

You must log in to answer this question.

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