schickling/chromeless

Listening to instance events

Open

#257 opened on Aug 22, 2017

View on GitHub
 (1 comment) (3 reactions) (0 assignees)TypeScript (13,240 stars) (606 forks)batch import
APIfeaturehelp wanted

Description

With nightmare.js it is possible to add an event listener, for example:

function onResponseDetails(event, status, newURL, originalURL, httpResponseCode, requestMethod, referrer, headers, resourceType) {
    if (httpResponseCode === 200) {
        if (resourceType === 'stylesheet') { stylesheets.push(newURL); }
        if (resourceType === 'image') { images.push(newURL);}
    }
  }

nightmare.on('did-get-response-details', onResponseDetails)

I think it's actually a electron feature https://electron.atom.io/docs/api/web-contents/#instance-events.

Anyway, I humbly request similar functionality to be added to chromeless. (Perhaps there is a way already?)

Thank you for your time!

Contributor guide

Tech stack
typescriptelectron
Domain
backend
Issue type
feature
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.
half day
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.
mostly clear
Prerequisites
Basic knowledge of Electron eventsFamiliarity with chromeless API
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Investigate Electron's web contents instance events (https://electron.atom.io/docs/api/web contents/#instance events) and study how nightmare.js implements its .on() method. Review chromeless source code for existing event handling patterns and propose a minimal implementation that exposes a similar .on() method on chromeless instances. Ensure consistency with the existing API and consider adding tests.