This works but we might want to leave the prompts in the code and just make them unselectable using CSS, see NixOS/nix#3741

The accessbility implications (if any) would need to be checked for which is preferrable between a CSS-derived prefix, or disabling selection via CSS.

A quasi-accessibility issue that exists with CSS-derived content is that user agents without CSS may not get that content. E.g. some crawlers, or more importantly, text-based (console) browsers.

Yeah, that was my concern as well. For regular browsers, ::before should be seen be screen readers IIRC. (Edit: Yup)

Yes, I wonder if there are other accessibility issues. Accessibility is hard!

Though I know that changing the contents via CSS is fraught with perils for some user agents. You're ending up losing some of the context. I'm thinking the most likely problematic user-agent (for the home page) would not be text browsers, but crawlers making "answer" based boxes. Though, in the manuals, definitely text-based browsers would end up losing context.

Additionally, changing the contents via CSS in cases like here pushes too much knowledge about the contents into the semantics, and then the presentation layer. It's not really wrong, but it's not exactly neat either.

I'm curious to hear opinions of others about that.

Opened #492, which is IMHO a better approach. The prompt is part of the screen just like the command or the output.

Opened #490, which is IMHO a better approach. The prompt is part of the screen just like the command or the output.

Or #492? :)

(I got confused when following the link.)