Open Bug 1158435 Opened 5 years ago Updated 1 year ago
input type number spin buttons on Windows Server 2012 R2 render issue
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:37.0) Gecko/20100101 Firefox/37.0 Build ID: 20150402191859 Steps to reproduce: - create a simple HTML5 page - add a single, unstyled input type number HTML element - load the page in Firefox running on Windows Server 2012 R2 Actual results: - the spin buttons to increase/decrease the number value is rendered as a 4px high bar --> see attached image Expected results: - the spin buttons should be rendered properly as on any other system
Please provide the following information: 1. Type about:support into the address bar and press Enter. 2. Copy the entire Graphics section to the clipboard, then paste it in a comment here. 3. Is there any difference when you toggle hardware acceleration then restart Firefox? https://support.mozilla.org/en-US/kb/advanced-panel-accessibility-browsing-network-upda#w_general-tab
Component: Untriaged → Layout: Form Controls
Product: Firefox → Core
Graphics Adapter Description VirtualBox Graphics Adapter for Windows 8 Adapter Drivers VBoxDispD3D Adapter RAM 0 Device ID 0xbeef Direct2D Enabled Blocked for your graphics card because of unresolved driver issues. DirectWrite Enabled false (6.3.9600.16384) Driver Date 4-14-2015 Driver Version 188.8.131.52 GPU #2 Active false GPU Accelerated Windows 1/1 Direct3D 11 (OMTC) Subsys ID 00000000 Vendor ID 0x80ee WebGL Renderer Blocked for your graphics card because of unresolved driver issues. windowLayerManagerRemote true AzureCanvasBackend skia AzureContentBackend cairo AzureFallbackCanvasBackend cairo AzureSkiaAccelerated 0 --- Additional info: - this bug is not related to VirtualBox. It also happens in other VM environments like VMware. - GUI hardware accelartion is not possible in this specific VM, I'll post additional comments from a VM with HW acceleration
More on HW acceleration in VMs: it seems that FF is black-listing most or all virtual graphic adapters (at least the ones in VirtualBox and Parallels) even if 2D and 3D acceleration is enabled for the VM and is available in the Windows installation. Force-enabling Direct2D via about:config leads to a FF crash on application start. The problem does not appear in a Windows 7 VM (VirtualBox and Parallels), though even here FF blacklists the graphic adapter (only in German this time, but the longer messages are the same as above): Direct2D aktiviert Wurde auf Grund Ihrer Grafikkarte blockiert, da ungelöste Treiberprobleme bestehen. DirectWrite aktiviert false (6.2.9200.16571) Geräte-ID 0x4005 GPU #2 aktiv false GPU-beschleunigte Fenster 0/1 Basic Wurde auf Grund Ihrer Grafikkarte blockiert, da ungelöste Treiberprobleme bestehen. Karten-Beschreibung Parallels Display Adapter (WDDM) Karten-RAM Unknown Karten-Treiber prl_umdd prl_umdd10 Treiber-Datum 3-26-2015 Treiber-Version 10.2.28956.0 Vendor-ID 0x1ab8 WebGL-Renderer Wurde auf Grund Ihrer Grafikkarte blockiert, da ungelöste Treiberprobleme bestehen. windowLayerManagerRemote false AzureCanvasBackend skia AzureContentBackend cairo AzureFallbackCanvasBackend cairo AzureSkiaAccelerated 0
Main differences between a working and non-working FF environment from a about:support view: - windowLayerManagerRemote (false on W7=works, true on W2012=non-working) - different device and vendor ID (0x4005 vs. 0xbeef)
(In reply to Hendrik Brandt from comment #3) > - this bug is not related to VirtualBox. It also happens in other VM > environments like VMware. But is it unique to running in a VM? Is the rendering correct when running under Windows Server 2012 that is not in a VM?
FWIW the rendering is fine for me in Windows 8.1 running under VMware.
We are experiencing this bug on Windows 2012 r2 on a Vmware VM.
The screenshot here is exactly what I see in bug 1287681 on Windows 10 (x64) on an actual machine. So it is not specific to VM-ware, or Windows Server 2012. My DPI setting is 100% so it is not specific to high-DPI either. What might be significant in my case is that I upgraded from Windows 7 (Home), and had set the theme to 'Windows Classic' before upgrading.
Same issue here on Win10, not on high-DPI.
You need to log in before you can comment on or make changes to this bug.