There's another one I can't find, but it writes out things like "user moved mouse to x,y. User has been idle for 10 seconds, page lost focus, page gained focus" .. kinda creepy how much is available to the Javascript engine.
And thanks for the new novelty website bookmark :D
Clickable link
>No plugins detected.
Interesting. I have 6 installed on Firefox.
I mean, it's not like every desktop application you've ever used in your life couldn't do the same or more?
I think that it would be a better comparison between a pdf file and the web: pdfs files can't do the same or more.
And I would argue it is harder for the average user to view the JavaScript inside PDFs: on the web just right click and choose Inspect Element right in the browser; for a PDF you'll have to use specialized tools to decode the myriad encoding schemes inside a PDF. The average JavaScript developer doesn't know how to extract JavaScript from a PDF.
My point still stands: I do not expect a pdf document to be able to do anything like the djsumdog's link and neither do most people. If a pdf document was able to do anything like that I would consider that viewer as broken.
> The average JavaScript developer doesn't know how to extract JavaScript from a PDF.
They could learn with a few google searches.
Is the "you" in this scenario Richard Stallman?
The easy check for this would be to see whether opening the devtools in detached mode via the menus makes it notice.
Note that this would actually be quite a pain to hide from the page, just because it's something the page needs to know to display some stuff and make rendering calculations. If it was hidden from the page, we'd suddenly be complaining about debugging floating footers which are hiding under the devtools.
document.addEventListener('keydown', ({ keyCode }) => console.log(keyCode))
91
16
73
You can see each key.
The person who figured this out probably opened them via menu and had dev tools in another window, so the evil folks couldn't detect the resize.