2019-01-15 04:34:50 +00:00
/ * *
* Copyright 2019 Google Inc . All rights reserved .
*
* Licensed under the Apache License , Version 2.0 ( the "License" ) ;
* you may not use this file except in compliance with the License .
* You may obtain a copy of the License at
*
* http : //www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing , software
* distributed under the License is distributed on an "AS IS" BASIS ,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND , either express or implied .
* See the License for the specific language governing permissions and
* limitations under the License .
* /
2022-06-22 13:25:44 +00:00
import { Protocol } from 'devtools-protocol' ;
import { assert } from './assert.js' ;
import { CDPSession } from './Connection.js' ;
feat!: type inference for evaluation types (#8547)
This PR greatly improves the types within Puppeteer:
- **Almost everything** is auto-deduced.
- Parameters don't need to be specified in the function. They are deduced from the spread.
- Return types don't need to be specified. They are deduced from the function. (More on this below)
- Selections based on tag names correctly deduce element type, similar to TypeScript's mechanism for `getElementByTagName`.
- [**BREAKING CHANGE**] We've removed the ability to declare return types in type arguments for the following reasons:
1. Setting them will indubitably break auto-deduction.
2. You can just use `as ...` in TypeScript to coerce the correct type (given it makes sense).
- [**BREAKING CHANGE**] `waitFor` is officially gone.
To migrate to these changes, there are only four things you may need to change:
- If you set a return type using the `ReturnType` type parameter, remove it and use `as ...` and `HandleFor` (if necessary).
⛔ `evaluate<ReturnType>(a: number, b: number) => {...}, a, b)`
✅ `(await evaluate(a, b) => {...}, a, b)) as ReturnType`
⛔ `evaluateHandle<ReturnType>(a: number, b: number) => {...}, a, b)`
✅ `(await evaluateHandle(a, b) => {...}, a, b)) as HandleFor<ReturnType>`
- If you set any type parameters in the *parameters* of an evaluation function, remove them.
⛔ `evaluate(a: number, b: number) => {...}, a, b)`
✅ `evaluate(a, b) => {...}, a, b)`
- If you set any type parameters in the method's declaration, remove them.
⛔ `evaluate<(a: number, b: number) => void>((a, b) => {...}, a, b)`
✅ `evaluate(a, b) => {...}, a, b)`
2022-06-23 09:29:46 +00:00
import { EvaluateFunc , EvaluateParams , HandleFor , HandleOr } from './types.js' ;
2022-06-22 13:25:44 +00:00
import { ExecutionContext } from './ExecutionContext.js' ;
import { Frame , FrameManager } from './FrameManager.js' ;
import { MouseButton } from './Input.js' ;
import { Page , ScreenshotOptions } from './Page.js' ;
import { _getQueryHandlerAndSelector } from './QueryHandler.js' ;
import { KeyInput } from './USKeyboardLayout.js' ;
2022-06-14 11:16:21 +00:00
import {
debugError ,
isString ,
releaseObject ,
valueFromRemoteObject ,
} from './util.js' ;
feat!: type inference for evaluation types (#8547)
This PR greatly improves the types within Puppeteer:
- **Almost everything** is auto-deduced.
- Parameters don't need to be specified in the function. They are deduced from the spread.
- Return types don't need to be specified. They are deduced from the function. (More on this below)
- Selections based on tag names correctly deduce element type, similar to TypeScript's mechanism for `getElementByTagName`.
- [**BREAKING CHANGE**] We've removed the ability to declare return types in type arguments for the following reasons:
1. Setting them will indubitably break auto-deduction.
2. You can just use `as ...` in TypeScript to coerce the correct type (given it makes sense).
- [**BREAKING CHANGE**] `waitFor` is officially gone.
To migrate to these changes, there are only four things you may need to change:
- If you set a return type using the `ReturnType` type parameter, remove it and use `as ...` and `HandleFor` (if necessary).
⛔ `evaluate<ReturnType>(a: number, b: number) => {...}, a, b)`
✅ `(await evaluate(a, b) => {...}, a, b)) as ReturnType`
⛔ `evaluateHandle<ReturnType>(a: number, b: number) => {...}, a, b)`
✅ `(await evaluateHandle(a, b) => {...}, a, b)) as HandleFor<ReturnType>`
- If you set any type parameters in the *parameters* of an evaluation function, remove them.
⛔ `evaluate(a: number, b: number) => {...}, a, b)`
✅ `evaluate(a, b) => {...}, a, b)`
- If you set any type parameters in the method's declaration, remove them.
⛔ `evaluate<(a: number, b: number) => void>((a, b) => {...}, a, b)`
✅ `evaluate(a, b) => {...}, a, b)`
2022-06-23 09:29:46 +00:00
import { WaitForSelectorOptions } from './DOMWorld.js' ;
2022-04-27 21:00:07 +00:00
2021-04-06 08:58:01 +00:00
/ * *
* @public
* /
2020-06-22 15:21:57 +00:00
export interface BoxModel {
2022-05-31 14:34:16 +00:00
content : Point [ ] ;
padding : Point [ ] ;
border : Point [ ] ;
margin : Point [ ] ;
2020-04-21 11:11:06 +00:00
width : number ;
height : number ;
}
2019-01-15 04:34:50 +00:00
2020-06-22 15:21:57 +00:00
/ * *
* @public
* /
2022-05-31 14:34:16 +00:00
export interface BoundingBox extends Point {
2020-06-22 15:21:57 +00:00
/ * *
* the width of the element in pixels .
* /
width : number ;
/ * *
* the height of the element in pixels .
* /
height : number ;
}
/ * *
* @internal
* /
2022-06-13 09:16:25 +00:00
export function _createJSHandle (
2020-05-07 10:54:55 +00:00
context : ExecutionContext ,
remoteObject : Protocol.Runtime.RemoteObject
feat!: type inference for evaluation types (#8547)
This PR greatly improves the types within Puppeteer:
- **Almost everything** is auto-deduced.
- Parameters don't need to be specified in the function. They are deduced from the spread.
- Return types don't need to be specified. They are deduced from the function. (More on this below)
- Selections based on tag names correctly deduce element type, similar to TypeScript's mechanism for `getElementByTagName`.
- [**BREAKING CHANGE**] We've removed the ability to declare return types in type arguments for the following reasons:
1. Setting them will indubitably break auto-deduction.
2. You can just use `as ...` in TypeScript to coerce the correct type (given it makes sense).
- [**BREAKING CHANGE**] `waitFor` is officially gone.
To migrate to these changes, there are only four things you may need to change:
- If you set a return type using the `ReturnType` type parameter, remove it and use `as ...` and `HandleFor` (if necessary).
⛔ `evaluate<ReturnType>(a: number, b: number) => {...}, a, b)`
✅ `(await evaluate(a, b) => {...}, a, b)) as ReturnType`
⛔ `evaluateHandle<ReturnType>(a: number, b: number) => {...}, a, b)`
✅ `(await evaluateHandle(a, b) => {...}, a, b)) as HandleFor<ReturnType>`
- If you set any type parameters in the *parameters* of an evaluation function, remove them.
⛔ `evaluate(a: number, b: number) => {...}, a, b)`
✅ `evaluate(a, b) => {...}, a, b)`
- If you set any type parameters in the method's declaration, remove them.
⛔ `evaluate<(a: number, b: number) => void>((a, b) => {...}, a, b)`
✅ `evaluate(a, b) => {...}, a, b)`
2022-06-23 09:29:46 +00:00
) : JSHandle | ElementHandle {
2019-01-15 04:34:50 +00:00
const frame = context . frame ( ) ;
if ( remoteObject . subtype === 'node' && frame ) {
const frameManager = frame . _frameManager ;
2020-05-07 10:54:55 +00:00
return new ElementHandle (
context ,
context . _client ,
remoteObject ,
2022-01-17 06:32:52 +00:00
frame ,
2020-05-07 10:54:55 +00:00
frameManager . page ( ) ,
frameManager
) ;
2019-01-15 04:34:50 +00:00
}
return new JSHandle ( context , context . _client , remoteObject ) ;
}
2022-06-15 10:42:21 +00:00
const applyOffsetsToQuad = (
quad : Point [ ] ,
offsetX : number ,
offsetY : number
) = > {
2022-06-22 13:25:44 +00:00
return quad . map ( part = > {
return { x : part.x + offsetX , y : part.y + offsetY } ;
2022-06-15 10:42:21 +00:00
} ) ;
} ;
2022-01-17 13:19:43 +00:00
2020-06-22 15:21:57 +00:00
/ * *
2020-06-25 14:49:35 +00:00
* Represents an in - page JavaScript object . JSHandles can be created with the
* { @link Page . evaluateHandle | page . evaluateHandle } method .
*
* @example
* ` ` ` js
* const windowHandle = await page . evaluateHandle ( ( ) = > window ) ;
* ` ` `
*
* JSHandle prevents the referenced JavaScript object from being garbage - collected
* unless the handle is { @link JSHandle . dispose | disposed } . JSHandles are auto -
* disposed when their origin frame gets navigated or the parent context gets destroyed .
*
* JSHandle instances can be used as arguments for { @link Page . $eval } ,
* { @link Page . evaluate } , and { @link Page . evaluateHandle } .
*
2020-06-22 15:21:57 +00:00
* @public
* /
feat!: type inference for evaluation types (#8547)
This PR greatly improves the types within Puppeteer:
- **Almost everything** is auto-deduced.
- Parameters don't need to be specified in the function. They are deduced from the spread.
- Return types don't need to be specified. They are deduced from the function. (More on this below)
- Selections based on tag names correctly deduce element type, similar to TypeScript's mechanism for `getElementByTagName`.
- [**BREAKING CHANGE**] We've removed the ability to declare return types in type arguments for the following reasons:
1. Setting them will indubitably break auto-deduction.
2. You can just use `as ...` in TypeScript to coerce the correct type (given it makes sense).
- [**BREAKING CHANGE**] `waitFor` is officially gone.
To migrate to these changes, there are only four things you may need to change:
- If you set a return type using the `ReturnType` type parameter, remove it and use `as ...` and `HandleFor` (if necessary).
⛔ `evaluate<ReturnType>(a: number, b: number) => {...}, a, b)`
✅ `(await evaluate(a, b) => {...}, a, b)) as ReturnType`
⛔ `evaluateHandle<ReturnType>(a: number, b: number) => {...}, a, b)`
✅ `(await evaluateHandle(a, b) => {...}, a, b)) as HandleFor<ReturnType>`
- If you set any type parameters in the *parameters* of an evaluation function, remove them.
⛔ `evaluate(a: number, b: number) => {...}, a, b)`
✅ `evaluate(a, b) => {...}, a, b)`
- If you set any type parameters in the method's declaration, remove them.
⛔ `evaluate<(a: number, b: number) => void>((a, b) => {...}, a, b)`
✅ `evaluate(a, b) => {...}, a, b)`
2022-06-23 09:29:46 +00:00
export class JSHandle < T = unknown > {
2022-06-13 09:16:25 +00:00
# client : CDPSession ;
# disposed = false ;
# context : ExecutionContext ;
# remoteObject : Protocol.Runtime.RemoteObject ;
2020-06-30 14:56:37 +00:00
/ * *
* @internal
* /
2022-06-13 09:16:25 +00:00
get _client ( ) : CDPSession {
return this . # client ;
}
2020-06-30 14:56:37 +00:00
/ * *
* @internal
* /
2022-06-13 09:16:25 +00:00
get _disposed ( ) : boolean {
return this . # disposed ;
}
2020-06-30 14:56:37 +00:00
/ * *
* @internal
* /
2022-06-13 09:16:25 +00:00
get _remoteObject ( ) : Protocol . Runtime . RemoteObject {
return this . # remoteObject ;
}
2020-06-30 14:56:37 +00:00
/ * *
* @internal
* /
2022-06-13 09:16:25 +00:00
get _context ( ) : ExecutionContext {
return this . # context ;
}
2020-04-21 11:11:06 +00:00
2020-06-30 14:56:37 +00:00
/ * *
* @internal
* /
2020-05-07 10:54:55 +00:00
constructor (
context : ExecutionContext ,
client : CDPSession ,
remoteObject : Protocol.Runtime.RemoteObject
) {
2022-06-13 09:16:25 +00:00
this . # context = context ;
this . # client = client ;
this . # remoteObject = remoteObject ;
2019-01-15 04:34:50 +00:00
}
2020-06-25 14:49:35 +00:00
/ * * R e t u r n s t h e e x e c u t i o n c o n t e x t t h e h a n d l e b e l o n g s t o .
* /
chore: migrate src/ExecutionContext (#5705)
* chore: migrate src/ExecutionContext to TypeScript
I spent a while trying to decide on the best course of action for
typing the `evaluate` function.
Ideally I wanted to use generics so that as a user you could type
something like:
```
handle.evaluate<HTMLElement, number, boolean>((node, x) => true, 5)
```
And have TypeScript know the arguments of `node` and `x` based on those
generics. But I hit two problems with that:
* you have to have n overloads of `evaluate` to cope for as many number
of arguments as you can be bothered too (e.g. we'd need an overload for
1 arg, 2 args, 3 args, etc)
* I decided it's actually confusing because you don't know as a user
what those generics actually map to.
So in the end I went with one generic which is the return type of the
function:
```
handle.evaluate<boolean>((node, x) => true, 5)
```
And `node` and `x` get typed as `any` which means you can tell TS
yourself:
```
handle.evaluate<boolean>((node: HTMLElement, x: number) => true, 5)
```
I'd like to find a way to force that the arguments after the function do
match the arguments you've given (in the above example, TS would moan if
I swapped that `5` for `"foo"`), but I tried a few things and to be
honest the complexity of the types wasn't worth it, I don't think.
I'm very open to tweaking these but I'd rather ship this and tweak going
forwards rather than spend hours now tweaking. Once we ship these
typedefs and get feedback from the community I'm sure we can improve
them.
2020-04-22 09:33:44 +00:00
executionContext ( ) : ExecutionContext {
2022-06-13 09:16:25 +00:00
return this . # context ;
2019-01-15 04:34:50 +00:00
}
2020-06-22 15:21:57 +00:00
/ * *
* This method passes this handle as the first argument to ` pageFunction ` .
* If ` pageFunction ` returns a Promise , then ` handle.evaluate ` would wait
* for the promise to resolve and return its value .
*
* @example
* ` ` ` js
* const tweetHandle = await page . $ ( '.tweet .retweets' ) ;
* expect ( await tweetHandle . evaluate ( node = > node . innerText ) ) . toBe ( '10' ) ;
* ` ` `
* /
2020-06-25 12:38:01 +00:00
feat!: type inference for evaluation types (#8547)
This PR greatly improves the types within Puppeteer:
- **Almost everything** is auto-deduced.
- Parameters don't need to be specified in the function. They are deduced from the spread.
- Return types don't need to be specified. They are deduced from the function. (More on this below)
- Selections based on tag names correctly deduce element type, similar to TypeScript's mechanism for `getElementByTagName`.
- [**BREAKING CHANGE**] We've removed the ability to declare return types in type arguments for the following reasons:
1. Setting them will indubitably break auto-deduction.
2. You can just use `as ...` in TypeScript to coerce the correct type (given it makes sense).
- [**BREAKING CHANGE**] `waitFor` is officially gone.
To migrate to these changes, there are only four things you may need to change:
- If you set a return type using the `ReturnType` type parameter, remove it and use `as ...` and `HandleFor` (if necessary).
⛔ `evaluate<ReturnType>(a: number, b: number) => {...}, a, b)`
✅ `(await evaluate(a, b) => {...}, a, b)) as ReturnType`
⛔ `evaluateHandle<ReturnType>(a: number, b: number) => {...}, a, b)`
✅ `(await evaluateHandle(a, b) => {...}, a, b)) as HandleFor<ReturnType>`
- If you set any type parameters in the *parameters* of an evaluation function, remove them.
⛔ `evaluate(a: number, b: number) => {...}, a, b)`
✅ `evaluate(a, b) => {...}, a, b)`
- If you set any type parameters in the method's declaration, remove them.
⛔ `evaluate<(a: number, b: number) => void>((a, b) => {...}, a, b)`
✅ `evaluate(a, b) => {...}, a, b)`
2022-06-23 09:29:46 +00:00
async evaluate <
Params extends unknown [ ] ,
Func extends EvaluateFunc < [ T , . . . Params ] > = EvaluateFunc < [ T , . . . Params ] >
> (
pageFunction : Func | string ,
. . . args : EvaluateParams < Params >
) : Promise < Awaited < ReturnType < Func > >> {
return await this . executionContext ( ) . evaluate ( pageFunction , this , . . . args ) ;
2019-09-04 22:19:34 +00:00
}
2020-06-22 15:21:57 +00:00
/ * *
* This method passes this handle as the first argument to ` pageFunction ` .
*
* @remarks
*
2020-06-25 14:49:35 +00:00
* The only difference between ` jsHandle.evaluate ` and
* ` jsHandle.evaluateHandle ` is that ` jsHandle.evaluateHandle `
* returns an in - page object ( JSHandle ) .
2020-06-22 15:21:57 +00:00
*
2020-06-25 14:49:35 +00:00
* If the function passed to ` jsHandle.evaluateHandle ` returns a Promise ,
* then ` evaluateHandle.evaluateHandle ` waits for the promise to resolve and
* returns its value .
2020-06-22 15:21:57 +00:00
*
* See { @link Page . evaluateHandle } for more details .
* /
feat!: type inference for evaluation types (#8547)
This PR greatly improves the types within Puppeteer:
- **Almost everything** is auto-deduced.
- Parameters don't need to be specified in the function. They are deduced from the spread.
- Return types don't need to be specified. They are deduced from the function. (More on this below)
- Selections based on tag names correctly deduce element type, similar to TypeScript's mechanism for `getElementByTagName`.
- [**BREAKING CHANGE**] We've removed the ability to declare return types in type arguments for the following reasons:
1. Setting them will indubitably break auto-deduction.
2. You can just use `as ...` in TypeScript to coerce the correct type (given it makes sense).
- [**BREAKING CHANGE**] `waitFor` is officially gone.
To migrate to these changes, there are only four things you may need to change:
- If you set a return type using the `ReturnType` type parameter, remove it and use `as ...` and `HandleFor` (if necessary).
⛔ `evaluate<ReturnType>(a: number, b: number) => {...}, a, b)`
✅ `(await evaluate(a, b) => {...}, a, b)) as ReturnType`
⛔ `evaluateHandle<ReturnType>(a: number, b: number) => {...}, a, b)`
✅ `(await evaluateHandle(a, b) => {...}, a, b)) as HandleFor<ReturnType>`
- If you set any type parameters in the *parameters* of an evaluation function, remove them.
⛔ `evaluate(a: number, b: number) => {...}, a, b)`
✅ `evaluate(a, b) => {...}, a, b)`
- If you set any type parameters in the method's declaration, remove them.
⛔ `evaluate<(a: number, b: number) => void>((a, b) => {...}, a, b)`
✅ `evaluate(a, b) => {...}, a, b)`
2022-06-23 09:29:46 +00:00
async evaluateHandle <
Params extends unknown [ ] ,
Func extends EvaluateFunc < [ T , . . . Params ] > = EvaluateFunc < [ T , . . . Params ] >
> (
pageFunction : Func ,
. . . args : EvaluateParams < Params >
) : Promise < HandleFor < Awaited < ReturnType < Func > >>> {
2020-05-07 10:54:55 +00:00
return await this . executionContext ( ) . evaluateHandle (
pageFunction ,
this ,
. . . args
) ;
2019-09-04 22:19:34 +00:00
}
feat!: type inference for evaluation types (#8547)
This PR greatly improves the types within Puppeteer:
- **Almost everything** is auto-deduced.
- Parameters don't need to be specified in the function. They are deduced from the spread.
- Return types don't need to be specified. They are deduced from the function. (More on this below)
- Selections based on tag names correctly deduce element type, similar to TypeScript's mechanism for `getElementByTagName`.
- [**BREAKING CHANGE**] We've removed the ability to declare return types in type arguments for the following reasons:
1. Setting them will indubitably break auto-deduction.
2. You can just use `as ...` in TypeScript to coerce the correct type (given it makes sense).
- [**BREAKING CHANGE**] `waitFor` is officially gone.
To migrate to these changes, there are only four things you may need to change:
- If you set a return type using the `ReturnType` type parameter, remove it and use `as ...` and `HandleFor` (if necessary).
⛔ `evaluate<ReturnType>(a: number, b: number) => {...}, a, b)`
✅ `(await evaluate(a, b) => {...}, a, b)) as ReturnType`
⛔ `evaluateHandle<ReturnType>(a: number, b: number) => {...}, a, b)`
✅ `(await evaluateHandle(a, b) => {...}, a, b)) as HandleFor<ReturnType>`
- If you set any type parameters in the *parameters* of an evaluation function, remove them.
⛔ `evaluate(a: number, b: number) => {...}, a, b)`
✅ `evaluate(a, b) => {...}, a, b)`
- If you set any type parameters in the method's declaration, remove them.
⛔ `evaluate<(a: number, b: number) => void>((a, b) => {...}, a, b)`
✅ `evaluate(a, b) => {...}, a, b)`
2022-06-23 09:29:46 +00:00
/ * *
* Fetches a single property from the referenced object .
2020-06-25 14:49:35 +00:00
* /
feat!: type inference for evaluation types (#8547)
This PR greatly improves the types within Puppeteer:
- **Almost everything** is auto-deduced.
- Parameters don't need to be specified in the function. They are deduced from the spread.
- Return types don't need to be specified. They are deduced from the function. (More on this below)
- Selections based on tag names correctly deduce element type, similar to TypeScript's mechanism for `getElementByTagName`.
- [**BREAKING CHANGE**] We've removed the ability to declare return types in type arguments for the following reasons:
1. Setting them will indubitably break auto-deduction.
2. You can just use `as ...` in TypeScript to coerce the correct type (given it makes sense).
- [**BREAKING CHANGE**] `waitFor` is officially gone.
To migrate to these changes, there are only four things you may need to change:
- If you set a return type using the `ReturnType` type parameter, remove it and use `as ...` and `HandleFor` (if necessary).
⛔ `evaluate<ReturnType>(a: number, b: number) => {...}, a, b)`
✅ `(await evaluate(a, b) => {...}, a, b)) as ReturnType`
⛔ `evaluateHandle<ReturnType>(a: number, b: number) => {...}, a, b)`
✅ `(await evaluateHandle(a, b) => {...}, a, b)) as HandleFor<ReturnType>`
- If you set any type parameters in the *parameters* of an evaluation function, remove them.
⛔ `evaluate(a: number, b: number) => {...}, a, b)`
✅ `evaluate(a, b) => {...}, a, b)`
- If you set any type parameters in the method's declaration, remove them.
⛔ `evaluate<(a: number, b: number) => void>((a, b) => {...}, a, b)`
✅ `evaluate(a, b) => {...}, a, b)`
2022-06-23 09:29:46 +00:00
async getProperty < K extends keyof T > (
propertyName : HandleOr < K >
) : Promise < HandleFor < T [ K ] > > ;
async getProperty ( propertyName : string ) : Promise < JSHandle < unknown > > ;
async getProperty < K extends keyof T > (
propertyName : HandleOr < K >
) : Promise < HandleFor < T [ K ] > > {
return await this . evaluateHandle ( ( object , propertyName ) = > {
return object [ propertyName ] ;
} , propertyName ) ;
2019-01-15 04:34:50 +00:00
}
2020-06-22 15:21:57 +00:00
/ * *
* The method returns a map with property names as keys and JSHandle
* instances for the property values .
*
* @example
* ` ` ` js
* const listHandle = await page . evaluateHandle ( ( ) = > document . body . children ) ;
* const properties = await listHandle . getProperties ( ) ;
* const children = [ ] ;
* for ( const property of properties . values ( ) ) {
* const element = property . asElement ( ) ;
* if ( element )
* children . push ( element ) ;
* }
* children ; // holds elementHandles to all children of document.body
* ` ` `
* /
2020-04-21 11:11:06 +00:00
async getProperties ( ) : Promise < Map < string , JSHandle > > {
2022-06-13 09:16:25 +00:00
assert ( this . # remoteObject . objectId ) ;
const response = await this . # client . send ( 'Runtime.getProperties' , {
objectId : this. # remoteObject . objectId ,
2020-05-07 10:54:55 +00:00
ownProperties : true ,
2019-01-15 04:34:50 +00:00
} ) ;
2020-04-21 11:11:06 +00:00
const result = new Map < string , JSHandle > ( ) ;
2019-01-15 04:34:50 +00:00
for ( const property of response . result ) {
2022-06-14 11:55:35 +00:00
if ( ! property . enumerable || ! property . value ) {
continue ;
}
2022-06-13 09:16:25 +00:00
result . set ( property . name , _createJSHandle ( this . # context , property . value ) ) ;
2019-01-15 04:34:50 +00:00
}
return result ;
}
2020-06-22 15:21:57 +00:00
/ * *
2021-05-26 14:37:38 +00:00
* @returns Returns a JSON representation of the object . If the object has a
* ` toJSON ` function , it will not be called .
2020-06-22 15:21:57 +00:00
* @remarks
*
* The JSON is generated by running { @link https : //developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/JSON/stringify | JSON.stringify}
* on the object in page and consequent { @link https : //developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/JSON/parse | JSON.parse} in puppeteer.
2020-06-25 14:49:35 +00:00
* * * NOTE * * The method throws if the referenced object is not stringifiable .
2020-06-22 15:21:57 +00:00
* /
2021-02-11 09:50:15 +00:00
async jsonValue < T = unknown > ( ) : Promise < T > {
2022-06-13 09:16:25 +00:00
if ( this . # remoteObject . objectId ) {
const response = await this . # client . send ( 'Runtime.callFunctionOn' , {
2019-01-15 04:34:50 +00:00
functionDeclaration : 'function() { return this; }' ,
2022-06-13 09:16:25 +00:00
objectId : this. # remoteObject . objectId ,
2019-01-15 04:34:50 +00:00
returnByValue : true ,
awaitPromise : true ,
} ) ;
2022-06-14 11:16:21 +00:00
return valueFromRemoteObject ( response . result ) as T ;
2019-01-15 04:34:50 +00:00
}
2022-06-14 11:16:21 +00:00
return valueFromRemoteObject ( this . # remoteObject ) as T ;
2019-01-15 04:34:50 +00:00
}
2020-06-25 14:49:35 +00:00
/ * *
2021-05-26 14:37:38 +00:00
* @returns Either ` null ` or the object handle itself , if the object
* handle is an instance of { @link ElementHandle } .
2020-06-25 14:49:35 +00:00
* /
2020-04-21 11:11:06 +00:00
asElement ( ) : ElementHandle | null {
2021-05-26 14:37:38 +00:00
/ * T h i s a l w a y s r e t u r n s n u l l , b u t s u b c l a s s e s c a n o v e r r i d e t h i s a n d r e t u r n a n
2022-06-09 11:27:34 +00:00
ElementHandle .
* /
2019-01-15 04:34:50 +00:00
return null ;
}
2020-06-22 15:21:57 +00:00
/ * *
2020-06-25 14:49:35 +00:00
* Stops referencing the element handle , and resolves when the object handle is
* successfully disposed of .
2020-06-22 15:21:57 +00:00
* /
2020-04-21 11:11:06 +00:00
async dispose ( ) : Promise < void > {
2022-06-14 11:55:35 +00:00
if ( this . # disposed ) {
return ;
}
2022-06-13 09:16:25 +00:00
this . # disposed = true ;
2022-06-14 11:16:21 +00:00
await releaseObject ( this . # client , this . # remoteObject ) ;
2019-01-15 04:34:50 +00:00
}
2020-06-25 14:49:35 +00:00
/ * *
* Returns a string representation of the JSHandle .
*
* @remarks Useful during debugging .
* /
2020-04-21 11:11:06 +00:00
toString ( ) : string {
2022-06-13 09:16:25 +00:00
if ( this . # remoteObject . objectId ) {
const type = this . # remoteObject . subtype || this . # remoteObject . type ;
2019-01-15 04:34:50 +00:00
return 'JSHandle@' + type ;
}
2022-06-14 11:16:21 +00:00
return 'JSHandle:' + valueFromRemoteObject ( this . # remoteObject ) ;
2019-01-15 04:34:50 +00:00
}
}
2020-06-22 15:21:57 +00:00
/ * *
* ElementHandle represents an in - page DOM element .
*
* @remarks
*
* ElementHandles can be created with the { @link Page . $ } method .
*
* ` ` ` js
* const puppeteer = require ( 'puppeteer' ) ;
*
* ( async ( ) = > {
* const browser = await puppeteer . launch ( ) ;
* const page = await browser . newPage ( ) ;
* await page . goto ( 'https://example.com' ) ;
* const hrefElement = await page . $ ( 'a' ) ;
* await hrefElement . click ( ) ;
* // ...
* } ) ( ) ;
* ` ` `
*
2020-06-25 14:49:35 +00:00
* ElementHandle prevents the DOM element from being garbage - collected unless the
* handle is { @link JSHandle . dispose | disposed } . ElementHandles are auto - disposed
* when their origin frame gets navigated .
2020-06-22 15:21:57 +00:00
*
* ElementHandle instances can be used as arguments in { @link Page . $eval } and
* { @link Page . evaluate } methods .
*
2020-07-02 09:09:34 +00:00
* If you ' re using TypeScript , ElementHandle takes a generic argument that
* denotes the type of element the handle is holding within . For example , if you
* have a handle to a ` <select> ` element , you can type it as
* ` ElementHandle<HTMLSelectElement> ` and you get some nicer type checks .
*
2020-06-22 15:21:57 +00:00
* @public
* /
2020-07-02 09:09:34 +00:00
export class ElementHandle <
ElementType extends Element = Element
2021-05-26 13:46:17 +00:00
> extends JSHandle < ElementType > {
2022-06-13 09:16:25 +00:00
# frame : Frame ;
# page : Page ;
# frameManager : FrameManager ;
2020-06-22 15:21:57 +00:00
/ * *
* @internal
* /
2020-05-07 10:54:55 +00:00
constructor (
context : ExecutionContext ,
client : CDPSession ,
remoteObject : Protocol.Runtime.RemoteObject ,
2022-01-17 06:32:52 +00:00
frame : Frame ,
2020-05-07 10:54:55 +00:00
page : Page ,
frameManager : FrameManager
) {
2019-01-15 04:34:50 +00:00
super ( context , client , remoteObject ) ;
2022-06-13 09:16:25 +00:00
this . # frame = frame ;
this . # page = page ;
this . # frameManager = frameManager ;
2019-01-15 04:34:50 +00:00
}
2021-12-09 11:51:14 +00:00
/ * *
* Wait for the ` selector ` to appear within the element . If at the moment of calling the
* method the ` selector ` already exists , the method will return immediately . If
* the ` selector ` doesn ' t appear after the ` timeout ` milliseconds of waiting , the
* function will throw .
*
* This method does not work across navigations or if the element is detached from DOM .
*
* @param selector - A
* { @link https : //developer.mozilla.org/en-US/docs/Web/CSS/CSS_Selectors | selector}
* of an element to wait for
* @param options - Optional waiting parameters
* @returns Promise which resolves when element specified by selector string
* is added to DOM . Resolves to ` null ` if waiting for hidden : ` true ` and
* selector is not found in DOM .
* @remarks
* The optional parameters in ` options ` are :
*
* - ` visible ` : wait for the selected element to be present in DOM and to be
* visible , i . e . to not have ` display: none ` or ` visibility: hidden ` CSS
* properties . Defaults to ` false ` .
*
* - ` hidden ` : wait for the selected element to not be found in the DOM or to be hidden ,
* i . e . have ` display: none ` or ` visibility: hidden ` CSS properties . Defaults to
* ` false ` .
*
* - ` timeout ` : maximum time to wait in milliseconds . Defaults to ` 30000 `
* ( 30 seconds ) . Pass ` 0 ` to disable timeout . The default value can be changed
* by using the { @link Page . setDefaultTimeout } method .
* /
feat!: type inference for evaluation types (#8547)
This PR greatly improves the types within Puppeteer:
- **Almost everything** is auto-deduced.
- Parameters don't need to be specified in the function. They are deduced from the spread.
- Return types don't need to be specified. They are deduced from the function. (More on this below)
- Selections based on tag names correctly deduce element type, similar to TypeScript's mechanism for `getElementByTagName`.
- [**BREAKING CHANGE**] We've removed the ability to declare return types in type arguments for the following reasons:
1. Setting them will indubitably break auto-deduction.
2. You can just use `as ...` in TypeScript to coerce the correct type (given it makes sense).
- [**BREAKING CHANGE**] `waitFor` is officially gone.
To migrate to these changes, there are only four things you may need to change:
- If you set a return type using the `ReturnType` type parameter, remove it and use `as ...` and `HandleFor` (if necessary).
⛔ `evaluate<ReturnType>(a: number, b: number) => {...}, a, b)`
✅ `(await evaluate(a, b) => {...}, a, b)) as ReturnType`
⛔ `evaluateHandle<ReturnType>(a: number, b: number) => {...}, a, b)`
✅ `(await evaluateHandle(a, b) => {...}, a, b)) as HandleFor<ReturnType>`
- If you set any type parameters in the *parameters* of an evaluation function, remove them.
⛔ `evaluate(a: number, b: number) => {...}, a, b)`
✅ `evaluate(a, b) => {...}, a, b)`
- If you set any type parameters in the method's declaration, remove them.
⛔ `evaluate<(a: number, b: number) => void>((a, b) => {...}, a, b)`
✅ `evaluate(a, b) => {...}, a, b)`
2022-06-23 09:29:46 +00:00
async waitForSelector < Selector extends keyof HTMLElementTagNameMap > (
selector : Selector ,
options? : Exclude < WaitForSelectorOptions , ' root ' >
) : Promise < ElementHandle < HTMLElementTagNameMap [ Selector ] > | null > ;
2021-12-21 08:53:20 +00:00
async waitForSelector (
2021-12-09 11:51:14 +00:00
selector : string ,
feat!: type inference for evaluation types (#8547)
This PR greatly improves the types within Puppeteer:
- **Almost everything** is auto-deduced.
- Parameters don't need to be specified in the function. They are deduced from the spread.
- Return types don't need to be specified. They are deduced from the function. (More on this below)
- Selections based on tag names correctly deduce element type, similar to TypeScript's mechanism for `getElementByTagName`.
- [**BREAKING CHANGE**] We've removed the ability to declare return types in type arguments for the following reasons:
1. Setting them will indubitably break auto-deduction.
2. You can just use `as ...` in TypeScript to coerce the correct type (given it makes sense).
- [**BREAKING CHANGE**] `waitFor` is officially gone.
To migrate to these changes, there are only four things you may need to change:
- If you set a return type using the `ReturnType` type parameter, remove it and use `as ...` and `HandleFor` (if necessary).
⛔ `evaluate<ReturnType>(a: number, b: number) => {...}, a, b)`
✅ `(await evaluate(a, b) => {...}, a, b)) as ReturnType`
⛔ `evaluateHandle<ReturnType>(a: number, b: number) => {...}, a, b)`
✅ `(await evaluateHandle(a, b) => {...}, a, b)) as HandleFor<ReturnType>`
- If you set any type parameters in the *parameters* of an evaluation function, remove them.
⛔ `evaluate(a: number, b: number) => {...}, a, b)`
✅ `evaluate(a, b) => {...}, a, b)`
- If you set any type parameters in the method's declaration, remove them.
⛔ `evaluate<(a: number, b: number) => void>((a, b) => {...}, a, b)`
✅ `evaluate(a, b) => {...}, a, b)`
2022-06-23 09:29:46 +00:00
options? : Exclude < WaitForSelectorOptions , ' root ' >
) : Promise < ElementHandle | null > ;
async waitForSelector (
selector : string ,
options : Exclude < WaitForSelectorOptions , ' root ' > = { }
2021-12-09 11:51:14 +00:00
) : Promise < ElementHandle | null > {
2021-12-21 08:53:20 +00:00
const frame = this . _context . frame ( ) ;
2022-05-31 14:34:16 +00:00
assert ( frame ) ;
2021-12-21 08:53:20 +00:00
const secondaryContext = await frame . _secondaryWorld . executionContext ( ) ;
const adoptedRoot = await secondaryContext . _adoptElementHandle ( this ) ;
const handle = await frame . _secondaryWorld . waitForSelector ( selector , {
2021-12-09 11:51:14 +00:00
. . . options ,
2021-12-21 08:53:20 +00:00
root : adoptedRoot ,
2021-12-09 11:51:14 +00:00
} ) ;
2021-12-21 08:53:20 +00:00
await adoptedRoot . dispose ( ) ;
2022-06-14 11:55:35 +00:00
if ( ! handle ) {
return null ;
}
2021-12-21 08:53:20 +00:00
const mainExecutionContext = await frame . _mainWorld . executionContext ( ) ;
const result = await mainExecutionContext . _adoptElementHandle ( handle ) ;
await handle . dispose ( ) ;
return result ;
2021-12-09 11:51:14 +00:00
}
2022-05-10 10:45:20 +00:00
/ * *
* Wait for the ` xpath ` within the element . If at the moment of calling the
* method the ` xpath ` already exists , the method will return immediately . If
* the ` xpath ` doesn ' t appear after the ` timeout ` milliseconds of waiting , the
* function will throw .
*
* If ` xpath ` starts with ` // ` instead of ` .// ` , the dot will be appended automatically .
*
* This method works across navigation
* ` ` ` js
* const puppeteer = require ( 'puppeteer' ) ;
* ( async ( ) = > {
* const browser = await puppeteer . launch ( ) ;
* const page = await browser . newPage ( ) ;
* let currentURL ;
* page
* . waitForXPath ( '//img' )
* . then ( ( ) = > console . log ( 'First URL with image: ' + currentURL ) ) ;
* for ( currentURL of [
* 'https://example.com' ,
* 'https://google.com' ,
* 'https://bbc.com' ,
* ] ) {
* await page . goto ( currentURL ) ;
* }
* await browser . close ( ) ;
* } ) ( ) ;
* ` ` `
* @param xpath - A
* { @link https : //developer.mozilla.org/en-US/docs/Web/XPath | xpath} of an
* element to wait for
* @param options - Optional waiting parameters
* @returns Promise which resolves when element specified by xpath string is
* added to DOM . Resolves to ` null ` if waiting for ` hidden: true ` and xpath is
* not found in DOM .
* @remarks
* The optional Argument ` options ` have properties :
*
* - ` visible ` : A boolean to wait for element to be present in DOM and to be
* visible , i . e . to not have ` display: none ` or ` visibility: hidden ` CSS
* properties . Defaults to ` false ` .
*
* - ` hidden ` : A boolean wait for element to not be found in the DOM or to be
* hidden , i . e . have ` display: none ` or ` visibility: hidden ` CSS properties .
* Defaults to ` false ` .
*
* - ` timeout ` : A number which is maximum time to wait for in milliseconds .
* Defaults to ` 30000 ` ( 30 seconds ) . Pass ` 0 ` to disable timeout . The default
* value can be changed by using the { @link Page . setDefaultTimeout } method .
* /
async waitForXPath (
xpath : string ,
options : {
visible? : boolean ;
hidden? : boolean ;
timeout? : number ;
} = { }
) : Promise < ElementHandle | null > {
const frame = this . _context . frame ( ) ;
2022-05-31 14:34:16 +00:00
assert ( frame ) ;
2022-05-10 10:45:20 +00:00
const secondaryContext = await frame . _secondaryWorld . executionContext ( ) ;
const adoptedRoot = await secondaryContext . _adoptElementHandle ( this ) ;
xpath = xpath . startsWith ( '//' ) ? '.' + xpath : xpath ;
if ( ! xpath . startsWith ( './/' ) ) {
await adoptedRoot . dispose ( ) ;
throw new Error ( 'Unsupported xpath expression: ' + xpath ) ;
}
const handle = await frame . _secondaryWorld . waitForXPath ( xpath , {
. . . options ,
root : adoptedRoot ,
} ) ;
await adoptedRoot . dispose ( ) ;
2022-06-14 11:55:35 +00:00
if ( ! handle ) {
return null ;
}
2022-05-10 10:45:20 +00:00
const mainExecutionContext = await frame . _mainWorld . executionContext ( ) ;
const result = await mainExecutionContext . _adoptElementHandle ( handle ) ;
await handle . dispose ( ) ;
return result ;
}
2022-05-31 14:34:16 +00:00
override asElement ( ) : ElementHandle < ElementType > | null {
2019-01-15 04:34:50 +00:00
return this ;
}
2020-06-22 15:21:57 +00:00
/ * *
* Resolves to the content frame for element handles referencing
* iframe nodes , or null otherwise
* /
2020-04-29 11:28:16 +00:00
async contentFrame ( ) : Promise < Frame | null > {
2019-01-15 04:34:50 +00:00
const nodeInfo = await this . _client . send ( 'DOM.describeNode' , {
2020-05-07 10:54:55 +00:00
objectId : this._remoteObject.objectId ,
2019-01-15 04:34:50 +00:00
} ) ;
2022-06-14 11:55:35 +00:00
if ( typeof nodeInfo . node . frameId !== 'string' ) {
return null ;
}
2022-06-13 09:16:25 +00:00
return this . # frameManager . frame ( nodeInfo . node . frameId ) ;
2019-01-15 04:34:50 +00:00
}
2022-06-13 09:16:25 +00:00
async # scrollIntoViewIfNeeded ( ) : Promise < void > {
2022-05-31 14:34:16 +00:00
const error = await this . evaluate (
feat!: type inference for evaluation types (#8547)
This PR greatly improves the types within Puppeteer:
- **Almost everything** is auto-deduced.
- Parameters don't need to be specified in the function. They are deduced from the spread.
- Return types don't need to be specified. They are deduced from the function. (More on this below)
- Selections based on tag names correctly deduce element type, similar to TypeScript's mechanism for `getElementByTagName`.
- [**BREAKING CHANGE**] We've removed the ability to declare return types in type arguments for the following reasons:
1. Setting them will indubitably break auto-deduction.
2. You can just use `as ...` in TypeScript to coerce the correct type (given it makes sense).
- [**BREAKING CHANGE**] `waitFor` is officially gone.
To migrate to these changes, there are only four things you may need to change:
- If you set a return type using the `ReturnType` type parameter, remove it and use `as ...` and `HandleFor` (if necessary).
⛔ `evaluate<ReturnType>(a: number, b: number) => {...}, a, b)`
✅ `(await evaluate(a, b) => {...}, a, b)) as ReturnType`
⛔ `evaluateHandle<ReturnType>(a: number, b: number) => {...}, a, b)`
✅ `(await evaluateHandle(a, b) => {...}, a, b)) as HandleFor<ReturnType>`
- If you set any type parameters in the *parameters* of an evaluation function, remove them.
⛔ `evaluate(a: number, b: number) => {...}, a, b)`
✅ `evaluate(a, b) => {...}, a, b)`
- If you set any type parameters in the method's declaration, remove them.
⛔ `evaluate<(a: number, b: number) => void>((a, b) => {...}, a, b)`
✅ `evaluate(a, b) => {...}, a, b)`
2022-06-23 09:29:46 +00:00
async ( element , pageJavascriptEnabled ) : Promise < string | false > = > {
2022-06-14 11:55:35 +00:00
if ( ! element . isConnected ) {
return 'Node is detached from document' ;
}
if ( element . nodeType !== Node . ELEMENT_NODE ) {
2022-05-31 14:34:16 +00:00
return 'Node is not of type HTMLElement' ;
2022-06-14 11:55:35 +00:00
}
2022-05-31 14:34:16 +00:00
// force-scroll if page's javascript is disabled.
if ( ! pageJavascriptEnabled ) {
element . scrollIntoView ( {
block : 'center' ,
inline : 'center' ,
// @ts-expect-error Chrome still supports behavior: instant but
// it's not in the spec so TS shouts We don't want to make this
// breaking change in Puppeteer yet so we'll ignore the line.
behavior : 'instant' ,
} ) ;
return false ;
}
2022-06-22 13:25:44 +00:00
const visibleRatio = await new Promise ( resolve = > {
const observer = new IntersectionObserver ( entries = > {
2022-05-31 14:34:16 +00:00
resolve ( entries [ 0 ] ! . intersectionRatio ) ;
observer . disconnect ( ) ;
} ) ;
observer . observe ( element ) ;
2019-01-15 04:34:50 +00:00
} ) ;
2022-05-31 14:34:16 +00:00
if ( visibleRatio !== 1.0 ) {
element . scrollIntoView ( {
block : 'center' ,
inline : 'center' ,
// @ts-expect-error Chrome still supports behavior: instant but
// it's not in the spec so TS shouts We don't want to make this
// breaking change in Puppeteer yet so we'll ignore the line.
behavior : 'instant' ,
} ) ;
}
2020-05-07 10:54:55 +00:00
return false ;
2022-05-31 14:34:16 +00:00
} ,
2022-06-13 09:16:25 +00:00
this . # page . isJavaScriptEnabled ( )
2022-05-31 14:34:16 +00:00
) ;
2020-04-21 11:11:06 +00:00
2022-06-14 11:55:35 +00:00
if ( error ) {
throw new Error ( error ) ;
}
2019-01-15 04:34:50 +00:00
}
2022-06-13 09:16:25 +00:00
async # getOOPIFOffsets (
2022-01-17 13:19:43 +00:00
frame : Frame
2022-06-22 13:25:44 +00:00
) : Promise < { offsetX : number ; offsetY : number } > {
2022-01-17 06:32:52 +00:00
let offsetX = 0 ;
let offsetY = 0 ;
2022-05-31 14:34:16 +00:00
let currentFrame : Frame | null = frame ;
while ( currentFrame && currentFrame . parentFrame ( ) ) {
const parent = currentFrame . parentFrame ( ) ;
if ( ! currentFrame . isOOPFrame ( ) || ! parent ) {
currentFrame = parent ;
2022-01-17 06:32:52 +00:00
continue ;
}
2022-06-22 13:25:44 +00:00
const { backendNodeId } = await parent . _client ( ) . send ( 'DOM.getFrameOwner' , {
frameId : currentFrame._id ,
} ) ;
2022-06-13 09:16:25 +00:00
const result = await parent . _client ( ) . send ( 'DOM.getBoxModel' , {
2022-01-17 06:32:52 +00:00
backendNodeId : backendNodeId ,
} ) ;
2022-01-18 08:22:15 +00:00
if ( ! result ) {
2022-01-17 06:32:52 +00:00
break ;
}
2022-01-18 08:22:15 +00:00
const contentBoxQuad = result . model . content ;
2022-06-13 09:16:25 +00:00
const topLeftCorner = this . # fromProtocolQuad ( contentBoxQuad ) [ 0 ] ;
2022-05-31 14:34:16 +00:00
offsetX += topLeftCorner ! . x ;
offsetY += topLeftCorner ! . y ;
currentFrame = parent ;
2022-01-17 06:32:52 +00:00
}
2022-06-22 13:25:44 +00:00
return { offsetX , offsetY } ;
2022-01-17 13:19:43 +00:00
}
/ * *
* Returns the middle point within an element unless a specific offset is provided .
* /
async clickablePoint ( offset? : Offset ) : Promise < Point > {
const [ result , layoutMetrics ] = await Promise . all ( [
this . _client
. send ( 'DOM.getContentQuads' , {
objectId : this._remoteObject.objectId ,
} )
. catch ( debugError ) ,
2022-06-13 09:16:25 +00:00
this . # page . _client ( ) . send ( 'Page.getLayoutMetrics' ) ,
2022-01-17 13:19:43 +00:00
] ) ;
2022-06-14 11:55:35 +00:00
if ( ! result || ! result . quads . length ) {
2022-01-17 13:19:43 +00:00
throw new Error ( 'Node is either not clickable or not an HTMLElement' ) ;
2022-06-14 11:55:35 +00:00
}
2022-01-17 13:19:43 +00:00
// Filter out quads that have too small area to click into.
// Fallback to `layoutViewport` in case of using Firefox.
2022-06-22 13:25:44 +00:00
const { clientWidth , clientHeight } =
2022-01-17 13:19:43 +00:00
layoutMetrics . cssLayoutViewport || layoutMetrics . layoutViewport ;
2022-06-22 13:25:44 +00:00
const { offsetX , offsetY } = await this . # getOOPIFOffsets ( this . # frame ) ;
2020-05-07 10:54:55 +00:00
const quads = result . quads
2022-06-22 13:25:44 +00:00
. map ( quad = > {
2022-06-15 10:42:21 +00:00
return this . # fromProtocolQuad ( quad ) ;
} )
2022-06-22 13:25:44 +00:00
. map ( quad = > {
2022-06-15 10:42:21 +00:00
return applyOffsetsToQuad ( quad , offsetX , offsetY ) ;
} )
2022-06-22 13:25:44 +00:00
. map ( quad = > {
2022-06-15 10:42:21 +00:00
return this . # intersectQuadWithViewport ( quad , clientWidth , clientHeight ) ;
} )
2022-06-22 13:25:44 +00:00
. filter ( quad = > {
2022-06-15 10:42:21 +00:00
return computeQuadArea ( quad ) > 1 ;
} ) ;
2022-06-14 11:55:35 +00:00
if ( ! quads . length ) {
2021-09-14 16:38:58 +00:00
throw new Error ( 'Node is either not clickable or not an HTMLElement' ) ;
2022-06-14 11:55:35 +00:00
}
2022-05-31 14:34:16 +00:00
const quad = quads [ 0 ] ! ;
2021-09-20 09:01:32 +00:00
if ( offset ) {
// Return the point of the first quad identified by offset.
let minX = Number . MAX_SAFE_INTEGER ;
let minY = Number . MAX_SAFE_INTEGER ;
for ( const point of quad ) {
if ( point . x < minX ) {
minX = point . x ;
}
if ( point . y < minY ) {
minY = point . y ;
}
}
if (
minX !== Number . MAX_SAFE_INTEGER &&
minY !== Number . MAX_SAFE_INTEGER
) {
return {
x : minX + offset . x ,
y : minY + offset . y ,
} ;
}
}
// Return the middle point of the first quad.
2019-01-15 04:34:50 +00:00
let x = 0 ;
let y = 0 ;
for ( const point of quad ) {
x += point . x ;
y += point . y ;
}
return {
x : x / 4 ,
2020-05-07 10:54:55 +00:00
y : y / 4 ,
2019-01-15 04:34:50 +00:00
} ;
}
2022-06-13 09:16:25 +00:00
# getBoxModel ( ) : Promise < void | Protocol.DOM.GetBoxModelResponse > {
2020-07-10 10:51:52 +00:00
const params : Protocol.DOM.GetBoxModelRequest = {
objectId : this._remoteObject.objectId ,
} ;
2022-06-22 13:25:44 +00:00
return this . _client . send ( 'DOM.getBoxModel' , params ) . catch ( error = > {
2022-06-15 10:42:21 +00:00
return debugError ( error ) ;
} ) ;
2019-01-15 04:34:50 +00:00
}
2022-06-13 09:16:25 +00:00
# fromProtocolQuad ( quad : number [ ] ) : Point [ ] {
2019-01-15 04:34:50 +00:00
return [
2022-06-22 13:25:44 +00:00
{ x : quad [ 0 ] ! , y : quad [ 1 ] ! } ,
{ x : quad [ 2 ] ! , y : quad [ 3 ] ! } ,
{ x : quad [ 4 ] ! , y : quad [ 5 ] ! } ,
{ x : quad [ 6 ] ! , y : quad [ 7 ] ! } ,
2019-01-15 04:34:50 +00:00
] ;
}
2022-06-13 09:16:25 +00:00
# intersectQuadWithViewport (
2022-05-31 14:34:16 +00:00
quad : Point [ ] ,
2020-05-07 10:54:55 +00:00
width : number ,
height : number
2022-05-31 14:34:16 +00:00
) : Point [ ] {
2022-06-22 13:25:44 +00:00
return quad . map ( point = > {
2022-06-15 10:42:21 +00:00
return {
x : Math.min ( Math . max ( point . x , 0 ) , width ) ,
y : Math.min ( Math . max ( point . y , 0 ) , height ) ,
} ;
} ) ;
2019-04-12 01:11:20 +00:00
}
2020-06-22 15:21:57 +00:00
/ * *
* This method scrolls element into view if needed , and then
* uses { @link Page . mouse } to hover over the center of the element .
* If the element is detached from DOM , the method throws an error .
* /
2020-04-21 11:11:06 +00:00
async hover ( ) : Promise < void > {
2022-06-13 09:16:25 +00:00
await this . # scrollIntoViewIfNeeded ( ) ;
2022-06-22 13:25:44 +00:00
const { x , y } = await this . clickablePoint ( ) ;
2022-06-13 09:16:25 +00:00
await this . # page . mouse . move ( x , y ) ;
2019-01-15 04:34:50 +00:00
}
2020-06-22 15:21:57 +00:00
/ * *
* This method scrolls element into view if needed , and then
* uses { @link Page . mouse } to click in the center of the element .
* If the element is detached from DOM , the method throws an error .
* /
2020-06-23 05:18:46 +00:00
async click ( options : ClickOptions = { } ) : Promise < void > {
2022-06-13 09:16:25 +00:00
await this . # scrollIntoViewIfNeeded ( ) ;
2022-06-22 13:25:44 +00:00
const { x , y } = await this . clickablePoint ( options . offset ) ;
2022-06-13 09:16:25 +00:00
await this . # page . mouse . click ( x , y , options ) ;
2019-01-15 04:34:50 +00:00
}
2021-06-04 10:25:36 +00:00
/ * *
* This method creates and captures a dragevent from the element .
* /
async drag ( target : Point ) : Promise < Protocol.Input.DragData > {
assert (
2022-06-13 09:16:25 +00:00
this . # page . isDragInterceptionEnabled ( ) ,
2021-06-04 10:25:36 +00:00
'Drag Interception is not enabled!'
) ;
2022-06-13 09:16:25 +00:00
await this . # scrollIntoViewIfNeeded ( ) ;
2021-06-04 10:25:36 +00:00
const start = await this . clickablePoint ( ) ;
2022-06-13 09:16:25 +00:00
return await this . # page . mouse . drag ( start , target ) ;
2021-06-04 10:25:36 +00:00
}
/ * *
* This method creates a ` dragenter ` event on the element .
* /
async dragEnter (
2022-06-22 13:25:44 +00:00
data : Protocol.Input.DragData = { items : [ ] , dragOperationsMask : 1 }
2021-06-04 10:25:36 +00:00
) : Promise < void > {
2022-06-13 09:16:25 +00:00
await this . # scrollIntoViewIfNeeded ( ) ;
2021-06-04 10:25:36 +00:00
const target = await this . clickablePoint ( ) ;
2022-06-13 09:16:25 +00:00
await this . # page . mouse . dragEnter ( target , data ) ;
2021-06-04 10:25:36 +00:00
}
/ * *
* This method creates a ` dragover ` event on the element .
* /
async dragOver (
2022-06-22 13:25:44 +00:00
data : Protocol.Input.DragData = { items : [ ] , dragOperationsMask : 1 }
2021-06-04 10:25:36 +00:00
) : Promise < void > {
2022-06-13 09:16:25 +00:00
await this . # scrollIntoViewIfNeeded ( ) ;
2021-06-04 10:25:36 +00:00
const target = await this . clickablePoint ( ) ;
2022-06-13 09:16:25 +00:00
await this . # page . mouse . dragOver ( target , data ) ;
2021-06-04 10:25:36 +00:00
}
/ * *
* This method triggers a drop on the element .
* /
async drop (
2022-06-22 13:25:44 +00:00
data : Protocol.Input.DragData = { items : [ ] , dragOperationsMask : 1 }
2021-06-04 10:25:36 +00:00
) : Promise < void > {
2022-06-13 09:16:25 +00:00
await this . # scrollIntoViewIfNeeded ( ) ;
2021-06-04 10:25:36 +00:00
const destination = await this . clickablePoint ( ) ;
2022-06-13 09:16:25 +00:00
await this . # page . mouse . drop ( destination , data ) ;
2021-06-04 10:25:36 +00:00
}
/ * *
* This method triggers a dragenter , dragover , and drop on the element .
* /
async dragAndDrop (
target : ElementHandle ,
2022-06-22 13:25:44 +00:00
options ? : { delay : number }
2021-06-04 10:25:36 +00:00
) : Promise < void > {
2022-06-13 09:16:25 +00:00
await this . # scrollIntoViewIfNeeded ( ) ;
2021-06-04 10:25:36 +00:00
const startPoint = await this . clickablePoint ( ) ;
const targetPoint = await target . clickablePoint ( ) ;
2022-06-13 09:16:25 +00:00
await this . # page . mouse . dragAndDrop ( startPoint , targetPoint , options ) ;
2021-06-04 10:25:36 +00:00
}
2020-06-22 15:21:57 +00:00
/ * *
* Triggers a ` change ` and ` input ` event once all the provided options have been
* selected . If there ' s no ` <select> ` element matching ` selector ` , the method
* throws an error .
*
* @example
* ` ` ` js
* handle . select ( 'blue' ) ; // single selection
* handle . select ( 'red' , 'green' , 'blue' ) ; // multiple selections
* ` ` `
* @param values - Values of options to select . If the ` <select> ` has the
* ` multiple ` attribute , all values are considered , otherwise only the first
* one is taken into account .
* /
2020-04-21 11:11:06 +00:00
async select ( . . . values : string [ ] ) : Promise < string [ ] > {
2022-06-09 11:27:34 +00:00
for ( const value of values ) {
2020-05-07 10:54:55 +00:00
assert (
2022-06-14 11:16:21 +00:00
isString ( value ) ,
2020-05-07 10:54:55 +00:00
'Values must be strings. Found value "' +
value +
'" of type "' +
typeof value +
'"'
) ;
2022-06-09 11:27:34 +00:00
}
2020-04-21 11:11:06 +00:00
feat!: type inference for evaluation types (#8547)
This PR greatly improves the types within Puppeteer:
- **Almost everything** is auto-deduced.
- Parameters don't need to be specified in the function. They are deduced from the spread.
- Return types don't need to be specified. They are deduced from the function. (More on this below)
- Selections based on tag names correctly deduce element type, similar to TypeScript's mechanism for `getElementByTagName`.
- [**BREAKING CHANGE**] We've removed the ability to declare return types in type arguments for the following reasons:
1. Setting them will indubitably break auto-deduction.
2. You can just use `as ...` in TypeScript to coerce the correct type (given it makes sense).
- [**BREAKING CHANGE**] `waitFor` is officially gone.
To migrate to these changes, there are only four things you may need to change:
- If you set a return type using the `ReturnType` type parameter, remove it and use `as ...` and `HandleFor` (if necessary).
⛔ `evaluate<ReturnType>(a: number, b: number) => {...}, a, b)`
✅ `(await evaluate(a, b) => {...}, a, b)) as ReturnType`
⛔ `evaluateHandle<ReturnType>(a: number, b: number) => {...}, a, b)`
✅ `(await evaluateHandle(a, b) => {...}, a, b)) as HandleFor<ReturnType>`
- If you set any type parameters in the *parameters* of an evaluation function, remove them.
⛔ `evaluate(a: number, b: number) => {...}, a, b)`
✅ `evaluate(a, b) => {...}, a, b)`
- If you set any type parameters in the method's declaration, remove them.
⛔ `evaluate<(a: number, b: number) => void>((a, b) => {...}, a, b)`
✅ `evaluate(a, b) => {...}, a, b)`
2022-06-23 09:29:46 +00:00
return this . evaluate ( ( element , vals ) : string [ ] = > {
2022-06-09 11:27:34 +00:00
const values = new Set ( vals ) ;
if ( ! ( element instanceof HTMLSelectElement ) ) {
throw new Error ( 'Element is not a <select> element.' ) ;
}
2021-05-26 13:46:17 +00:00
2022-06-09 11:27:34 +00:00
const selectedValues = new Set < string > ( ) ;
if ( ! element . multiple ) {
for ( const option of element . options ) {
option . selected = false ;
2021-05-26 13:46:17 +00:00
}
2022-06-09 11:27:34 +00:00
for ( const option of element . options ) {
if ( values . has ( option . value ) ) {
option . selected = true ;
selectedValues . add ( option . value ) ;
break ;
}
}
} else {
for ( const option of element . options ) {
option . selected = values . has ( option . value ) ;
if ( option . selected ) {
selectedValues . add ( option . value ) ;
}
}
}
2022-06-22 13:25:44 +00:00
element . dispatchEvent ( new Event ( 'input' , { bubbles : true } ) ) ;
element . dispatchEvent ( new Event ( 'change' , { bubbles : true } ) ) ;
2022-06-09 11:27:34 +00:00
return [ . . . selectedValues . values ( ) ] ;
} , values ) ;
2019-09-04 22:19:34 +00:00
}
2020-06-22 15:21:57 +00:00
/ * *
* This method expects ` elementHandle ` to point to an
* { @link https : //developer.mozilla.org/en-US/docs/Web/HTML/Element/input | input element}.
2022-06-07 14:17:21 +00:00
*
2020-06-22 15:21:57 +00:00
* @param filePaths - Sets the value of the file input to these paths .
2022-06-07 14:17:21 +00:00
* If a path is relative , then it is resolved against the
* { @link https : //nodejs.org/api/process.html#process_process_cwd | current working directory}.
* Note for locals script connecting to remote chrome environments ,
* paths must be absolute .
2020-06-22 15:21:57 +00:00
* /
feat!: type inference for evaluation types (#8547)
This PR greatly improves the types within Puppeteer:
- **Almost everything** is auto-deduced.
- Parameters don't need to be specified in the function. They are deduced from the spread.
- Return types don't need to be specified. They are deduced from the function. (More on this below)
- Selections based on tag names correctly deduce element type, similar to TypeScript's mechanism for `getElementByTagName`.
- [**BREAKING CHANGE**] We've removed the ability to declare return types in type arguments for the following reasons:
1. Setting them will indubitably break auto-deduction.
2. You can just use `as ...` in TypeScript to coerce the correct type (given it makes sense).
- [**BREAKING CHANGE**] `waitFor` is officially gone.
To migrate to these changes, there are only four things you may need to change:
- If you set a return type using the `ReturnType` type parameter, remove it and use `as ...` and `HandleFor` (if necessary).
⛔ `evaluate<ReturnType>(a: number, b: number) => {...}, a, b)`
✅ `(await evaluate(a, b) => {...}, a, b)) as ReturnType`
⛔ `evaluateHandle<ReturnType>(a: number, b: number) => {...}, a, b)`
✅ `(await evaluateHandle(a, b) => {...}, a, b)) as HandleFor<ReturnType>`
- If you set any type parameters in the *parameters* of an evaluation function, remove them.
⛔ `evaluate(a: number, b: number) => {...}, a, b)`
✅ `evaluate(a, b) => {...}, a, b)`
- If you set any type parameters in the method's declaration, remove them.
⛔ `evaluate<(a: number, b: number) => void>((a, b) => {...}, a, b)`
✅ `evaluate(a, b) => {...}, a, b)`
2022-06-23 09:29:46 +00:00
async uploadFile (
this : ElementHandle < HTMLInputElement > ,
. . . filePaths : string [ ]
) : Promise < void > {
const isMultiple = await this . evaluate ( element = > {
return element . multiple ;
} ) ;
2020-05-07 10:54:55 +00:00
assert (
filePaths . length <= 1 || isMultiple ,
'Multiple file uploads only work with <input type=file multiple>'
) ;
2020-04-16 15:22:52 +00:00
2020-04-24 11:36:46 +00:00
// Locate all files and confirm that they exist.
2022-06-09 11:03:44 +00:00
let path : typeof import ( 'path' ) ;
try {
path = await import ( 'path' ) ;
} catch ( error ) {
if ( error instanceof TypeError ) {
throw new Error (
` JSHandle#uploadFile can only be used in Node-like environments. `
) ;
}
throw error ;
}
2022-06-22 13:25:44 +00:00
const files = filePaths . map ( filePath = > {
2022-06-10 12:34:57 +00:00
if ( path . win32 . isAbsolute ( filePath ) || path . posix . isAbsolute ( filePath ) ) {
2022-06-07 14:17:21 +00:00
return filePath ;
} else {
return path . resolve ( filePath ) ;
}
} ) ;
2022-06-22 13:25:44 +00:00
const { objectId } = this . _remoteObject ;
const { node } = await this . _client . send ( 'DOM.describeNode' , { objectId } ) ;
const { backendNodeId } = node ;
2020-04-16 15:22:52 +00:00
2021-05-26 14:37:38 +00:00
/ * T h e z e r o - l e n g t h a r r a y i s a s p e c i a l c a s e , i t s e e m s t h a t
2022-06-09 11:27:34 +00:00
DOM . setFileInputFiles does not actually update the files in that case ,
so the solution is to eval the element value to a new FileList directly .
* /
2020-04-16 15:22:52 +00:00
if ( files . length === 0 ) {
feat!: type inference for evaluation types (#8547)
This PR greatly improves the types within Puppeteer:
- **Almost everything** is auto-deduced.
- Parameters don't need to be specified in the function. They are deduced from the spread.
- Return types don't need to be specified. They are deduced from the function. (More on this below)
- Selections based on tag names correctly deduce element type, similar to TypeScript's mechanism for `getElementByTagName`.
- [**BREAKING CHANGE**] We've removed the ability to declare return types in type arguments for the following reasons:
1. Setting them will indubitably break auto-deduction.
2. You can just use `as ...` in TypeScript to coerce the correct type (given it makes sense).
- [**BREAKING CHANGE**] `waitFor` is officially gone.
To migrate to these changes, there are only four things you may need to change:
- If you set a return type using the `ReturnType` type parameter, remove it and use `as ...` and `HandleFor` (if necessary).
⛔ `evaluate<ReturnType>(a: number, b: number) => {...}, a, b)`
✅ `(await evaluate(a, b) => {...}, a, b)) as ReturnType`
⛔ `evaluateHandle<ReturnType>(a: number, b: number) => {...}, a, b)`
✅ `(await evaluateHandle(a, b) => {...}, a, b)) as HandleFor<ReturnType>`
- If you set any type parameters in the *parameters* of an evaluation function, remove them.
⛔ `evaluate(a: number, b: number) => {...}, a, b)`
✅ `evaluate(a, b) => {...}, a, b)`
- If you set any type parameters in the method's declaration, remove them.
⛔ `evaluate<(a: number, b: number) => void>((a, b) => {...}, a, b)`
✅ `evaluate(a, b) => {...}, a, b)`
2022-06-23 09:29:46 +00:00
await this . evaluate ( element = > {
2020-04-16 15:22:52 +00:00
element . files = new DataTransfer ( ) . files ;
// Dispatch events for this case because it should behave akin to a user action.
2022-06-22 13:25:44 +00:00
element . dispatchEvent ( new Event ( 'input' , { bubbles : true } ) ) ;
element . dispatchEvent ( new Event ( 'change' , { bubbles : true } ) ) ;
2020-04-16 15:22:52 +00:00
} ) ;
} else {
2020-05-07 10:54:55 +00:00
await this . _client . send ( 'DOM.setFileInputFiles' , {
objectId ,
files ,
backendNodeId ,
} ) ;
2019-12-03 08:18:18 +00:00
}
2019-01-15 04:34:50 +00:00
}
2020-06-22 15:21:57 +00:00
/ * *
* This method scrolls element into view if needed , and then uses
* { @link Touchscreen . tap } to tap in the center of the element .
* If the element is detached from DOM , the method throws an error .
* /
2020-04-21 11:11:06 +00:00
async tap ( ) : Promise < void > {
2022-06-13 09:16:25 +00:00
await this . # scrollIntoViewIfNeeded ( ) ;
2022-06-22 13:25:44 +00:00
const { x , y } = await this . clickablePoint ( ) ;
2022-06-13 09:16:25 +00:00
await this . # page . touchscreen . tap ( x , y ) ;
2019-01-15 04:34:50 +00:00
}
2020-06-22 15:21:57 +00:00
/ * *
* Calls { @link https : //developer.mozilla.org/en-US/docs/Web/API/HTMLElement/focus | focus} on the element.
* /
2020-04-21 11:11:06 +00:00
async focus ( ) : Promise < void > {
feat!: type inference for evaluation types (#8547)
This PR greatly improves the types within Puppeteer:
- **Almost everything** is auto-deduced.
- Parameters don't need to be specified in the function. They are deduced from the spread.
- Return types don't need to be specified. They are deduced from the function. (More on this below)
- Selections based on tag names correctly deduce element type, similar to TypeScript's mechanism for `getElementByTagName`.
- [**BREAKING CHANGE**] We've removed the ability to declare return types in type arguments for the following reasons:
1. Setting them will indubitably break auto-deduction.
2. You can just use `as ...` in TypeScript to coerce the correct type (given it makes sense).
- [**BREAKING CHANGE**] `waitFor` is officially gone.
To migrate to these changes, there are only four things you may need to change:
- If you set a return type using the `ReturnType` type parameter, remove it and use `as ...` and `HandleFor` (if necessary).
⛔ `evaluate<ReturnType>(a: number, b: number) => {...}, a, b)`
✅ `(await evaluate(a, b) => {...}, a, b)) as ReturnType`
⛔ `evaluateHandle<ReturnType>(a: number, b: number) => {...}, a, b)`
✅ `(await evaluateHandle(a, b) => {...}, a, b)) as HandleFor<ReturnType>`
- If you set any type parameters in the *parameters* of an evaluation function, remove them.
⛔ `evaluate(a: number, b: number) => {...}, a, b)`
✅ `evaluate(a, b) => {...}, a, b)`
- If you set any type parameters in the method's declaration, remove them.
⛔ `evaluate<(a: number, b: number) => void>((a, b) => {...}, a, b)`
✅ `evaluate(a, b) => {...}, a, b)`
2022-06-23 09:29:46 +00:00
await this . evaluate ( element = > {
if ( ! ( element instanceof HTMLElement ) ) {
throw new Error ( 'Cannot focus non-HTMLElement' ) ;
}
2022-06-15 10:42:21 +00:00
return element . focus ( ) ;
} ) ;
2019-01-15 04:34:50 +00:00
}
2020-06-22 15:21:57 +00:00
/ * *
* Focuses the element , and then sends a ` keydown ` , ` keypress ` / ` input ` , and
* ` keyup ` event for each character in the text .
*
* To press a special key , like ` Control ` or ` ArrowDown ` ,
* use { @link ElementHandle . press } .
*
* @example
* ` ` ` js
* await elementHandle . type ( 'Hello' ) ; // Types instantly
* await elementHandle . type ( 'World' , { delay : 100 } ) ; // Types slower, like a user
* ` ` `
*
* @example
* An example of typing into a text field and then submitting the form :
*
* ` ` ` js
* const elementHandle = await page . $ ( 'input' ) ;
* await elementHandle . type ( 'some text' ) ;
* await elementHandle . press ( 'Enter' ) ;
* ` ` `
* /
2022-06-22 13:25:44 +00:00
async type ( text : string , options ? : { delay : number } ) : Promise < void > {
2019-01-15 04:34:50 +00:00
await this . focus ( ) ;
2022-06-13 09:16:25 +00:00
await this . # page . keyboard . type ( text , options ) ;
2019-01-15 04:34:50 +00:00
}
2020-06-22 15:21:57 +00:00
/ * *
* Focuses the element , and then uses { @link Keyboard . down } and { @link Keyboard . up } .
*
* @remarks
* If ` key ` is a single character and no modifier keys besides ` Shift `
* are being held down , a ` keypress ` / ` input ` event will also be generated .
* The ` text ` option can be specified to force an input event to be generated .
*
* * * NOTE * * Modifier keys DO affect ` elementHandle.press ` . Holding down ` Shift `
* will type the text in upper case .
*
* @param key - Name of key to press , such as ` ArrowLeft ` .
* See { @link KeyInput } for a list of all key names .
* /
async press ( key : KeyInput , options? : PressOptions ) : Promise < void > {
2019-01-15 04:34:50 +00:00
await this . focus ( ) ;
2022-06-13 09:16:25 +00:00
await this . # page . keyboard . press ( key , options ) ;
2019-01-15 04:34:50 +00:00
}
2020-06-22 15:21:57 +00:00
/ * *
* This method returns the bounding box of the element ( relative to the main frame ) ,
* or ` null ` if the element is not visible .
* /
async boundingBox ( ) : Promise < BoundingBox | null > {
2022-06-13 09:16:25 +00:00
const result = await this . # getBoxModel ( ) ;
2019-01-15 04:34:50 +00:00
2022-06-14 11:55:35 +00:00
if ( ! result ) {
return null ;
}
2019-01-15 04:34:50 +00:00
2022-06-22 13:25:44 +00:00
const { offsetX , offsetY } = await this . # getOOPIFOffsets ( this . # frame ) ;
2019-01-15 04:34:50 +00:00
const quad = result . model . border ;
2022-05-31 14:34:16 +00:00
const x = Math . min ( quad [ 0 ] ! , quad [ 2 ] ! , quad [ 4 ] ! , quad [ 6 ] ! ) ;
const y = Math . min ( quad [ 1 ] ! , quad [ 3 ] ! , quad [ 5 ] ! , quad [ 7 ] ! ) ;
const width = Math . max ( quad [ 0 ] ! , quad [ 2 ] ! , quad [ 4 ] ! , quad [ 6 ] ! ) - x ;
const height = Math . max ( quad [ 1 ] ! , quad [ 3 ] ! , quad [ 5 ] ! , quad [ 7 ] ! ) - y ;
2019-01-15 04:34:50 +00:00
2022-06-22 13:25:44 +00:00
return { x : x + offsetX , y : y + offsetY , width , height } ;
2019-01-15 04:34:50 +00:00
}
/ * *
2020-06-22 15:21:57 +00:00
* This method returns boxes of the element , or ` null ` if the element is not visible .
*
* @remarks
*
* Boxes are represented as an array of points ;
* Each Point is an object ` {x, y} ` . Box points are sorted clock - wise .
2019-01-15 04:34:50 +00:00
* /
2020-04-21 11:11:06 +00:00
async boxModel ( ) : Promise < BoxModel | null > {
2022-06-13 09:16:25 +00:00
const result = await this . # getBoxModel ( ) ;
2019-01-15 04:34:50 +00:00
2022-06-14 11:55:35 +00:00
if ( ! result ) {
return null ;
}
2019-01-15 04:34:50 +00:00
2022-06-22 13:25:44 +00:00
const { offsetX , offsetY } = await this . # getOOPIFOffsets ( this . # frame ) ;
2022-01-17 13:19:43 +00:00
2022-06-22 13:25:44 +00:00
const { content , padding , border , margin , width , height } = result . model ;
2019-01-15 04:34:50 +00:00
return {
2022-01-17 13:19:43 +00:00
content : applyOffsetsToQuad (
2022-06-13 09:16:25 +00:00
this . # fromProtocolQuad ( content ) ,
2022-01-17 13:19:43 +00:00
offsetX ,
offsetY
) ,
padding : applyOffsetsToQuad (
2022-06-13 09:16:25 +00:00
this . # fromProtocolQuad ( padding ) ,
2022-01-17 13:19:43 +00:00
offsetX ,
offsetY
) ,
border : applyOffsetsToQuad (
2022-06-13 09:16:25 +00:00
this . # fromProtocolQuad ( border ) ,
2022-01-17 13:19:43 +00:00
offsetX ,
offsetY
) ,
margin : applyOffsetsToQuad (
2022-06-13 09:16:25 +00:00
this . # fromProtocolQuad ( margin ) ,
2022-01-17 13:19:43 +00:00
offsetX ,
offsetY
) ,
2019-01-15 04:34:50 +00:00
width ,
2020-05-07 10:54:55 +00:00
height ,
2019-01-15 04:34:50 +00:00
} ;
}
2020-06-22 15:21:57 +00:00
/ * *
* This method scrolls element into view if needed , and then uses
* { @link Page . screenshot } to take a screenshot of the element .
* If the element is detached from DOM , the method throws an error .
* /
2021-09-29 15:46:57 +00:00
async screenshot ( options : ScreenshotOptions = { } ) : Promise < string | Buffer > {
2019-01-15 04:34:50 +00:00
let needsViewportReset = false ;
let boundingBox = await this . boundingBox ( ) ;
assert ( boundingBox , 'Node is either not visible or not an HTMLElement' ) ;
2022-06-13 09:16:25 +00:00
const viewport = this . # page . viewport ( ) ;
2022-05-31 14:34:16 +00:00
assert ( viewport ) ;
2019-01-15 04:34:50 +00:00
2020-05-07 10:54:55 +00:00
if (
2022-05-31 14:34:16 +00:00
boundingBox . width > viewport . width ||
boundingBox . height > viewport . height
2020-05-07 10:54:55 +00:00
) {
2019-01-15 04:34:50 +00:00
const newViewport = {
width : Math.max ( viewport . width , Math . ceil ( boundingBox . width ) ) ,
height : Math.max ( viewport . height , Math . ceil ( boundingBox . height ) ) ,
} ;
2022-06-13 09:16:25 +00:00
await this . # page . setViewport ( Object . assign ( { } , viewport , newViewport ) ) ;
2019-01-15 04:34:50 +00:00
needsViewportReset = true ;
}
2022-06-13 09:16:25 +00:00
await this . # scrollIntoViewIfNeeded ( ) ;
2019-01-15 04:34:50 +00:00
boundingBox = await this . boundingBox ( ) ;
assert ( boundingBox , 'Node is either not visible or not an HTMLElement' ) ;
assert ( boundingBox . width !== 0 , 'Node has 0 width.' ) ;
assert ( boundingBox . height !== 0 , 'Node has 0 height.' ) ;
2021-07-01 11:23:38 +00:00
const layoutMetrics = await this . _client . send ( 'Page.getLayoutMetrics' ) ;
// Fallback to `layoutViewport` in case of using Firefox.
2022-06-22 13:25:44 +00:00
const { pageX , pageY } =
2022-02-15 10:15:18 +00:00
layoutMetrics . cssVisualViewport || layoutMetrics . layoutViewport ;
2019-01-15 04:34:50 +00:00
const clip = Object . assign ( { } , boundingBox ) ;
clip . x += pageX ;
clip . y += pageY ;
2022-06-13 09:16:25 +00:00
const imageData = await this . # page . screenshot (
2020-05-07 10:54:55 +00:00
Object . assign (
{ } ,
{
clip ,
} ,
options
)
) ;
2019-01-15 04:34:50 +00:00
2022-06-14 11:55:35 +00:00
if ( needsViewportReset ) {
await this . # page . setViewport ( viewport ) ;
}
2019-01-15 04:34:50 +00:00
return imageData ;
}
2020-06-22 15:21:57 +00:00
/ * *
2022-05-31 14:34:16 +00:00
* Runs ` element.querySelector ` within the page .
*
2022-05-31 17:04:30 +00:00
* @param selector - The selector to query with .
2022-05-31 14:34:16 +00:00
* @returns ` null ` if no element matches the selector .
* @throws ` Error ` if the selector has no associated query handler .
2020-06-22 15:21:57 +00:00
* /
feat!: type inference for evaluation types (#8547)
This PR greatly improves the types within Puppeteer:
- **Almost everything** is auto-deduced.
- Parameters don't need to be specified in the function. They are deduced from the spread.
- Return types don't need to be specified. They are deduced from the function. (More on this below)
- Selections based on tag names correctly deduce element type, similar to TypeScript's mechanism for `getElementByTagName`.
- [**BREAKING CHANGE**] We've removed the ability to declare return types in type arguments for the following reasons:
1. Setting them will indubitably break auto-deduction.
2. You can just use `as ...` in TypeScript to coerce the correct type (given it makes sense).
- [**BREAKING CHANGE**] `waitFor` is officially gone.
To migrate to these changes, there are only four things you may need to change:
- If you set a return type using the `ReturnType` type parameter, remove it and use `as ...` and `HandleFor` (if necessary).
⛔ `evaluate<ReturnType>(a: number, b: number) => {...}, a, b)`
✅ `(await evaluate(a, b) => {...}, a, b)) as ReturnType`
⛔ `evaluateHandle<ReturnType>(a: number, b: number) => {...}, a, b)`
✅ `(await evaluateHandle(a, b) => {...}, a, b)) as HandleFor<ReturnType>`
- If you set any type parameters in the *parameters* of an evaluation function, remove them.
⛔ `evaluate(a: number, b: number) => {...}, a, b)`
✅ `evaluate(a, b) => {...}, a, b)`
- If you set any type parameters in the method's declaration, remove them.
⛔ `evaluate<(a: number, b: number) => void>((a, b) => {...}, a, b)`
✅ `evaluate(a, b) => {...}, a, b)`
2022-06-23 09:29:46 +00:00
async $ < Selector extends keyof HTMLElementTagNameMap > (
selector : Selector
) : Promise < ElementHandle < HTMLElementTagNameMap [ Selector ] > | null > ;
async $ ( selector : string ) : Promise < ElementHandle | null > ;
async $ ( selector : string ) : Promise < ElementHandle | null > {
2022-06-22 13:25:44 +00:00
const { updatedSelector , queryHandler } =
2022-06-13 09:16:25 +00:00
_getQueryHandlerAndSelector ( selector ) ;
2022-05-31 14:34:16 +00:00
assert (
queryHandler . queryOne ,
'Cannot handle queries for a single element with the given selector'
) ;
2020-09-23 14:02:22 +00:00
return queryHandler . queryOne ( this , updatedSelector ) ;
2019-01-15 04:34:50 +00:00
}
2020-06-22 15:21:57 +00:00
/ * *
2020-06-25 14:49:35 +00:00
* Runs ` element.querySelectorAll ` within the page . If no elements match the selector ,
* the return value resolves to ` [] ` .
2020-06-22 15:21:57 +00:00
* /
2022-05-31 14:34:16 +00:00
/ * *
* Runs ` element.querySelectorAll ` within the page .
*
2022-05-31 17:04:30 +00:00
* @param selector - The selector to query with .
2022-05-31 14:34:16 +00:00
* @returns ` [] ` if no element matches the selector .
* @throws ` Error ` if the selector has no associated query handler .
* /
feat!: type inference for evaluation types (#8547)
This PR greatly improves the types within Puppeteer:
- **Almost everything** is auto-deduced.
- Parameters don't need to be specified in the function. They are deduced from the spread.
- Return types don't need to be specified. They are deduced from the function. (More on this below)
- Selections based on tag names correctly deduce element type, similar to TypeScript's mechanism for `getElementByTagName`.
- [**BREAKING CHANGE**] We've removed the ability to declare return types in type arguments for the following reasons:
1. Setting them will indubitably break auto-deduction.
2. You can just use `as ...` in TypeScript to coerce the correct type (given it makes sense).
- [**BREAKING CHANGE**] `waitFor` is officially gone.
To migrate to these changes, there are only four things you may need to change:
- If you set a return type using the `ReturnType` type parameter, remove it and use `as ...` and `HandleFor` (if necessary).
⛔ `evaluate<ReturnType>(a: number, b: number) => {...}, a, b)`
✅ `(await evaluate(a, b) => {...}, a, b)) as ReturnType`
⛔ `evaluateHandle<ReturnType>(a: number, b: number) => {...}, a, b)`
✅ `(await evaluateHandle(a, b) => {...}, a, b)) as HandleFor<ReturnType>`
- If you set any type parameters in the *parameters* of an evaluation function, remove them.
⛔ `evaluate(a: number, b: number) => {...}, a, b)`
✅ `evaluate(a, b) => {...}, a, b)`
- If you set any type parameters in the method's declaration, remove them.
⛔ `evaluate<(a: number, b: number) => void>((a, b) => {...}, a, b)`
✅ `evaluate(a, b) => {...}, a, b)`
2022-06-23 09:29:46 +00:00
async $ $ < Selector extends keyof HTMLElementTagNameMap > (
selector : Selector
) : Promise < ElementHandle < HTMLElementTagNameMap [ Selector ] > [ ] > ;
async $ $ ( selector : string ) : Promise < ElementHandle [ ] > ;
async $ $ ( selector : string ) : Promise < ElementHandle [ ] > {
2022-06-22 13:25:44 +00:00
const { updatedSelector , queryHandler } =
2022-06-13 09:16:25 +00:00
_getQueryHandlerAndSelector ( selector ) ;
2022-05-31 14:34:16 +00:00
assert (
queryHandler . queryAll ,
'Cannot handle queries for a multiple element with the given selector'
) ;
2020-09-23 14:02:22 +00:00
return queryHandler . queryAll ( this , updatedSelector ) ;
2019-01-15 04:34:50 +00:00
}
2020-06-22 15:21:57 +00:00
/ * *
* This method runs ` document.querySelector ` within the element and passes it as
* the first argument to ` pageFunction ` . If there ' s no element matching ` selector ` ,
* the method throws an error .
*
* If ` pageFunction ` returns a Promise , then ` frame. $ eval ` would wait for the promise
* to resolve and return its value .
*
* @example
* ` ` ` js
* const tweetHandle = await page . $ ( '.tweet' ) ;
* expect ( await tweetHandle . $eval ( '.like' , node = > node . innerText ) ) . toBe ( '100' ) ;
* expect ( await tweetHandle . $eval ( '.retweets' , node = > node . innerText ) ) . toBe ( '10' ) ;
* ` ` `
* /
feat!: type inference for evaluation types (#8547)
This PR greatly improves the types within Puppeteer:
- **Almost everything** is auto-deduced.
- Parameters don't need to be specified in the function. They are deduced from the spread.
- Return types don't need to be specified. They are deduced from the function. (More on this below)
- Selections based on tag names correctly deduce element type, similar to TypeScript's mechanism for `getElementByTagName`.
- [**BREAKING CHANGE**] We've removed the ability to declare return types in type arguments for the following reasons:
1. Setting them will indubitably break auto-deduction.
2. You can just use `as ...` in TypeScript to coerce the correct type (given it makes sense).
- [**BREAKING CHANGE**] `waitFor` is officially gone.
To migrate to these changes, there are only four things you may need to change:
- If you set a return type using the `ReturnType` type parameter, remove it and use `as ...` and `HandleFor` (if necessary).
⛔ `evaluate<ReturnType>(a: number, b: number) => {...}, a, b)`
✅ `(await evaluate(a, b) => {...}, a, b)) as ReturnType`
⛔ `evaluateHandle<ReturnType>(a: number, b: number) => {...}, a, b)`
✅ `(await evaluateHandle(a, b) => {...}, a, b)) as HandleFor<ReturnType>`
- If you set any type parameters in the *parameters* of an evaluation function, remove them.
⛔ `evaluate(a: number, b: number) => {...}, a, b)`
✅ `evaluate(a, b) => {...}, a, b)`
- If you set any type parameters in the method's declaration, remove them.
⛔ `evaluate<(a: number, b: number) => void>((a, b) => {...}, a, b)`
✅ `evaluate(a, b) => {...}, a, b)`
2022-06-23 09:29:46 +00:00
async $eval <
Selector extends keyof HTMLElementTagNameMap ,
Params extends unknown [ ] ,
Func extends EvaluateFunc <
[ HTMLElementTagNameMap [ Selector ] , . . . Params ]
> = EvaluateFunc < [ HTMLElementTagNameMap [ Selector ] , . . . Params ] >
> (
selector : Selector ,
pageFunction : Func | string ,
. . . args : EvaluateParams < Params >
) : Promise < Awaited < ReturnType < Func > >> ;
async $eval <
Params extends unknown [ ] ,
Func extends EvaluateFunc < [ Element , . . . Params ] > = EvaluateFunc <
[ Element , . . . Params ]
>
> (
selector : string ,
pageFunction : Func | string ,
. . . args : EvaluateParams < Params >
) : Promise < Awaited < ReturnType < Func > >> ;
async $eval <
Params extends unknown [ ] ,
Func extends EvaluateFunc < [ Element , . . . Params ] > = EvaluateFunc <
[ Element , . . . Params ]
>
> (
2020-05-07 10:54:55 +00:00
selector : string ,
feat!: type inference for evaluation types (#8547)
This PR greatly improves the types within Puppeteer:
- **Almost everything** is auto-deduced.
- Parameters don't need to be specified in the function. They are deduced from the spread.
- Return types don't need to be specified. They are deduced from the function. (More on this below)
- Selections based on tag names correctly deduce element type, similar to TypeScript's mechanism for `getElementByTagName`.
- [**BREAKING CHANGE**] We've removed the ability to declare return types in type arguments for the following reasons:
1. Setting them will indubitably break auto-deduction.
2. You can just use `as ...` in TypeScript to coerce the correct type (given it makes sense).
- [**BREAKING CHANGE**] `waitFor` is officially gone.
To migrate to these changes, there are only four things you may need to change:
- If you set a return type using the `ReturnType` type parameter, remove it and use `as ...` and `HandleFor` (if necessary).
⛔ `evaluate<ReturnType>(a: number, b: number) => {...}, a, b)`
✅ `(await evaluate(a, b) => {...}, a, b)) as ReturnType`
⛔ `evaluateHandle<ReturnType>(a: number, b: number) => {...}, a, b)`
✅ `(await evaluateHandle(a, b) => {...}, a, b)) as HandleFor<ReturnType>`
- If you set any type parameters in the *parameters* of an evaluation function, remove them.
⛔ `evaluate(a: number, b: number) => {...}, a, b)`
✅ `evaluate(a, b) => {...}, a, b)`
- If you set any type parameters in the method's declaration, remove them.
⛔ `evaluate<(a: number, b: number) => void>((a, b) => {...}, a, b)`
✅ `evaluate(a, b) => {...}, a, b)`
2022-06-23 09:29:46 +00:00
pageFunction : Func | string ,
. . . args : EvaluateParams < Params >
) : Promise < Awaited < ReturnType < Func > >> {
2019-01-15 04:34:50 +00:00
const elementHandle = await this . $ ( selector ) ;
2022-06-14 11:55:35 +00:00
if ( ! elementHandle ) {
2020-05-07 10:54:55 +00:00
throw new Error (
` Error: failed to find element matching selector " ${ selector } " `
) ;
2022-06-14 11:55:35 +00:00
}
feat!: type inference for evaluation types (#8547)
This PR greatly improves the types within Puppeteer:
- **Almost everything** is auto-deduced.
- Parameters don't need to be specified in the function. They are deduced from the spread.
- Return types don't need to be specified. They are deduced from the function. (More on this below)
- Selections based on tag names correctly deduce element type, similar to TypeScript's mechanism for `getElementByTagName`.
- [**BREAKING CHANGE**] We've removed the ability to declare return types in type arguments for the following reasons:
1. Setting them will indubitably break auto-deduction.
2. You can just use `as ...` in TypeScript to coerce the correct type (given it makes sense).
- [**BREAKING CHANGE**] `waitFor` is officially gone.
To migrate to these changes, there are only four things you may need to change:
- If you set a return type using the `ReturnType` type parameter, remove it and use `as ...` and `HandleFor` (if necessary).
⛔ `evaluate<ReturnType>(a: number, b: number) => {...}, a, b)`
✅ `(await evaluate(a, b) => {...}, a, b)) as ReturnType`
⛔ `evaluateHandle<ReturnType>(a: number, b: number) => {...}, a, b)`
✅ `(await evaluateHandle(a, b) => {...}, a, b)) as HandleFor<ReturnType>`
- If you set any type parameters in the *parameters* of an evaluation function, remove them.
⛔ `evaluate(a: number, b: number) => {...}, a, b)`
✅ `evaluate(a, b) => {...}, a, b)`
- If you set any type parameters in the method's declaration, remove them.
⛔ `evaluate<(a: number, b: number) => void>((a, b) => {...}, a, b)`
✅ `evaluate(a, b) => {...}, a, b)`
2022-06-23 09:29:46 +00:00
const result = await elementHandle . evaluate ( pageFunction , . . . args ) ;
2019-01-15 04:34:50 +00:00
await elementHandle . dispose ( ) ;
feat!: type inference for evaluation types (#8547)
This PR greatly improves the types within Puppeteer:
- **Almost everything** is auto-deduced.
- Parameters don't need to be specified in the function. They are deduced from the spread.
- Return types don't need to be specified. They are deduced from the function. (More on this below)
- Selections based on tag names correctly deduce element type, similar to TypeScript's mechanism for `getElementByTagName`.
- [**BREAKING CHANGE**] We've removed the ability to declare return types in type arguments for the following reasons:
1. Setting them will indubitably break auto-deduction.
2. You can just use `as ...` in TypeScript to coerce the correct type (given it makes sense).
- [**BREAKING CHANGE**] `waitFor` is officially gone.
To migrate to these changes, there are only four things you may need to change:
- If you set a return type using the `ReturnType` type parameter, remove it and use `as ...` and `HandleFor` (if necessary).
⛔ `evaluate<ReturnType>(a: number, b: number) => {...}, a, b)`
✅ `(await evaluate(a, b) => {...}, a, b)) as ReturnType`
⛔ `evaluateHandle<ReturnType>(a: number, b: number) => {...}, a, b)`
✅ `(await evaluateHandle(a, b) => {...}, a, b)) as HandleFor<ReturnType>`
- If you set any type parameters in the *parameters* of an evaluation function, remove them.
⛔ `evaluate(a: number, b: number) => {...}, a, b)`
✅ `evaluate(a, b) => {...}, a, b)`
- If you set any type parameters in the method's declaration, remove them.
⛔ `evaluate<(a: number, b: number) => void>((a, b) => {...}, a, b)`
✅ `evaluate(a, b) => {...}, a, b)`
2022-06-23 09:29:46 +00:00
return result ;
2019-01-15 04:34:50 +00:00
}
2020-06-22 15:21:57 +00:00
/ * *
* This method runs ` document.querySelectorAll ` within the element and passes it as
* the first argument to ` pageFunction ` . If there ' s no element matching ` selector ` ,
* the method throws an error .
*
* If ` pageFunction ` returns a Promise , then ` frame. $ $ eval ` would wait for the
* promise to resolve and return its value .
*
* @example
* ` ` ` html
* < div class = "feed" >
* < div class = "tweet" > Hello ! < / div >
* < div class = "tweet" > Hi ! < / div >
* < / div >
* ` ` `
*
* @example
* ` ` ` js
* const feedHandle = await page . $ ( '.feed' ) ;
* expect ( await feedHandle . $ $eval ( '.tweet' , nodes = > nodes . map ( n = > n . innerText ) ) )
* . toEqual ( [ 'Hello!' , 'Hi!' ] ) ;
* ` ` `
* /
feat!: type inference for evaluation types (#8547)
This PR greatly improves the types within Puppeteer:
- **Almost everything** is auto-deduced.
- Parameters don't need to be specified in the function. They are deduced from the spread.
- Return types don't need to be specified. They are deduced from the function. (More on this below)
- Selections based on tag names correctly deduce element type, similar to TypeScript's mechanism for `getElementByTagName`.
- [**BREAKING CHANGE**] We've removed the ability to declare return types in type arguments for the following reasons:
1. Setting them will indubitably break auto-deduction.
2. You can just use `as ...` in TypeScript to coerce the correct type (given it makes sense).
- [**BREAKING CHANGE**] `waitFor` is officially gone.
To migrate to these changes, there are only four things you may need to change:
- If you set a return type using the `ReturnType` type parameter, remove it and use `as ...` and `HandleFor` (if necessary).
⛔ `evaluate<ReturnType>(a: number, b: number) => {...}, a, b)`
✅ `(await evaluate(a, b) => {...}, a, b)) as ReturnType`
⛔ `evaluateHandle<ReturnType>(a: number, b: number) => {...}, a, b)`
✅ `(await evaluateHandle(a, b) => {...}, a, b)) as HandleFor<ReturnType>`
- If you set any type parameters in the *parameters* of an evaluation function, remove them.
⛔ `evaluate(a: number, b: number) => {...}, a, b)`
✅ `evaluate(a, b) => {...}, a, b)`
- If you set any type parameters in the method's declaration, remove them.
⛔ `evaluate<(a: number, b: number) => void>((a, b) => {...}, a, b)`
✅ `evaluate(a, b) => {...}, a, b)`
2022-06-23 09:29:46 +00:00
async $ $eval <
Selector extends keyof HTMLElementTagNameMap ,
Params extends unknown [ ] ,
Func extends EvaluateFunc <
[ HTMLElementTagNameMap [ Selector ] [ ] , . . . Params ]
> = EvaluateFunc < [ HTMLElementTagNameMap [ Selector ] [ ] , . . . Params ] >
> (
selector : Selector ,
pageFunction : Func | string ,
. . . args : EvaluateParams < Params >
) : Promise < Awaited < ReturnType < Func > >> ;
async $ $eval <
Params extends unknown [ ] ,
Func extends EvaluateFunc < [ Element [ ] , . . . Params ] > = EvaluateFunc <
[ Element [ ] , . . . Params ]
>
> (
2020-05-07 10:54:55 +00:00
selector : string ,
feat!: type inference for evaluation types (#8547)
This PR greatly improves the types within Puppeteer:
- **Almost everything** is auto-deduced.
- Parameters don't need to be specified in the function. They are deduced from the spread.
- Return types don't need to be specified. They are deduced from the function. (More on this below)
- Selections based on tag names correctly deduce element type, similar to TypeScript's mechanism for `getElementByTagName`.
- [**BREAKING CHANGE**] We've removed the ability to declare return types in type arguments for the following reasons:
1. Setting them will indubitably break auto-deduction.
2. You can just use `as ...` in TypeScript to coerce the correct type (given it makes sense).
- [**BREAKING CHANGE**] `waitFor` is officially gone.
To migrate to these changes, there are only four things you may need to change:
- If you set a return type using the `ReturnType` type parameter, remove it and use `as ...` and `HandleFor` (if necessary).
⛔ `evaluate<ReturnType>(a: number, b: number) => {...}, a, b)`
✅ `(await evaluate(a, b) => {...}, a, b)) as ReturnType`
⛔ `evaluateHandle<ReturnType>(a: number, b: number) => {...}, a, b)`
✅ `(await evaluateHandle(a, b) => {...}, a, b)) as HandleFor<ReturnType>`
- If you set any type parameters in the *parameters* of an evaluation function, remove them.
⛔ `evaluate(a: number, b: number) => {...}, a, b)`
✅ `evaluate(a, b) => {...}, a, b)`
- If you set any type parameters in the method's declaration, remove them.
⛔ `evaluate<(a: number, b: number) => void>((a, b) => {...}, a, b)`
✅ `evaluate(a, b) => {...}, a, b)`
2022-06-23 09:29:46 +00:00
pageFunction : Func | string ,
. . . args : EvaluateParams < Params >
) : Promise < Awaited < ReturnType < Func > >> ;
async $ $eval <
Params extends unknown [ ] ,
Func extends EvaluateFunc < [ Element [ ] , . . . Params ] > = EvaluateFunc <
[ Element [ ] , . . . Params ]
>
> (
selector : string ,
pageFunction : Func | string ,
. . . args : EvaluateParams < Params >
) : Promise < Awaited < ReturnType < Func > >> {
2022-06-22 13:25:44 +00:00
const { updatedSelector , queryHandler } =
2022-06-13 09:16:25 +00:00
_getQueryHandlerAndSelector ( selector ) ;
2022-05-31 14:34:16 +00:00
assert ( queryHandler . queryAllArray ) ;
2020-09-23 14:02:22 +00:00
const arrayHandle = await queryHandler . queryAllArray ( this , updatedSelector ) ;
feat!: type inference for evaluation types (#8547)
This PR greatly improves the types within Puppeteer:
- **Almost everything** is auto-deduced.
- Parameters don't need to be specified in the function. They are deduced from the spread.
- Return types don't need to be specified. They are deduced from the function. (More on this below)
- Selections based on tag names correctly deduce element type, similar to TypeScript's mechanism for `getElementByTagName`.
- [**BREAKING CHANGE**] We've removed the ability to declare return types in type arguments for the following reasons:
1. Setting them will indubitably break auto-deduction.
2. You can just use `as ...` in TypeScript to coerce the correct type (given it makes sense).
- [**BREAKING CHANGE**] `waitFor` is officially gone.
To migrate to these changes, there are only four things you may need to change:
- If you set a return type using the `ReturnType` type parameter, remove it and use `as ...` and `HandleFor` (if necessary).
⛔ `evaluate<ReturnType>(a: number, b: number) => {...}, a, b)`
✅ `(await evaluate(a, b) => {...}, a, b)) as ReturnType`
⛔ `evaluateHandle<ReturnType>(a: number, b: number) => {...}, a, b)`
✅ `(await evaluateHandle(a, b) => {...}, a, b)) as HandleFor<ReturnType>`
- If you set any type parameters in the *parameters* of an evaluation function, remove them.
⛔ `evaluate(a: number, b: number) => {...}, a, b)`
✅ `evaluate(a, b) => {...}, a, b)`
- If you set any type parameters in the method's declaration, remove them.
⛔ `evaluate<(a: number, b: number) => void>((a, b) => {...}, a, b)`
✅ `evaluate(a, b) => {...}, a, b)`
2022-06-23 09:29:46 +00:00
const result = await arrayHandle . evaluate ( pageFunction , . . . args ) ;
2019-01-15 04:34:50 +00:00
await arrayHandle . dispose ( ) ;
feat!: type inference for evaluation types (#8547)
This PR greatly improves the types within Puppeteer:
- **Almost everything** is auto-deduced.
- Parameters don't need to be specified in the function. They are deduced from the spread.
- Return types don't need to be specified. They are deduced from the function. (More on this below)
- Selections based on tag names correctly deduce element type, similar to TypeScript's mechanism for `getElementByTagName`.
- [**BREAKING CHANGE**] We've removed the ability to declare return types in type arguments for the following reasons:
1. Setting them will indubitably break auto-deduction.
2. You can just use `as ...` in TypeScript to coerce the correct type (given it makes sense).
- [**BREAKING CHANGE**] `waitFor` is officially gone.
To migrate to these changes, there are only four things you may need to change:
- If you set a return type using the `ReturnType` type parameter, remove it and use `as ...` and `HandleFor` (if necessary).
⛔ `evaluate<ReturnType>(a: number, b: number) => {...}, a, b)`
✅ `(await evaluate(a, b) => {...}, a, b)) as ReturnType`
⛔ `evaluateHandle<ReturnType>(a: number, b: number) => {...}, a, b)`
✅ `(await evaluateHandle(a, b) => {...}, a, b)) as HandleFor<ReturnType>`
- If you set any type parameters in the *parameters* of an evaluation function, remove them.
⛔ `evaluate(a: number, b: number) => {...}, a, b)`
✅ `evaluate(a, b) => {...}, a, b)`
- If you set any type parameters in the method's declaration, remove them.
⛔ `evaluate<(a: number, b: number) => void>((a, b) => {...}, a, b)`
✅ `evaluate(a, b) => {...}, a, b)`
2022-06-23 09:29:46 +00:00
return result ;
2019-01-15 04:34:50 +00:00
}
2020-06-22 15:21:57 +00:00
/ * *
* The method evaluates the XPath expression relative to the elementHandle .
* If there are no such elements , the method will resolve to an empty array .
* @param expression - Expression to { @link https : //developer.mozilla.org/en-US/docs/Web/API/Document/evaluate | evaluate}
* /
2020-04-21 11:11:06 +00:00
async $x ( expression : string ) : Promise < ElementHandle [ ] > {
feat!: type inference for evaluation types (#8547)
This PR greatly improves the types within Puppeteer:
- **Almost everything** is auto-deduced.
- Parameters don't need to be specified in the function. They are deduced from the spread.
- Return types don't need to be specified. They are deduced from the function. (More on this below)
- Selections based on tag names correctly deduce element type, similar to TypeScript's mechanism for `getElementByTagName`.
- [**BREAKING CHANGE**] We've removed the ability to declare return types in type arguments for the following reasons:
1. Setting them will indubitably break auto-deduction.
2. You can just use `as ...` in TypeScript to coerce the correct type (given it makes sense).
- [**BREAKING CHANGE**] `waitFor` is officially gone.
To migrate to these changes, there are only four things you may need to change:
- If you set a return type using the `ReturnType` type parameter, remove it and use `as ...` and `HandleFor` (if necessary).
⛔ `evaluate<ReturnType>(a: number, b: number) => {...}, a, b)`
✅ `(await evaluate(a, b) => {...}, a, b)) as ReturnType`
⛔ `evaluateHandle<ReturnType>(a: number, b: number) => {...}, a, b)`
✅ `(await evaluateHandle(a, b) => {...}, a, b)) as HandleFor<ReturnType>`
- If you set any type parameters in the *parameters* of an evaluation function, remove them.
⛔ `evaluate(a: number, b: number) => {...}, a, b)`
✅ `evaluate(a, b) => {...}, a, b)`
- If you set any type parameters in the method's declaration, remove them.
⛔ `evaluate<(a: number, b: number) => void>((a, b) => {...}, a, b)`
✅ `evaluate(a, b) => {...}, a, b)`
2022-06-23 09:29:46 +00:00
const arrayHandle = await this . evaluateHandle ( ( element , expression ) = > {
const document = element . ownerDocument || element ;
const iterator = document . evaluate (
expression ,
element ,
null ,
XPathResult . ORDERED_NODE_ITERATOR_TYPE
) ;
const array = [ ] ;
let item ;
while ( ( item = iterator . iterateNext ( ) ) ) {
array . push ( item ) ;
}
return array ;
} , expression ) ;
2019-01-15 04:34:50 +00:00
const properties = await arrayHandle . getProperties ( ) ;
await arrayHandle . dispose ( ) ;
const result = [ ] ;
for ( const property of properties . values ( ) ) {
const elementHandle = property . asElement ( ) ;
2022-06-14 11:55:35 +00:00
if ( elementHandle ) {
result . push ( elementHandle ) ;
}
2019-01-15 04:34:50 +00:00
}
return result ;
}
2020-06-22 15:21:57 +00:00
/ * *
* Resolves to true if the element is visible in the current viewport .
* /
2021-09-15 20:56:50 +00:00
async isIntersectingViewport ( options ? : {
threshold? : number ;
} ) : Promise < boolean > {
feat!: type inference for evaluation types (#8547)
This PR greatly improves the types within Puppeteer:
- **Almost everything** is auto-deduced.
- Parameters don't need to be specified in the function. They are deduced from the spread.
- Return types don't need to be specified. They are deduced from the function. (More on this below)
- Selections based on tag names correctly deduce element type, similar to TypeScript's mechanism for `getElementByTagName`.
- [**BREAKING CHANGE**] We've removed the ability to declare return types in type arguments for the following reasons:
1. Setting them will indubitably break auto-deduction.
2. You can just use `as ...` in TypeScript to coerce the correct type (given it makes sense).
- [**BREAKING CHANGE**] `waitFor` is officially gone.
To migrate to these changes, there are only four things you may need to change:
- If you set a return type using the `ReturnType` type parameter, remove it and use `as ...` and `HandleFor` (if necessary).
⛔ `evaluate<ReturnType>(a: number, b: number) => {...}, a, b)`
✅ `(await evaluate(a, b) => {...}, a, b)) as ReturnType`
⛔ `evaluateHandle<ReturnType>(a: number, b: number) => {...}, a, b)`
✅ `(await evaluateHandle(a, b) => {...}, a, b)) as HandleFor<ReturnType>`
- If you set any type parameters in the *parameters* of an evaluation function, remove them.
⛔ `evaluate(a: number, b: number) => {...}, a, b)`
✅ `evaluate(a, b) => {...}, a, b)`
- If you set any type parameters in the method's declaration, remove them.
⛔ `evaluate<(a: number, b: number) => void>((a, b) => {...}, a, b)`
✅ `evaluate(a, b) => {...}, a, b)`
2022-06-23 09:29:46 +00:00
const { threshold = 0 } = options ? ? { } ;
return await this . evaluate ( async ( element , threshold ) = > {
2022-06-22 13:25:44 +00:00
const visibleRatio = await new Promise < number > ( resolve = > {
const observer = new IntersectionObserver ( entries = > {
2022-05-31 14:34:16 +00:00
resolve ( entries [ 0 ] ! . intersectionRatio ) ;
2021-09-15 20:56:50 +00:00
observer . disconnect ( ) ;
2019-01-15 04:34:50 +00:00
} ) ;
2021-09-15 20:56:50 +00:00
observer . observe ( element ) ;
} ) ;
return threshold === 1 ? visibleRatio === 1 : visibleRatio > threshold ;
} , threshold ) ;
2019-01-15 04:34:50 +00:00
}
}
2021-09-20 09:01:32 +00:00
/ * *
* @public
* /
export interface Offset {
/ * *
* x - offset for the clickable point relative to the top - left corder of the border box .
* /
x : number ;
/ * *
* y - offset for the clickable point relative to the top - left corder of the border box .
* /
y : number ;
}
2020-06-22 15:21:57 +00:00
/ * *
* @public
* /
export interface ClickOptions {
/ * *
* Time to wait between ` mousedown ` and ` mouseup ` in milliseconds .
*
* @defaultValue 0
* /
delay? : number ;
/ * *
* @defaultValue 'left'
* /
2022-04-27 21:00:07 +00:00
button? : MouseButton ;
2020-06-22 15:21:57 +00:00
/ * *
* @defaultValue 1
* /
clickCount? : number ;
2021-09-20 09:01:32 +00:00
/ * *
* Offset for the clickable point relative to the top - left corder of the border box .
* /
offset? : Offset ;
2020-06-22 15:21:57 +00:00
}
/ * *
* @public
* /
export interface PressOptions {
/ * *
* Time to wait between ` keydown ` and ` keyup ` in milliseconds . Defaults to 0 .
* /
delay? : number ;
/ * *
* If specified , generates an input event with this text .
* /
text? : string ;
}
2021-06-04 10:25:36 +00:00
/ * *
* @public
* /
export interface Point {
x : number ;
y : number ;
}
2022-05-31 14:34:16 +00:00
function computeQuadArea ( quad : Point [ ] ) : number {
2021-05-26 14:37:38 +00:00
/ * C o m p u t e s u m o f a l l d i r e c t e d a r e a s o f a d j a c e n t t r i a n g l e s
2022-06-09 11:27:34 +00:00
https : //en.wikipedia.org/wiki/Polygon#Simple_polygons
* /
2019-01-15 04:34:50 +00:00
let area = 0 ;
for ( let i = 0 ; i < quad . length ; ++ i ) {
2022-05-31 14:34:16 +00:00
const p1 = quad [ i ] ! ;
const p2 = quad [ ( i + 1 ) % quad . length ] ! ;
2019-01-15 04:34:50 +00:00
area += ( p1 . x * p2 . y - p2 . x * p1 . y ) / 2 ;
}
return Math . abs ( area ) ;
}