blog:http content is usually dynamically managed via asynchronous requests.
Your best bet is to use the Network tab and filter the actual request made by the browser when it tries to expand the resource.
fabio
joined 4 months ago
blog:http content is usually dynamically managed via asynchronous requests.
Your best bet is to use the Network tab and filter the actual request made by the browser when it tries to expand the resource.
The closest thing I know (but it only works in the browser) is the Firenvim extension