Summary: | REGRESSION(r286955): Rendering Links during search: highlighting fails | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | enometh | ||||||
Component: | CSS | Assignee: | Carlos Garcia Campos <cgarcia> | ||||||
Status: | RESOLVED FIXED | ||||||||
Severity: | Normal | CC: | bugs-noreply, cgarcia, changseok, darin, esprehn+autocc, ews-watchlist, glenn, kondapallykalyan, mcatanzaro, ntim, pdr, simon.fraser, webkit-bug-importer | ||||||
Priority: | P2 | Keywords: | InRadar | ||||||
Version: | Other | ||||||||
Hardware: | Unspecified | ||||||||
OS: | Unspecified | ||||||||
See Also: | https://bugs.webkit.org/show_bug.cgi?id=227445 | ||||||||
Attachments: |
|
Description
enometh
2022-03-12 21:11:32 PST
This is not GTK specific, but it's more noticeable because we use white color for the selection text foreground. This regressed in r286955, because in case of text with decorations, the foreground text is rendered in the same coalesced marked text loop than the decorations and StyledMarkedText::coalesceAdjacentWithEqualDecorations() doesn't take into account the text styles. So, when we start rendering from the beginning of the line, only one style marked text is generated and the whole line is painted with the selection style (white foreground), on white background it looks like the non selected text disappears. When we start selecting from the end of the line, a single styled marked text is generated, but the selected text is painted with the non-selected style, and it becomes white once we complete the line selection. Created attachment 454695 [details]
Patch
The test is actually passing in mac, but there are a few unrelated pixel differences in the image diff, maybe because of the transparent selection background. Any idea how to avoid it in mac? Created attachment 454959 [details]
Patch
Committed r291552 (248658@trunk): <https://commits.webkit.org/248658@trunk> What did we do about the iOS failure? (In reply to Darin Adler from comment #7) > What did we do about the iOS failure? Oh, I'm sorry, I thought it was unrelated because I saw iOS failures with other patches too. Yes, I think it probably is unrelated. For the health of the project I tend to try to get these fixed rather than start ignoring them across many different patches. So I typically don’t say “I can ignore this”, but rather “Who do I need to talk to to get this fixed?’ |