Navigation

    Migaku Community

    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups

    Reader does not properly mark words as known

    Migaku Browser Extension
    bug reader
    4
    6
    95
    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.
    • I
      Istangel last edited by

      Oftentimes, the reader will not actually mark the word as known, even if the red line is removed. The number of known words will not go up, and if you advance the page and then go back, the word will have a red line under it again. I have not tested this functionality for other media, just the reader.

      SteviMigaku LucasMigaku 3 Replies Last reply Reply Quote 0
      • H
        Hieronymus @SteviMigaku last edited by

        @stevijs

        I am on the newest version and it doesn't work on Netflix for me, have to try it on the reader.

        1 Reply Last reply Reply Quote 0
        • I
          Istangel @SteviMigaku last edited by

          @stevijs I am indeed not on the newest version, I'm on 0.9.6.2.... that's my bad. I'll update and then see if the issue still arises, thank you!

          1 Reply Last reply Reply Quote 0
          • LucasMigaku
            LucasMigaku @Istangel last edited by

            @istangel We will talk about the issue here but I don't want you to share the file here that is.

            1 Reply Last reply Reply Quote 0
            • LucasMigaku
              LucasMigaku @Istangel last edited by

              @istangel Yes, can you please confirm that this is happening on the current reader version? If so can you dm me the book and the page where this issue is happening through Discord? I would like to fix it for you.

              1 Reply Last reply Reply Quote 0
              • SteviMigaku
                SteviMigaku @Istangel last edited by

                @istangel Are you on the newest version (0.9.9.2)? I remember that we had this bug on the older one, but it should be fix IIRC.

                I H 2 Replies Last reply Reply Quote 0
                • First post
                  Last post