-
Notifications
You must be signed in to change notification settings - Fork 200
Description
This is new in 1.4, and only happens in CPU render mode.
1.) Build the sample browser in CPU render mode, via the following line after declaring the "Settings settings;" line in Browser.cpp:
settings.force_cpu_renderer = true;
2.) Open the attached "Highlight_bug.htm" in the sample browser.
3.) Select all or part of the word "test".
4.) Tab to the input field (do not click).
Bug: The highlight remains on the word "test", but it is a repaint failure. If you start dragging within "test" it will begin disappearing.
In the sample browser, typing in the input field corrects the problem. But in my actual app with the full content, typing does not help.
The problem is very dependent on the layout of the page. The only style in the example file which is not necessarily required for the bug is the margin-top, but that is needed so the text is visible below the input field. For example, using a smaller padding-left will prevent it. Both width styles are required, but using smaller values or px values does not make a difference.
The "test" text does not need to be in a div, but that avoids the selection extending to the entire page body.