search

microsoftgraph / microsoft-graph-explorer-v4

React/Redux version of Graph Explorer used to learn the Microsoft Graph Api
https://developer.microsoft.com/graph/graph-explorer
MIT License
202 stars 84 forks source link

NPS survey cropped on Chrome #1988

Open RabebOthmani opened 1 year ago

RabebOthmani commented 1 year ago

The NPS survey is cropped on Chrome. My machine is ThinkPad X1. The same issue was reported from Surface users.

NPS survey on chrome
RabebOthmani commented 1 year ago

Potentially related to https://github.com/microsoftgraph/microsoft-graph-explorer-v4/issues/1412 The recommendation from the UX team is to use 1873W x 947H

ElinorW commented 1 year ago

@RabebOthmani upon investigation, @MaryannGitonga and I have realized this is mostly affected on devices where the display settings, specifically the scale setting is at 200% and the browser zoom is at 100%. Referencing this comment https://github.com/microsoftgraph/microsoft-graph-explorer-v4/issues/1524#issuecomment-1204245723 by @gavinbarron, I think we may need to wait on the telemetry, especially if we are able to capture the device scale used.

Furthermore, with the CSS settings provided by OCV none of them solve this which leads me to believe the form hasn't been designed with device scale settings in mind. I shall raise this issue with OCV and get back with their response.

ElinorW commented 1 year ago

The OCV team has created a ticket to fix this here https://office.visualstudio.com/CLE/_workitems/edit/6485875

ElinorW commented 1 year ago

This issue is similar to #1987

gavinbarron commented 1 year ago

I'd suggest that we close #1987 as a duplicate of this item.

RabebOthmani commented 1 year ago

@ElinorW where are we on this? It is still happening. It was also reported by external users. This has a big impact on users, the NPS/CES scores and feedback we receive as well as our brand. According to the data, the most used browser with GE is Chrome.

ElinorW commented 1 year ago

@RabebOthmani yeah, the OCV team is working on it... Once they fix it on their end, I'll know if there's anything I need to do on the GE end. The issue is present on both Chrome and Edge... One fix should cover both browser cases