Since today the behaviour of the lingq reader in the browser has changed.
In the past, when I marked a blue or yellow word as known the word stayed selected, but since today it automatically jumps to the next blue or yellow word. This is highly annoying, as
- the word may be in a completely different part of the sentence, a different sentence or even a new paragraph.
- I automatically get to see suggestions for translations of said word, before I even had a chance to try to remember the meaning of the word or guess it from context
I have not found a way to disable this behaviour. Is this default behaviour or a bug? And is there a way to get rid of this? I am using Firefox by default, but Google Chrome shows the same behaviour.
Thanks in advance
Now it seems to be working as it did before. Odd.
EDIT: Nope, back to the other behaviour. I have no idea what is going on, but am I the only one experiencing this?!
Thanks, I asked our team to look into that.
I remember this was a feature few months ago. Then they got rid of it. It is actually handy especially at the beginning where there are lot of blue words one knows. One does not have to manually go for the next word.
No its horrible because I can’t even read my sentence. It springs from sentence to sentence without me being able to even read the sentence.
I noticed this behavior a little bit recently.
I thought it was quite handy, as jansiebert mentioned, but I haven’t been able to use it enough to tell how useful it is past an initial study session where one preview and marks all the blue words when they first go through a lesson — if you’re like me and do that.
If you are trying to add multiple meanings or look at more stuff on a blue word you clicked and added a meaning, then I definitely see were moving to the next blue word after creating the LingQ would be horrible as others have mentioned.
As convenient as the above use case (first scenario mentioned) would be, it’s not worth the headache it would cause for scenarios like the one I mentioned above. It would help more people to have it not do that, I think.
After using it like this a while and gotting used to not looking at the suggestions it actually speeds up things. The best thing would be if it could be adjusted by the users to their preferences imho. And considering the response of zoran I assume it didn’t happen intentionally.
It only works when you use the side bar, however. The “widget” often obscures the sentence you’re currently reading.
When will it be fixed? hello, I can’t use lingq like this…
would be nice to have an opt-out possibility. Doesn’t make lingq unusable, as you always have the option to just close the pop-up, but not that useful for me at the moment.
While it’s easy to close the pop up, the problem I have is that if I’m listening to a podcast or video and I forget a word, I quickly click it to be reminded, but then it sets off a chain reaction popping to other words on the page, obscuring the text and making the audio impossible to hear.
Hey LingQ Support Team,
Would it be possible to change this to a shortcut option to toggle on/off in a given lesson/study session?
Like, I don’t know command + b (or something else) toggles off/on automatically going to the next blue word (a.k.a. the “chain reaction feature” for lack of a better reference to that behavior).
Seems a bit odd to have this as a feature (though I like this, as I stated here) when y’all have the shortcut B that goes to the next blue word in a lesson.
Unless this is a bug or something else.
*Note: Edited to fix typo.
We are working on this and we will push a fix soon. Thanks for your patience.
Could you please make it optional? I actually liked it that it finally jumped to the next word again after making a word known or ignoring it. Maybe as long as it’s on the same page? Thanks!
Yes same, can you make it an option
We’ll see what we can do.
Thanks! BTW, when I open a lesson again, it often happens that the next page is opened instead of the page I was on. Not always, but often enough. Could you look into that, please? Thanks!
We will check that, thanks for reporting.