You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you save a term, the window, that fills most of the screen, doesn't disappear so you have to click X to get it out of the way each time.
yep.
When having to click buttons in the bottom of pages in the dictionary, you can't reach them because it won't let you scroll that far. (my problem was accepting/rejecting cookies on https://context.reverso.net/translation/). Temporary fix: drag the tab to make the dictionary fill the whole screen and you might see enough of the button to click it.
hm.
I also had this bug, where i had looked up a new word without doing anything else to it and every time i saved another new word the blue line, that's supposed to be underneath the one i just selected, would jump back up to the first new word. And if I tried the translate sentence function, it would translate the sentence of the first new word instead of the sentence where i actually just looked up a word. It would do this every time a new word was saved. Temporary fix: refresh page.
Need to confirm this one.
Another issue I noticed: clicking a new term near the bottom of the reading pane doesn't show the form.
The text was updated successfully, but these errors were encountered:
jzohrab
added
the
tweak
Adjustment to the code -- not a new feature, just minor mods/tweaks
label
May 6, 2024
The form activates but it is pushed below of what you can see. Words on the bottom line for me barely show the tab so I can pull the form higher up into view. I use a large-ish font and spacing though.
It would be helpful if the form never appeared lower than about 1/3 of the screen. Or whatever feels the best there I guess.
From Xolog in discord:
yep.
hm.
Need to confirm this one.
Another issue I noticed: clicking a new term near the bottom of the reading pane doesn't show the form.
The text was updated successfully, but these errors were encountered: