-
Notifications
You must be signed in to change notification settings - Fork 10.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Editor] Add a toggle button to show/hide all the highlights (bug 1867740) #17778
Conversation
749c47d
to
dc1d34c
Compare
dc1d34c
to
39aeea3
Compare
/botio-linux preview |
From: Bot.io (Linux m4)ReceivedCommand cmd_preview from @Snuffleupagus received. Current queue size: 0 Live output at: http://54.241.84.105:8877/24af36e57e29bf0/output.txt |
From: Bot.io (Linux m4)SuccessFull output at http://54.241.84.105:8877/24af36e57e29bf0/output.txt Total script time: 1.29 mins Published |
One question, based on testing the preview, however this may not be something that we want to implement: |
Good question and another came in my mind: what should we do when showAll is off and the user leaves the Highlighting mode ? |
I think in the future having a better affordance for the state of tools and annotations makes sense. This should be a part of the longer term UX debt improvements as there are many ways to solve this, and I would want to ensure scalability.
I think the flow now works; a user that toggles visibility off and disables the tool can enable the tool and either toggle visible, or begin highlighting and have visibility=true. I think this should be the same for when a user creates a highlight via selecting text/in-content. One caveat is that the toggle button may not be enough affordance to indicate state, which IMO relays back to the first question. |
/botio integrationtest |
From: Bot.io (Linux m4)ReceivedCommand cmd_integrationtest from @calixteman received. Current queue size: 0 Live output at: http://54.241.84.105:8877/3c7463cf2a4bebd/output.txt |
From: Bot.io (Windows)ReceivedCommand cmd_integrationtest from @calixteman received. Current queue size: 0 Live output at: http://54.193.163.58:8877/56fb383e162c65b/output.txt |
From: Bot.io (Linux m4)SuccessFull output at http://54.241.84.105:8877/3c7463cf2a4bebd/output.txt Total script time: 6.30 mins
|
From: Bot.io (Windows)SuccessFull output at http://54.193.163.58:8877/56fb383e162c65b/output.txt Total script time: 15.40 mins
|
No description provided.