Closed Bug 1075006 Opened 10 years ago Closed 8 years ago

element screenshots in chrome discussion

Categories

(Remote Protocol :: Marionette, defect)

defect
Not set
normal

Tracking

(firefox53 fixed)

RESOLVED FIXED
mozilla53
Tracking Status
firefox53 --- fixed

People

(Reporter: mdas, Unassigned)

References

Details

(Keywords: pi-marionette-server)

When Bug 883294 lands, we'll have screenshot() working in chrome context, but it will only take a screenshot of the full viewport. Do we want the ability to take screenshots of particular elements, like we do in content?
Flags: needinfo?(dmose)
Flags: needinfo?(dburns)
It sounds useful, but wasn't actually aware of the ability in content, so I've never used it, and thus don't have any real-world experience with this. I could imagine it being handy for doing reftest-like image comparisons on (eg) toolbar buttons, but I don't have any real sense of whether this would be used. If it's cheap, turn it and document it as experimental, blog about it (maybe on hacks.mozilla.org), and on later do some searches to see if it gets used? Presumably, a fair amount depends on what you expect the maintenance burden to be. I've CCed a few folks who might also have opinions.
Flags: needinfo?(dmose)
wrt elements in content, in my experience this a rarely used feature. If you're using the screenshot in a test result the element alone is not enough information for debugging the test failure. You need the whole viewport screenshot to give context to the element. It's perhaps only good for programmatically scraping pages as images.
This might be useful for the Mozmill folks so let's leave this here until they request it.
Flags: needinfo?(dburns)
This will be available once my patch on bug 1243415 has been landed.
Depends on: 1243415
Fixed by bug 1243415.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla53
Product: Testing → Remote Protocol
You need to log in before you can comment on or make changes to this bug.