Skip to content
This repository has been archived by the owner on Nov 24, 2018. It is now read-only.

Support for setFileInput() over Proxy #186

Open
3 tasks
adieuadieu opened this issue Aug 6, 2017 · 2 comments
Open
3 tasks

Support for setFileInput() over Proxy #186

adieuadieu opened this issue Aug 6, 2017 · 2 comments

Comments

@adieuadieu
Copy link
Collaborator

adieuadieu commented Aug 6, 2017

setFileInput() was implemented in #170. However, the setFileInput() does not currently work over the Proxy as expected because files are not transmitted from the local Chromeless instance to the Proxy (something which may be difficult given the AWS IoT 128KB message size limit.)

This issue tracks progress on supporting the Proxy.

Acceptance Criteria

  • Add support to setFileInput() for S3 paths (which means fetching the S3 file, then passing the local disk path from the resulting object to setFileInput()
  • Add support to setFileInput() for URLs
  • if a local file path is provided to setFileInput() we will try to upload it to S3, then pass the S3 path to the Proxy.
await chromeless.selectFile('.uploader', [
  's3://my-bucket/my/object/prefix/file.jpg',
  'http://sweet-site.cool/my-image.jpg'
])
@timbaileyjones
Copy link

Hi @adieuadieu - I find myself needing this feature to feed a file to an element in Chrome on AWS Lambda. Any progress?

@adieuadieu
Copy link
Collaborator Author

@timbaileyjones no progress. See if puppeteer addresses your needs. You can run puppeteer together with serverless-chrome. Here is an article describing how.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants