This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 25694 - 16.2 section isn't needed as it's possible to take screenshot of "html"/"body"
Summary: 16.2 section isn't needed as it's possible to take screenshot of "html"/"body"
Status: RESOLVED WONTFIX
Alias: None
Product: Browser Test/Tools WG
Classification: Unclassified
Component: WebDriver (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Browser Testing and Tools WG
QA Contact: Browser Testing and Tools WG
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 20860
  Show dependency treegraph
 
Reported: 2014-05-13 21:16 UTC by Andrey Botalov
Modified: 2014-07-07 16:26 UTC (History)
2 users (show)

See Also:


Attachments

Description Andrey Botalov 2014-05-13 21:16:46 UTC
16.1 section provides a way to take screenshot of any WebElement, not just current window. Thus a user can take screenshot of "body", "html" or some other element with fairly large client rectangle (much more than innerWidth/innerHeight). So the same principles that should be applied for taking screenshot of window should be also applied to taking screenshot of WebElement. So the relevant info about infinite scrolling, nested frames, etc. should be moved to 16.3 section and 16.2 section can be removed.

Also spec tells:
> Implementations of the remote end should capture the entire Document, even if this would require a user to scroll the browser window

However, it's not clear from 16 section how entire document/WebElement can be captured if parallax scrolling is used by the website. I mean site like e.g.:
http://islreview.com/

Also I think that when takeScreenshot is applied to element not currently in the view, then remote end MUST scroll element into view to get a better screenshot (it would be helpful if parallax scrolling is used by the website so it would be good to do for all WebElements).
Comment 1 David Burns :automatedtester 2014-07-07 16:26:39 UTC
This was discussed in the F2F

We are going to keep them separate since we can have separate capabilities since currently there is only 1 implementation of takesElementScreenshot.

Since taking a screenshot of the document is the default we will have to keep it.