-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Enable sharing_hub::kDesktopScreenshots feature #28560
Labels
OS/Desktop
priority/P3
The next thing for us to work on. It'll ride the trains.
QA Pass-Linux
QA Pass-macOS
QA Pass-Win64
QA/Test-All-Platforms
QA/Yes
release-notes/include
Milestone
Comments
25 tasks
simonhong
added a commit
to brave/brave-core
that referenced
this issue
Feb 16, 2023
Labelling as Current test plan (per description) is:
|
Removing |
Verified with
Verified test plan from #28560 (comment).
|
Verified with
Verified test plan from #28560 (comment).
|
Verification
|
Brave | 1.50.112 Chromium: 112.0.5615.49 (Official Build) (64-bit) |
---|---|
Revision | bd2a7bcb881c11e8cfe3078709382934e3916914-refs/branch-heads/5615@{#936} |
Verified test plan from #28560 (comment).
- Confirmed that
Screenshot
is available in the Share menu in the url bar beneathCopy Clean Link
and beforeSend to your devices
(if sync enabled and a mobile device is part of sync chain, otherwise this option does not display). - Confirmed when selecting
Screenshot
a cursor is available and am able to select a portion of the browser content window to create a screenshot. - Confirmed that the screenshot tool does not allow selection outside of the content window.
- Confirmed able to get out of screenshot mode by selecting
Esc
.- Note, selecting/clicking outside of the window does not get out of screenshot mode as mentioned in the description/test plan. Confirmed this is the same behavior in Chrome with
112.0.5615.49 (Official Build) beta (x86_64)
. Confirmed this is ok per https://bravesoftware.slack.com/archives/C7VLGSR55/p1680272767922349?thread_ts=1680271939.020979&cid=C7VLGSR55.
- Note, selecting/clicking outside of the window does not get out of screenshot mode as mentioned in the description/test plan. Confirmed this is the same behavior in Chrome with
- Confirmed able to grab a screenshot by selecting content within the content window.
- Confirmed that a screenshot preview is generated and can be downloaded.
- Confirmed that the screenshot has
brave_screenshot
pre-appended to the file name and includes the domain name as part of the filename to the png file. - Confirmed the screenshot can be accessed via the download UI button and brave://downloads/
- Confirmed the flag is available in brave://flags and default is enabled.
- Confirmed able to set flag to disabled and
Screenshot
does not display in share menu
Example | Example | Example | Example | Example |
---|---|---|---|---|
![]() |
![]() |
![]() |
![]() |
![]() |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
OS/Desktop
priority/P3
The next thing for us to work on. It'll ride the trains.
QA Pass-Linux
QA Pass-macOS
QA Pass-Win64
QA/Test-All-Platforms
QA/Yes
release-notes/include
Description
Enable
sharing-desktop-screenshots
feature by defaultWith this feature, we can see

screenshot
menu from sharing hub.When download the screenshot file from below bubble,

proposed screenshot file name should have
brave_
prefix instead ofchrome_
prefix.Test Plan
Feature test
Screenshot
is available in the Share menu in the url bar beneathCopy Clean Link
and beforeSend your devices
.Screenshot
and confirm that a selection cursor is available and you can now select a portion of the browser content window to create a screenshot. Note that screenshot tool does not allow you to select outside of the content window. Also confirm that you can select outside of the window to get out of taking a screenshot.brave_screenshot
pre-appended to the file name and includes the domain name as part of the filename to the png file and can be accessed via the download UI button or brave://downloads/Flag test
The text was updated successfully, but these errors were encountered: