Numbered pages
Fyre looks for a next control by role, label and position. If it finds one, following it is reliable and fast. Set a page cap and a delay; 800 ms between pages is a reasonable starting point for a site you do not own.
If the site uses a URL pattern instead — ?page=2 — you can supply the pattern directly and Fyre will generate the range rather than clicking.
Load more
The button is clicked repeatedly until it disappears, becomes disabled, or stops adding rows. That last condition matters: plenty of sites leave the button in place forever and simply return nothing after a certain depth. Fyre stops after two consecutive clicks that add no rows.
Infinite scroll
Scrolling is driven in steps with a settle period after each one, waiting for network activity to quiet down before measuring whether new rows appeared. The default settle is 1,200 ms. Raise it for image-heavy pages and lower it for text lists.
Watch for virtualised lists — containers that remove rows from the DOM as you scroll past them. Fyre captures rows as they appear rather than at the end, so these work, but the total will not match the DOM node count at any single moment.
Knowing when to stop
Always set a cap. An uncapped run against a site with a cyclic paginator will happily go forever. The cap is a page count, not a row count, so a page that returns 500 rows still counts as one.