This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Action item from Santa Clara http://www.w3.org/2014/10/30-testing-minutes.html#action15
Hello, I read through https://w3c.github.io/webdriver/webdriver-spec.html and the transcript at http://www.w3.org/2014/10/30-testing-minutes.html#action15 I submitted a related issue to selenium webdriver (https://github.com/SeleniumHQ/selenium/issues/646) and I am not sure where the proper place to do this is In short my proposal was to add a parameter to allow selecting between fullpage and clipped. best regards Jean
*** This bug has been marked as a duplicate of bug 27646 ***
(In reply to Jean Helou from comment #1) > Hello, > > I read through https://w3c.github.io/webdriver/webdriver-spec.html and the > transcript at http://www.w3.org/2014/10/30-testing-minutes.html#action15 > > I submitted a related issue to selenium webdriver > (https://github.com/SeleniumHQ/selenium/issues/646) and I am not sure where > the proper place to do this is > > In short my proposal was to add a parameter to allow selecting between > fullpage and clipped. > > best regards > Jean A number of vendors don't want to be doing full page. If you raise a separate bug, sorry, and then it can be a specific point of discussion at TPAC.
I initially proposed this parameter as webdriver only did fullpage and I needed a clipped rendering. My use case is just fine now that clipped is the default :)