Web Screenshot Plugin Issue

[1RB]

Using the Web Screenshot plugin

.yml file

name: Screenshot
on:
  schedule: [{cron: "0 0 * * 0"}]
  workflow_dispatch:
  push: {branches: ["master", "main"]}
jobs:
  web-screenshot:
    runs-on: ubuntu-latest
    permissions:
      contents: write
    steps:
      - uses: lowlighter/metrics@latest
        with:
          filename: site.screenshot.svg
          token: NOT_NEEDED

          # Options
          template: classic
          base: ""
          plugin_screenshot: yes
          plugin_screenshot_background: yes
          plugin_screenshot_selector: body
          plugin_screenshot_title: Inimicalpart.com
          plugin_screenshot_url: https://inimicalpart.com  

README.md

<img src="/site.screenshot.svg" alt="inimicalpart.com">

Expected Result

Actual Result

[lowlighter]

Hi 👋 !

It'll be fixed by 7d7e9d6 on @master/@main once the rebuild complete

The issue was that it was only listening for the "onload" event so it was taking the screenshot a bit too early.

I also added:

• feat(plugins/community/screenshot): add plugin_screenshot_viewport and plugin_screenshot_wait #1288

So if you need to change the scale of the viewport to make it a bit bigger you can easily do it by adding

plugin_screenshot.viewport: |
  {"width":500, "height":200}

Which looks like this:

[1RB]

would you mind pasting the code for

as I'm still having troubles getting it to work

Also i'm not sure if you are aware but

it seems that it didnt get deployed to @latest and maybe thats why im having trouble with getting it to work

[lowlighter]

I've used the following:

      - uses: lowlighter/metrics@master # not @latest
        with:
          token: NOT_NEEDED
          template: classic
          base: ""
          plugin_screenshot: yes
          plugin_screenshot_selector: body
          plugin_screenshot_title: Inimicalpart.com
          plugin_screenshot_url: https://inimicalpart.com
          plugin_screenshot_viewport: |
            {"width":500, "height":200}

it seems that it didnt get deployed to @latest and maybe thats why im having trouble with getting it to work

Yeah this is the intended behaviour, the @latest branch is treated as the "stable" one which only reflect the latest release (v3.29 currently).
The patches are currently only present on @master/@main branches for now, which are treated as the testing branches

So you may need to switch to one of the testing branches for now, or just wait a few weeks until v3.30 is released

Hope this isn't too confusing 😅

[1RB]

ohhh that makes perfect sense thank you so much