You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 11, 2019. It is now read-only.
Did you search for similar issues before submitting this one?
Yes.
Describe the issue you encountered:
The "use fullscreen" permission buttons seem out of order compared to other permissions. Use fullscreen has the Deny button first, but other permissions (e.g. autoplay video) have Yes first. For consistency, I think all "affirmative" buttons should be first (leftmost).
Platform (Win7, 8, 10? macOS? Linux distro?):
macOS 10.12.x
Brave Version (revision SHA):
0.17.13 ()
Steps to reproduce:
Go to any site with a fullscreen video (e.g. YouTube). Make sure use fullscreen is turned off by default for the site in settings.
Click the fullscreen button.
Actual result:
The Deny button is first.
Expected result:
The Allow button should be first.
Will the steps above reproduce in a fresh profile? If not what other info can be added?
Yes.
Is this an issue in the currently released version?
Yes, 0.17.13.
Can this issue be consistently reproduced?
Yes.
Extra QA steps:
1.
2.
3.
Screenshot if needed:
Any related issues:
None.
The text was updated successfully, but these errors were encountered:
Did you search for similar issues before submitting this one?
Yes.
Describe the issue you encountered:
The "use fullscreen" permission buttons seem out of order compared to other permissions. Use fullscreen has the
Deny
button first, but other permissions (e.g. autoplay video) haveYes
first. For consistency, I think all "affirmative" buttons should be first (leftmost).Platform (Win7, 8, 10? macOS? Linux distro?):
macOS 10.12.x
Brave Version (revision SHA):
0.17.13 ()
Steps to reproduce:
Actual result:
The
Deny
button is first.Expected result:
The
Allow
button should be first.Will the steps above reproduce in a fresh profile? If not what other info can be added?
Yes.
Is this an issue in the currently released version?
Yes, 0.17.13.
Can this issue be consistently reproduced?
Yes.
Extra QA steps:
1.
2.
3.
Screenshot if needed:

Any related issues:
None.
The text was updated successfully, but these errors were encountered: