mouse position shows in upper-left corner when taking a custom area screenshot
Bug #1627704 reported by
wolf
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Screenshot |
In Progress
|
Low
|
Jeremy Wootten | ||
Bug Description
Observed behavior: Screenshot app, select option to preserve mouse position, take custom area shot, in the resulting screenshot, submenus are not highlighted as expected and the mouse is moved to the upper-left corner, not where it was hovering during the screenshot.
For example, http://
Expected behavior: Both window and area select should capture the space exactly as set up when the screenshot is taken, but at the very least, the mouse position should not move to the upper-left corner when the toggle indicates that the mouse position would be included in the screenshot.
Related branches
lp:~jeremywootten/screenshot-tool/fix-1438250-include-child-windows
- Danielle Foré: Needs Fixing
- Sergey Kislyakov (community): Approve
-
Diff: 425 lines (+282/-53)1 file modifiedsrc/ScreenshotWindow.vala (+282/-53)
| affects: | elementaryos → screenshot-tool |
| summary: |
- screenshot app: mouse position moved to upper left corner, not where it - was in the screenshot + mouse position shows in upper-left corner, not where it was in the + screenshot |
| summary: |
- mouse position shows in upper-left corner, not where it was in the + mouse position shows in upper-left corner, not where it was during the screenshot |
Revision history for this message
| Fabio Zaramella (fabiozaramella) wrote | #1 |
| summary: |
- mouse position shows in upper-left corner, not where it was during the + mouse position shows in upper-left corner when taking a custom area screenshot |
| description: | updated |
| Changed in screenshot-tool: | |
| status: | New → Confirmed |
| importance: | Undecided → Low |
| Changed in screenshot-tool: | |
| assignee: | nobody → Jeremy Wootten (jeremywootten) |
| status: | Confirmed → In Progress |
To post a comment you must log in.
I can confirm that this bug is still present but only in custom area screenshots.