Fluentui: [DetailsRow] `NaN` is an invalid value for the `width` css style property.

Created on 3 Jan 2018  路  4Comments  路  Source: microsoft/fluentui

Bug Report

  • __Package version(s)__: 5.36.0
  • __Browser and OS versions__: Chrome, El Capitan OSX

Priorities and help requested (not applicable if asking question):

Are you willing to submit a PR to fix? No

Requested priority: (Blocking, High, Normal, Low) Low

Products/sites affected: (if applicable) ---

Describe the issue:

Using DetailRow component I see warning that telling me:
Warning: NaN is an invalid value for the width css style property.
I am testing this component: https://developer.microsoft.com/en-us/fabric#/components/groupedlist and I have all the same as in the example code of this site (first or second) and I do not know what is happening that I see the warning.

When removing DetailRow component, warning disappears.
Is there something I missed ? Some prop is not provided ?

I am using React 16.2.0.

Actual behavior:

Warning appears

Expected behavior:

No warnings are displayed in the console.

If applicable, please provide a codepen repro:

Do not have one, I had problems to run it on codepen, sorry...

Type

Most helpful comment

I have the same problem.
This example produces an error at startup React Create App development mode.

All 4 comments

Hi @MaronMariusz - I don't see the warning on the example page. Could you please share a repro so we can debug what's causing this?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions to Fabric React!

Hey @MaronMariusz we appreciate the report. I've been unable to repro this both via CodePen and the Fabric examples website. Please feel free to re-open if you have a repro so that we can debug. From the error message it seems like your instance (somehow) was passing a non-numeric value for the width style property. Since I can't repro it seems like its an implementation issue until confirmed otherwise.

I have the same problem.
This example produces an error at startup React Create App development mode.

Was this page helpful?
0 / 5 - 0 ratings