This repository has been archived by the owner on Dec 11, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 975
when syncing a new device, unable to click in field to give device an optional name #11653
Labels
bug
feature/sync
priority/P3
Major loss of function.
QA/checked-Linux
QA/checked-macOS
QA/checked-Win64
QA/test-plan-specified
regression
release-notes/include
Milestone
Comments
alexwykoff
added
the
needs-owner ♞
This issue is tagged for an upcoming release but has no owner.
label
Oct 24, 2017
I just ran into this in 0.19.131. I was able to work around the buggy behavior by using Tab to focus the name field. |
+1 from Twitter https://twitter.com/AlexanderGunz/status/953019949777375233
|
self-note: this is a bug in React with |
cezaraugusto
added a commit
that referenced
this issue
Jan 22, 2018
cezaraugusto
added a commit
that referenced
this issue
Jan 22, 2018
This was referenced Jun 11, 2018
This was referenced Jun 19, 2018
kjozwiak
removed
the
needs-owner ♞
This issue is tagged for an upcoming release but has no owner.
label
Jun 25, 2018
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
bug
feature/sync
priority/P3
Major loss of function.
QA/checked-Linux
QA/checked-macOS
QA/checked-Win64
QA/test-plan-specified
regression
release-notes/include
Description
When syncing a new device, you are unable to click in the optional field to give the device a name. You can tab to this field as a workaround. This happens whether you have entered the code words or left the code words blank.
Steps to Reproduce
Actual result:
You are not able to click in the optional field. If you watch closely, you can see a border around the field flash, but your cursor does not display in this field, it remains in the code words box.
Expected result:
You should be able to click on this field and enter your optional name if desired.
Reproduces how often: [What percentage of the time does it reproduce?] 100%
Brave Version
about:brave info:
Brave | 0.19.62
rev | fe3f350
Muon | 4.5.7
Reproducible on current live release:
yes, this happens on 0.19.53
Additional Information
This was working in 0.19.2 and stopped working in 0.19.3.
The text was updated successfully, but these errors were encountered: