J-Novel Club
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Users

    You are on the cloned forums!

    Up/Down Arrow keys not working

    Support
    3
    6
    195
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • D
      drstampy Member last edited by

      Yo, a little while ago the up/down arrow keys stopped working on the web browser reader. I use google chrome on a laptop, and other things involving arrow keys still work. The problem has persisted for more than a week.

      Does anyone know how to fix this?

      Other ways to scroll still work, like left/right, wasd, etc. Also the up/down arrow keys do work if I try in firefox.

      chocolatkey 1 Reply Last reply Reply Quote 0
      • chocolatkey
        chocolatkey Staff @drstampy last edited by

        @drstampy Could you answer the following:

        • Is this in a manga or novel?
        • Are you in horizontal or vertical reading mode?
        • Aer you in single or spread mode if in horizontal?
        D 1 Reply Last reply Reply Quote 0
        • LegitPancake
          LegitPancake Premium Member last edited by LegitPancake

          Arrow keys worked just fine for me on chrome on my PC. I tested on both novels and manga (vertical mode) , as well as the "Open in new tab" feature.

          1 Reply Last reply Reply Quote 0
          • D
            drstampy Member @chocolatkey last edited by

            @chocolatkey

            Novel, vertical mode.

            chocolatkey 1 Reply Last reply Reply Quote 0
            • chocolatkey
              chocolatkey Staff @drstampy last edited by

              @drstampy Hmm that should work fine. Could you provide me with a screenshot of the page in the state where the arrow keys don't work?

              D 1 Reply Last reply Reply Quote 0
              • D
                drstampy Member @chocolatkey last edited by

                @chocolatkey nvm I fixed it. Some accessibility setting in chrome was making it happen. Woops :U

                1 Reply Last reply Reply Quote 0
                • 1 / 1
                • First post
                  Last post