Hacker News Reader

From the article:

> Instead, Firefox offers an individual pdfjs.enableScripting preference that can be configured from the about:flags page.

As a long time FF user I have never heard of about:flags and it does not work either. about:config contains the setting like a million of other ones that no ordinary mortal can ever manage.

Just a mistake in TFA or am I missing something?

View on HN

Chromium has chrome://flags, that's probably where the confusion came from.

Probably an error on a GPT generated article :)

Unless they were using a highly quantized local language model, it seems more like a human error than a GPT error.

But it got wrong both entities (the config address and the setting name). It feels like an LLM error on writing based on short high levels descriptions of sections.

Reply on news.ycombinator.com