schickling/chromeless

Why after waitiing, the 'click' is undefined

Open

#215 opened on Aug 10, 2017

View on GitHub
 (2 comments) (0 reactions) (0 assignees)TypeScript (13,240 stars) (606 forks)batch import
discussionenhancementhelp wantedquestion

Description

const { Chromeless } = require('chromeless')
async function run() {
  const chromeless = new Chromeless()

  const screenshot = await chromeless
    .goto('https://www.google.com')
    .wait('div[data-type="planName"]')
    .click('div[data-type="planName"]') //after wait(), 'click' is undefined
    .screenshot()

  console.log(screenshot) 
  await chromeless.end()
}

run().catch(console.error.bind(console))

the error message: (node:10204) UnhandledPromiseRejectionWarning: Unhandled promise rejection (reje ction id: 1): Error: TypeError: Cannot read property 'click' of undefined at expressionResult (:8:17) at :9:11 at :15:7

Why after waitiing, the 'click 'is undefined? I often encounter this situation.

Contributor guide

Tech stack
typescriptjavascriptnodejs
Domain
testing
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
JavaScriptasync/awaitChromeless basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
The issue reports that after calling `.wait()`, the subsequent `.click()` method is undefined. This suggests a potential chaining issue in the Chromeless API. First, review the Chromeless documentation and source code (e.g., the class definition in `src/`) to verify whether `wait()` returns a Chainable instance or a Promise that resolves to a different type. Check the existing issue comments for any maintainer responses or user workarounds. Also, look at related issues or PRs that might address method chaining. The goal is to determine whether this is a user error or a library bug, and if the library handles promise chaining correctly.