![]() On Win and Linux, Ctrl-A is handled by Chrome, and puppeteer does emulate this. Puppeteer doesn't emulate native shortcuts because native shortcuts depend on the active window, which is out of control for puppeteer. When you install Puppeteer, it downloads a recent version of Chromium (170MB Mac, 282MB Linux, 280MB Win) that is guaranteed to work with the API. On the other hand, these bits on suggest that Ctrl-F should work:įor finer control, you can use keyboard.down, keyboard.up, and ndCharacter to manually fire events as if they were generated from a real keyboard. Generally the home directory is well-defined (even on Windows), but occasionally the home directory may not be available. Teach puppeteer new tricks through plugins. ![]() Contribute to berstend/puppeteer-extra development by creating an account on GitHub. On the one hand, I see that the basic idea is dispathing a key event to the page. Puppeteer doesn't emulate native shortcuts because native shortcuts depend on the active window, which is out of control for puppeteer. Starting from v19.0.0, Puppeteer will download browsers into /.cache/puppeteer using os.homedir for better caching between Puppeteer upgrades. VDOMDHTMLCTYPE html> GitHub - berstend/puppeteer-extra: Teach puppeteer new tricks through plugins. Const puppeteer = require ( 'puppeteer' ) ( async ( ) => ) ( ) Īnyway, it would be interesting to hear on the page.keyboard.* issue. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |