Genuinely Useful Mobile Bug Reports



  • Bug: Clicking "Quote Reply" on iOS difficult due to iOS highlight menu

    Just a sample, but sometimes the iOS menu practically completely covers the button. So maybe some browser/device detection and maybe put that button elsewhere?


  • @ChaosTheEternal said:

    Bug: Clicking "Quote Reply" on iOS difficult due to iOS highlight menu

    On a related note, on Android, sometimes the "quote reply" button gets placed behind the avatar on the z-axis, which makes it unclickable. I'll try to get a screenshot of it tomorrow. I can't be bothered to go grab my phone from downstairs right now.



  • I'd try to get that for you and see it myself, but Discourse flat out doesn't load on Gingerbread, not even the "no JS looks like crap" version, which bugs me on a certain level.


  • Banned

    Discourse only supports Android 4.1 or higher:



  • That isn't entirely right. The HTML in the noscript tag certainly works in older versions of Android (at least in 2.3.4), and since your "unsupported browser" banner is added via JavaScript, why not also do something like this which could put the "noscript" content out for a downlevel browser and make the experience practically the same, whether my browser isn't supported because it's old or because I don't have JavaScript enabled.



  • @codinghorror said:

    Discourse only supports Android 4.1 or higher:

    High version requirements are a barrier to reading.



  • Bug: On Chrome for iOS, site features break repeatedly

    Very often, the AJAX features just stop working after leaving one topic and entering another, either directly or via the topic list. The posts won't load in and the position indicator is missing one or both numbers and has no green to indicate relative position, and on the topic list' the title bar changes to "Loading topic..." by itself (this is also the only time the title bar changes to that, and not when it is working normally). Happens very frequently.



  • Bug: The "quote reply" button gets placed behind the avatar, which makes it unclickable.
    Expected: Button should pop up in front of everything.
    Actual:
    System: Chrome 34 on Android 4.3



  • Bug: CSS renders Polls improperly on Firefox Mobile
    Expected: rendering of Polls to work properly.
    Actual:



  • Mini bug.

    When hovering on the number of likes:

    When hovering on the heart icon:

    I'm using the mobile view if that is significant.



  • You can't see all categories when creating a new topic in the mobile view. The screenshot below demonstrates the problem in Chrome:

    I've scrolled the page and category list as far as I can and the Coding Help category is hidden below the fold. The same happens on my phone (WP8, IE10).

    I accidentally discovered that you can type to filter the list, but this isn't too helpful if you don't know which categories are hidden.

    Also, to support the type-to-filter function, my phone pops up a keyboard when I open the "Select a category..." drop down, moving screen content around and reducing further the amount that can be displayed on the screen. Very annoying. Perhaps the text input could be activated by clicking a separate filter icon rather than when the list is expanded.


  • Banned

    We don't test on Firefox for Android at all (and technically it's unsupported). We only test on the default browsers for each mobile platform. I strongly suggest moving to Chrome for Android.

    If it is some easy markup fix, though, feel free to propose it -- I find mobile "alternative" browsers are often very very buggy, e.g. Chrome on iOS is awful and has unique rendering errors we don't see on any other platform and certainly no other version of Chrome.



  • @codinghorror said:

    I strongly suggest moving to Chrome for Android.
    Chrome for Android doesn't have plugins, so Ghostery isn't available for it. That's a deal-breaker.


  • Discourse touched me in a no-no place

    Bug: On the mobile version (Chrome 35 on Android), while the red pen indicating edits is visible, clicking it does nothing. Works as expected when desktop version is requested.



  • Can confirm as a problem with the mobile view, rather than the browser - successful reproduction on Ubuntu Chrome 35, Mobile View.



  • Bug: Presses while topics are loading interact with topics that haven't yet actually loaded.

    Twice now recently when I have tapped twice to read a topic (due to no indicator that it is loading), the second tap is processed after the topic loads, over a second later, and unintended effects happen, like "liking" this post.



  • Bug: Edit reason box shows up behind text entry when opened when editing posts that aren't replies.


    Filled under: [Whoever thought to tie the screenshot key combo to a volume key didn't think the implementation all the way through] (#tag), [image editing options on Android are terrible](#tag), [so is my grasp on grammar at times](#tag)

  • Banned

    Yet again, I just want to emphasize that we only support Chrome as the default Android browser at this time. And on iOS, only the default Safari is supported.

    Please be sure to mention which mobile browser (of the dozen available) for Android you are using in your bug report.



  • It is Chrome for Android.

    You should assume I'm reporting these for only your supported browser list.


  • Banned

    No repro on Nexus 5 and Chrome latest version, though, which is why I asked. See screenshot:



  • There is no edit reason box in your screenshot. You know, the text field that appears when you click "add edit reason" on one of your posts? And try being in landscape if you see the "reply to" blurb.


    Filed under: I edit my posts more often than I make new ones


  • Banned

    Right but I am editing my post on the Nexus 5 and I don't see the edit reason box at all. Are you saying to repro this you have to start editing in landscape, then rotate?



  • On posts that aren't replies to specific posts, it looks like this:

    Note the "add edit reason" link.

    On posts that are replies, you can't see the link unless you go into landscape:

    But in either orientation, in either case if I click that link, I get what I screenshot in my original report, on a Droid Maxx.


  • Discourse touched me in a no-no place

    Bug: Quote reply only works intermittently on Chrome for Android. It fails most of the time, but occasionally works.

    **Repro: **Highlight text you want to quote, tap "quote reply", nothing happens.

    **System info: **
    Application Chrome 35.0.1916.138 1916138
    OS Android 4.4.2; Nexus 5 Build/KOT49H
    Blink 537.36 (@174108)
    JavaScript V8 3.25.28.18
    User Agent Mozilla/5.0 (Linux; Android 4.4.2; Nexus 5 Build/KOT49H) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/35.0.1916.138 Mobile Safari/537.36


  • Banned

    @neil fixed a bunch of these yesterday, and can elaborate on the details.



  • Two fixes so far:

    @moderator said:

    The "quote reply" button gets placed behind the avatar, which makes it unclickable.

    @ChaosTheEternal said:

    Edit reason box shows up behind text entry when opened when editing posts that aren't replies.

    This one is a problem on all 3 phones I have for testing, (iOS 7, Android, and Windows mobile), so I'll tackle it next:

    @ChaosTheEternal said:

    Clicking "Quote Reply" on iOS difficult due to iOS highlight menu

    That "quote reply" button needs to go somewhere else (underneath instead of on top) on mobile without the need for device detection.


  • Banned

    As reported elsewhere, we made default mobile entry area smaller to accommodate Android. Screenshot on my test Nexus 5



  • @codinghorror said:

    As reported elsewhere, we made default mobile entry area smaller to accommodate Android. Screenshot on my test Nexus 5

    <img src="/uploads/default/2262/50b0d6cc49444024.png" width="281" height="500">

    How can you call this a proper test when your battery is that low? And look, you missed a phone call? Smacks of lazy testing to me.


  • Banned


  • Banned


Log in to reply
 

Looks like your connection to What the Daily WTF? was lost, please wait while we try to reconnect.