How does one get XY coords of an element without using JS ?

[Justin Yeap]

Am trying to avoid using JS via evaluate runtime due to testing/experimental reasons. Would there happen to have a Devtools method for finding element's Viewport's Coords ? Thanks.

[Eric Seckler]

The DOM domain has a command to get the box model of a node (by nodeId or backendNodeId). X/Y coordinates are in the quads. Maybe that's of use?

https://chromedevtools.github.io/devtools-protocol/tot/DOM/#method-getBoxModel

On Wed, Sep 20, 2017, 07:36 Justin Yeap <guach...@gmail.com> wrote:

Am trying to avoid using JS via evaluate runtime due to testing/experimental reasons. Would there happen to have a Devtools method for finding element's Viewport's Coords ? Thanks.

--
You received this message because you are subscribed to the Google Groups "headless-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to headless-dev...@chromium.org.
To post to this group, send email to headle...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/headless-dev/b4f2c0f0-e943-4d9e-8fb0-13e688994535%40chromium.org.

[Isaac Dawson]

Yeah, that's what I use: https://github.com/wirepair/autogcd/blob/master/element.go#L620

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/headless-dev/CAHZJZiH%2ByBW7G7nvK0uBVGb3yRF38qCjExqkWDGA07Z9ay%2Busw%40mail.gmail.com.

[Justin Yeap]

I think it should work, just wondering would one be right to say backendnodes and nodesids have some overlap, just that backendnodes may not have been pushed to frontend ?

On Wed, Sep 20, 2017 at 2:48 PM, Eric Seckler <esec...@google.com> wrote:

The DOM domain has a command to get the box model of a node (by nodeId or backendNodeId). X/Y coordinates are in the quads. Maybe that's of use?

https://chromedevtools.github.io/devtools-protocol/tot/DOM/#method-getBoxModel

On Wed, Sep 20, 2017, 07:36 Justin Yeap <guach...@gmail.com> wrote:

Am trying to avoid using JS via evaluate runtime due to testing/experimental reasons. Would there happen to have a Devtools method for finding element's Viewport's Coords ? Thanks.

--
You received this message because you are subscribed to the Google Groups "headless-dev" group.

To unsubscribe from this group and stop receiving emails from it, send an email to headless-dev+unsubscribe@chromium.org.

[Eric Seckler]

They are different ID spaces, but yes - nodes corresponding to a known nodeId have always been pushed to the frontend, while you may know backendNodeIds of nodes that haven't been pushed.

On Wed, Sep 20, 2017, 07:51 Justin Yeap <guach...@gmail.com> wrote:

I think it should work, just wondering would one be right to say backendnodes and nodesids have some overlap, just that backendnodes may not have been pushed to frontend ?

On Wed, Sep 20, 2017 at 2:48 PM, Eric Seckler <esec...@google.com> wrote:

The DOM domain has a command to get the box model of a node (by nodeId or backendNodeId). X/Y coordinates are in the quads. Maybe that's of use?

https://chromedevtools.github.io/devtools-protocol/tot/DOM/#method-getBoxModel

On Wed, Sep 20, 2017, 07:36 Justin Yeap <guach...@gmail.com> wrote:

Am trying to avoid using JS via evaluate runtime due to testing/experimental reasons. Would there happen to have a Devtools method for finding element's Viewport's Coords ? Thanks.

--
You received this message because you are subscribed to the Google Groups "headless-dev" group.

To unsubscribe from this group and stop receiving emails from it, send an email to headless-dev...@chromium.org.