Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: FluentDataGrid GenerateHeaderOption.Sticky not working in Chrome on iPad #2228

Closed
kostas-infolyseis opened this issue Jun 20, 2024 · 2 comments
Labels
area:fluent-ui-web-components A FluentUI specific issue closed:not-actionable There is no action to be taken in response to this issue.

Comments

@kostas-infolyseis
Copy link

🐛 Bug Report

When viewing a FluentDataGrid with the GenerateHeader parameter set to GenerateHeaderOption.Sticky, from mobile Chrome on an iPad the column headers do not stay on top of the containing element like they suppose to.

💻 Repro or Code Sample

Visit the demo site from an iPad device with Chrome , go to https://www.fluentui-blazor.net/DataGrid and see the FluentDataGrid example in the "Remote Data" section that uses GenerateHeaderOption.Sticky. The DataGrid headers do not stay on top.

screenshot

🌍 Your Environment

  • OS & Device: iPadOS 17.5.1 on iPad 8th generation
  • Browser: Chrome 126.0.6478.108
  • .NET and Fluent UI Blazor library Version [e.g. 8.0.6 and 4.8.0]
@microsoft-github-policy-service microsoft-github-policy-service bot added the triage New issue. Needs to be looked at label Jun 20, 2024
@vnbaaij vnbaaij added area:fluent-ui-web-components A FluentUI specific issue closed:not-actionable There is no action to be taken in response to this issue. and removed triage New issue. Needs to be looked at labels Jun 20, 2024
@vnbaaij
Copy link
Collaborator

vnbaaij commented Jun 20, 2024

Hi,

We are using the Fluent UI Web Components (not developed/maintained by this team) to render the data grid elements. These undergo rigorous testing to make them as compatible as possible on the different OSes and browsers but there might always be something that does not work exactly as expected in one of those combinations.

Unfortunately, we do not have capacity, possibility (I do not have an iPad to test on for example) nor opportunity (this is an issue in a downstream component) to address all of these. While I acknowledge that this is an issue, I am going to close this as 'not planned' because of the reason mentioned. Hope you can understand.

ps. We are happy to take on community contributions. If you are capable to find what (CSS) adjustments might be needed to fix this specific case, by all means please submit a PR for it.

@vnbaaij vnbaaij closed this as completed Jun 20, 2024
@kostas-infolyseis
Copy link
Author

@vnbaaij Thank you very much for taking the time to answer, I do understand and I appreciate the work you are doing. I will work on it a little bit more, as we use this component in our products, and as you said I will submit a PR once I have a solid solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:fluent-ui-web-components A FluentUI specific issue closed:not-actionable There is no action to be taken in response to this issue.
Projects
None yet
Development

No branches or pull requests

2 participants