0

Not too much else I can say, here's a screenshot, and a link to where this happens:

enter image description here

Here is the page where this happens.

This problem persisted past the beta, so it's time to fix it!

Improve this question
4
  • meta.stackexchange.com/a/71208/188613
    – User1000547
    Commented Jun 11, 2013 at 15:02
  • 1
    It always seems odd that a site that caters to developers and the tools developers need to use for their craft would explicitly shy away from pre-release browsers that developers need to use and test. I get that you might postpone fixing some things when a tool is really alpha/broken/new, but to have a policy of non-support seems a bit of a mixed message to me.
    – bmike
    Commented Jun 11, 2013 at 15:23
  • 1
    @bmike it's not a mixed message, we do not support beta browsers, period. If it's our bug, we're happy to fix it, but in the almost every case it's a bug in that browser that's fix on their end. People who use betas opt into bugs, and are often asked to report said bugs to the software creator...that's what should be done.
    – Nick Craver Mod
    Commented Jun 11, 2013 at 17:57
  • 1
    @NickCraver I should be clear - I'm just sharing my impression of the message. I very much appreciate the breadth and definitiveness of the site's support for a plethora of browsers. The mixed message seems to be "don't report anything beta" when it should be - awesome, thanks, we will queue this to try and reproduce things once the beta is GM. Rather than status declined - status-non-repro/status-repro and/or status-deferred would be ideal in my eyes.
    – bmike
    Commented Jun 11, 2013 at 18:52

1 Answer 1

Reset to default
9

We don't support beta browsers. This is a bug on their side, one that should be reported to Apple and hopefully fixed before they release iOS 7. We can't spend time on transient bugs that aren't caused on our end (often without any possible fix even if we did spend time on it).

Betas are buggy, that's why they're called betas.

Improve this answer
11
  • I disagree. Without looking into the bug you cannot definitively know that the bug is on their side, and not on yours.
    – Richard J. Ross III
    Commented Jun 11, 2013 at 17:56
  • 8
    @RichardJ.RossIII It works in every other browser including Safari on iOS 6.1.3 - I just verified that on 6 desktop browsers and 6 mobile devices. Which is more likely, your brand new not-yet-out-24-hours software is buggy, or all my tests are lying?
    – Nick Craver Mod
    Commented Jun 11, 2013 at 17:58
  • I'm not denying that it could be a browser bug. I'm just saying that blanket statements about it being a browser bug while saying you wont even look into is contradictory.
    – Richard J. Ross III
    Commented Jun 11, 2013 at 17:59
  • 5
    @RichardJ.RossIII I did look into it - did you read my above comment? Give the 99% probability it's on their side, it's not worth my time to attempt a crazy workaround (if that's even possible)...we have better things to do. Let me be clear: you opted into bugs with a beta browser, expect bugs.
    – Nick Craver Mod
    Commented Jun 11, 2013 at 18:01
  • I don't deny what you are saying, just how you are saying it in your answer.
    – Richard J. Ross III
    Commented Jun 11, 2013 at 18:03
  • 1
    This answer is outdated now that iOS 7 is officially out and this bug remains.
    – Richard J. Ross III
    Commented Sep 19, 2013 at 13:27
  • 1
    It is still most likely a bug with the browser and happening on other sites and not just Stack Exchange and something that Apple needs to fix and not Stack Exchange.
    – Joe W
    Commented Sep 19, 2013 at 14:10
  • @JoeW unlikely to be fixed though at this point, meaning SE should still look into it, in the name of consistency and usability.
    – Richard J. Ross III
    Commented Sep 19, 2013 at 14:29
  • 1
    @RichardJ.RossIII: isn't the problem that iOS 7 is ignoring consistency and usability?
    – user7116
    Commented Sep 19, 2013 at 14:40
  • @RichardJ.RossIII Unlikely to be fixed? What information is there that apple is unlikely to fix the bug? Chances are this bug will cause issues on more sites then Stack Exchange and will get fixed when they get to it in the priority list.
    – Joe W
    Commented Sep 19, 2013 at 14:53
  • 3
    @RichardJ.RossIII Not only is this a bug with iOS7 and not us, but you're also using the full site on mobile software, for which the full site is still not supported, as per this FAQ. Only the mobile view is supported for mobile browsers, so any bugs on the full view are extremely unlikely to be fixed.
    – animuson StaffMod
    Commented Sep 19, 2013 at 15:34

You must log in to answer this question.

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