Skip to content
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

Blue circle hover effects on top of arrows #1051

Closed
paaljoachim opened this issue Jun 7, 2017 · 6 comments
Closed

Blue circle hover effects on top of arrows #1051

paaljoachim opened this issue Jun 7, 2017 · 6 comments

Comments

@paaljoachim
Copy link
Contributor

paaljoachim commented Jun 7, 2017

I am testing: https://testgutenberg.wpkonsulterna.se/wp-admin/admin.php?page=gutenberg

I believe this is already a part of an existing issue but I can not locate it right now.

Initially hovering over the left arrow beside the text block the up arrow is barely seen greyed out and the down arrow is obvious to notice.
I click to move the block one step down.
I click to move it up again.
This time there is a blue circle around the greyed out up button.

screen shot 2017-06-07 at 12 15 42

To me the blue circle feels out of place. The up arrow is already greyed out showing that one can not move it further up. Hmm hovering over the down arrow the blue circle is now also visible. Instead of having a blue circle what about just having the arrows turn blue?

blue-arrow

As one hovers over the arrows one can see a more subtile change.

@jasmussen
Copy link
Contributor

The blue circle is the focus highlight. I agree that it should show up only when you are using keyboard input, and not on button press. Though whether this is a bug or not, is part of a larger discussion that is ongoing in #904 (comment). For that reason, I'm closing this one. But thank you for reporting it as an issue.

@afercia
Copy link
Contributor

afercia commented Jun 7, 2017

This is also because the up arrow in this case is not really "disabled", it just looks disabled. Adding a disabled attribute when it's... disabled, would make it not focusable -> no focus style. If I remember correctly, this is already mentioned in another issue.

@jasmussen
Copy link
Contributor

Was the disabled aspect not fixed in #228 ? @iseulde any insights? Thank you.

@ellatrix
Copy link
Member

ellatrix commented Jun 8, 2017

@jasmussen I'm not sure what you're asking. The ticket you're linking was a prototype ticket.

@jasmussen
Copy link
Contributor

Argh, I'm having a case of the mondays. Nevermind me. I could just swear we had a ticket somewhere for actually adding a disabled attribute to the up/down arrows when they are at the top or bottom of the block list.

@aduth
Copy link
Member

aduth commented Jun 8, 2017

#984 was somewhat related, though to labeling the buttons, not applying the disabled attribute.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants