This Page Is a Quine (2021)

The trick is `* {display:block;}`. Having learned that, I wondered whether https://secretgeek.github.io/html_wysiwyg/html.html used the same trick. So I opened up the page and Ctrl+F'ed for "display:". Nothing came up! Back to https://pranavg.me/ and Ctrl+F'ed for "display". Nothing came up!

Apparently, at least on Chrome, Ctrl+F will not find text inside a block, no matter whether it's displayed or not.

Ctrl+F works even to find text inside the displayed and elements, but not inside the displayed element. What could be the browser-writer's rationale for this? And are there any other HTML elements that "suppress searching" like this?

Re: This Page Is a Quine (2021)

#9

Post by _ache_ » Wed, Sep 03, 2025, 9:15 PM UTC

omoikane wrote: post #5

> This page works on all browsers But on Lynx, it's rendered as only a plain page without all the CSS style bits to make it quine.

I suspect Lynx isn't very sophisticated because I just tried with curl and it works like a charm.

Re: This Page Is a Quine (2021)

#10

Post by sltkr » Wed, Sep 03, 2025, 11:36 PM UTC

quuxplusone wrote: post #8

The trick is `* {display:block;}`. Having learned that, I wondered whether https://secretgeek.github.io/html_wysiwyg/html.html used the same trick. So I opened up the page and Ctrl+F'ed for "display:". Nothing came up! Back to https://pranavg.me/ and Ctrl+F'ed for "display". Nothing came up! Apparently, at least on Chrome, Ctrl+F will not find text inside a block, no matter whether it's displayed or not. Ctrl+F works…

Curious.

Interesting enough, document.body.innerText does contain the style sheet contents, so the browser does consider it visible text in some sense.