Here's a scenario:
*Configurable Content Links - has state Lock and Unlock.

1. User click on Lock, and links is replaced to unlock. Keeps page open.
2. User opens same page in other browser - clicks unlock
3. User back to original page, and clicks on Unlock, but actually for system it's like he clicked on lock.

So, maybe links should be:

cclinks/cclink0/558-enable/593?destination=node
cclinks/cclink0/558-disable/593?destination=node

Comments

fago’s picture

fago
Primary language German
Location Vienna
commented

hm, I think it's not that common that user's are using two different browser at the same time.. But having only one link might also be useful in some situations. So I'm not sure if we should change it that way.

amitaibu’s picture

amitaibu
Primary language Hebrew
Location Israel
commented
Priority: Normal » Minor

Yes, I guess it is a really minor thing. I just wanted to point out the fact that a link might say enable, but will actually disable.

If you think it's 'too' minor, please close it.