Sometimes search and replace bar have no anti-aliasing

[akiirui]

Sometimes, search and replace bar not have anti-aliasing:

Normal situation:

• VSCode Version: 1.40.2
• OS Version: Arch Linux
• Desktop environment: GNOME 3.34 with text-scaling-factor 1.5

Steps to Reproduce:

1. New file
2. Ctrl + F or Ctrl + H

Does this issue occur when all extensions are disabled?
Yes

Also test on insiders build 1574746489, same as 1.40.2.
Only happens after 1.40 update

[roblourens]

Can you try this in Insiders? We have made some antialiasing improvements this month.

[akiirui]

Also test on insiders build 1574746489, same as 1.40.2.
Only happens after 1.40 update

@roblourens Yes, I have try in latest Insiders build:

• Version: 1.41.0-insider
• Commit: a8158ae
• Date: 2019-11-26T21:17:16.825Z
• Electron: 6.1.5
• Chrome: 76.0.3809.146
• Node.js: 12.4.0
• V8: 7.6.303.31-electron.0
• OS: Linux x64 5.4.0-arch1-1

Same as stable 1.40.2:

[roblourens]

Can you check other input elements, like in the search viewlet, to see if they show the same thing? This is just a <textarea> with the placeholder attribute, and I don't think there's much I can do...

[akiirui]

@roblourens Thanks for reply.

Can you check other input elements, like in the search viewlet, to see if they show the same thing?

Only div.editor-widget.find-widget have this issue.

More infomations:

Item

Value

GPU Status

2d_canvas: enabled flash_3d: enabled flash_stage3d: enabled flash_stage3d_baseline: enabled gpu_compositing: enabled metal: disabled_off multiple_raster_threads: enabled_on oop_rasterization: disabled_off protected_video_decode: unavailable_off rasterization: disabled_software skia_renderer: disabled_off surface_control: disabled_off surface_synchronization: enabled_on video_decode: unavailable_off viz_display_compositor: enabled_on viz_hit_test_surface_layer: disabled_off webgl: enabled webgl2: enabled

And more tests:

1.40.* with --disable-gpu

Less serious, just a little blurry:

Normal:

1.39.2 without --disable-gpu

No this issue

[akiirui]

More info:

Trigger when first time open find-widget. (or other conditions)
Fix when change to another tab.

[roblourens]

No idea, @rebornix any idea?

[rebornix]

I don't know but I'll try to reproduce this issue.

[rebornix]

Didn't reproduce by any means. @deepak1556 could you help provide guidance on this? It would be great if you can share how to set up the machine to reproduce anti aliasing related issue.