[css-pseudo-4] The browser cannot search the content, is it intentional?

[zhangenming]

• please tag the issue title with the spec's shortname, like [css-foo]
  (this is the name from the spec URL, without a level number unless the issue is specific to that level).
  If you're proposing a new feature that doesn't obviously fit in an existing spec, skip this part — don't make something up.

• please be specific (in the title and issue) about what you want to change:
  “make it better” means different things to different people!
  

• please link to the spec section you're talking about, or at least the spec

[fantasai]

sigh No, it's not intentional. Generated content is supposed to be searchable, but it doesn't work properly in Chrome and Safari. Firefox gets this right, though. We could maybe change the spec generator to include the labels inline, but it would be better if browsers just fixed this. :) CC @chrishtr @tabatkins

[chrishtr]

I filed crbug.com/1222857 and will follow up.

[emilio]

Fwiw Firefox does this since https://bugzilla.mozilla.org/show_bug.cgi?id=1627643

[jyasskin]

@emilio Are you sure this works in Firefox? Searching for "<meta>" in https://wicg.github.io/client-hints-infrastructure/#delegate-ch-algo (from the bikeshed bug) doesn't find anything. Searching for "<" does find the generated content, but that's not useful without including its surroundings.

[emilio]

@jyasskin the fact that we can't create a selection spanning pseudo and non-pseudo content is a known issue. The current thing is useful tho, see OP for a case which does work in Firefox.