- Blind mode tutorial
lichess.org
Donate

It keeps showing variation arrow even though i turned it off

@lonelypeanut said in #19:

Yes there was an update but it's impact may be browser dependent.

Another thing completely:
Could you edit your posts rather than add another one every time please? Nobody's going to read the threat like this, also if it gets to long it gets automatically pushed down at some point so nobody will see it after that.

Sure thanks, i’ll start editing ;) i do that so it is visible to new people or mods

@lonelypeanut said in #19: > Yes there was an update but it's impact may be browser dependent. > > Another thing completely: > Could you edit your posts rather than add another one every time please? Nobody's going to read the threat like this, also if it gets to long it gets automatically pushed down at some point so nobody will see it after that. Sure thanks, i’ll start editing ;) i do that so it is visible to new people or mods

@schlawg said in #20:

there were non-trivial changes in this area (and more are coming), so we'll have some minor issues to work out.

to distill the previous 19 messages, variation arrows cannot be turned off on touch devices and do not appear as a toggle in the action menu?

I am confused, i don’t have the option to turn off variation arrows on a Tablet/iPad but i do on a computer, however the aren’t synced so the two do affect each other

@schlawg said in #20: > there were non-trivial changes in this area (and more are coming), so we'll have some minor issues to work out. > > to distill the previous 19 messages, variation arrows cannot be turned off on touch devices and do not appear as a toggle in the action menu? I am confused, i don’t have the option to turn off variation arrows on a Tablet/iPad but i do on a computer, however the aren’t synced so the two do affect each other

@schlawg Among other issues detailed in other threads, yes.

As a frequent user for many years, I am terrified by the casualness with which you say "and more are coming". Just a suggestion (we are in the feedback section, after all): Lichess could ask users before making changes which significantly impact regular usage of the site's most popular features. Or Lichess could at least tell users in advance, give us a bit of warning, let us know how to voice our concerns or report bugs in a more structured manner than what is happening now: lots of people complaining about the same issues in multiple threads that pop up within hours of each other.

@schlawg Among other issues detailed in other threads, yes. As a frequent user for many years, I am terrified by the casualness with which you say "and more are coming". Just a suggestion (we are in the feedback section, after all): Lichess could ask users _before_ making changes which significantly impact regular usage of the site's most popular features. Or Lichess could at least tell users in advance, give us a bit of warning, let us know how to voice our concerns or report bugs in a more structured manner than what is happening now: lots of people complaining about the same issues in multiple threads that pop up within hours of each other.

@biscuitfiend

I am terrified by the casualness with which you say "and more are coming"

we are always trying to improve the product. unfortunately, we don't have the resources to organize a PR campaign every time we change a button. if you don't like it, there are other chess websites, OTB with friends and family, and many other ways to spend your free time.

@biscuitfiend > I am terrified by the casualness with which you say "and more are coming" we are always trying to improve the product. unfortunately, we don't have the resources to organize a PR campaign every time we change a button. if you don't like it, there are other chess websites, OTB with friends and family, and many other ways to spend your free time.

@Planet_CHESS465 said in #24:

So can the problem be fixed?

yes!

@Planet_CHESS465 said in #24: > So can the problem be fixed? yes!

@schlawg said in #26:

yes!

If you don’t mind, how and when? I sometimes stop before I see the blunder annotation to figure out a better move myself, and with the arrows in the way it makes seeing the board harder.

@schlawg said in #26: > yes! If you don’t mind, how and when? I sometimes stop before I see the blunder annotation to figure out a better move myself, and with the arrows in the way it makes seeing the board harder.

I understand. We'll probably get the issues patched up by this time tomorrow. But I haven't had time to look at them yet, I'm planning on it this evening.

I understand. We'll probably get the issues patched up by this time tomorrow. But I haven't had time to look at them yet, I'm planning on it this evening.

@schlawg said in #28:

I understand. We'll probably get the issues patched up by this time tomorrow. But I haven't had time to look at them yet, I'm planning on it this evening.
@schlawg said in #28:
I understand. We'll probably get the issues patched up by this time tomorrow. But I haven't had time to look at them yet, I'm planning on it this evening.

Thank you.

@schlawg said in #28: > I understand. We'll probably get the issues patched up by this time tomorrow. But I haven't had time to look at them yet, I'm planning on it this evening. @schlawg said in #28: > I understand. We'll probably get the issues patched up by this time tomorrow. But I haven't had time to look at them yet, I'm planning on it this evening. Thank you.

@schlawg said in #25:

unfortunately, we don't have the resources to organize a PR campaign every time we change a button.

I understand. In that case, you can continue to spend what limited resources you have making changes, only to spend more resources reverting or patching them later.

In case it's not clear, I was suggesting that it might save resources in the long term if some are spent now - or sooner rather than later - to implement a proper testing and review system. But it's not my site, and they aren't my resources to spend.

@schlawg said in #25: > unfortunately, we don't have the resources to organize a PR campaign every time we change a button. I understand. In that case, you can continue to spend what limited resources you have making changes, only to spend more resources reverting or patching them later. In case it's not clear, I was suggesting that it might save resources in the long term if some are spent now - or sooner rather than later - to implement a proper testing and review system. But it's not my site, and they aren't my resources to spend.

This topic has been archived and can no longer be replied to.