Navigation

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Popular
    • Tags
    • Users
    • Groups
    1. Home
    2. Tags
    3. browser
    Log in to post
    • All categories
    • A

      Support on IE8 Browser
      Bug Reports • browser ie8 • • akumbhare

      3
      0
      Votes
      3
      Posts
      1613
      Views

      A

      @psychobunny End of life Imo. 🙂

    • vivek tailor

      whsta wrong on chrome
      Bug Reports • browser theme • • vivek tailor

      21
      0
      Votes
      21
      Posts
      5041
      Views

      D

      @Tanner I guess that works, but I should also learn how to pull specific commits.

    • aixnr

      Buggy view on mobile browser
      Bug Reports • browser theme • • Aizan Fahri

      11
      0
      Votes
      11
      Posts
      2669
      Views

      A

      @psychobunny Hmm, updated, cleared the cache etc, no difference. 😕

      On a sidenote, running git pull gives me an error about node_modules/cookie-parser not being on npm.

    • nik

      Mobile Bug
      Bug Reports • browser samsung • • nik

      4
      0
      Votes
      4
      Posts
      1416
      Views

      julian

      @zenkamal @a_5mith This sounds like it's due the new way we store post bookmarks.

      Basically:

      Before, we stored the pid (e.g. 2341) Now, we store the post index (e.g. 5) The bookmark only updates if the current post # is > than the bookmarked post # Unfortunately, 5 will never be greater than 2341, so the bookmark never goes away.

      The old bookmark is basically trying to load the 2341th post in the topic, which doesn't exist. You can clear the bookmark by clicking the "x" at the top right of the notification alert, then that topic should be fixed.