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

[BUG] - Prop autoCapitalize did not match. Server: "none" Client: "off" #3297

Closed
EnricoElias opened this issue Jun 21, 2024 · 3 comments · Fixed by #3376
Closed

[BUG] - Prop autoCapitalize did not match. Server: "none" Client: "off" #3297

EnricoElias opened this issue Jun 21, 2024 · 3 comments · Fixed by #3376
Assignees

Comments

@EnricoElias
Copy link

NextUI Version

"@nextui-org/date-picker": "^2.1.2", "@nextui-org/react": "^2.4.2",

Describe the bug

I am using the DateRangePicker component in my nextjs project like this:

<DateRangePicker
                label="label"
                value={dateRange}
                onChange={handleChange}
                className="max-w-xs"
                visibleMonths={2}
/>

In my browser console, there is this error:

 Prop `autoCapitalize` did not match. Server: "none" Client: "off"
div
DateInputSegment@webpack-internal:///(app-pages-browser)/./node_modules/@nextui-org/date-input/dist/chunk-4HVI6SVI.mjs:18:64
div
DateRangePickerField@webpack-internal:///(app-pages-browser)/./node_modules/@nextui-org/date-picker/dist/chunk-73TKHF55.mjs:28:90
div
div
div
_c<@webpack-internal:///(app-pages-browser)/./node_modules/@nextui-org/date-input/dist/chunk-YVBCSFY6.mjs:17:288
DateRangePicker@webpack-internal:///(app-pages-browser)/./node_modules/@nextui-org/date-picker/dist/chunk-GTKUT4FT.mjs:33:457

Your Example Website or App

No response

Steps to Reproduce the Bug or Issue

  1. Create nextjs App
  2. Import DateRangePicker
  3. Use the component
  4. Look in your browser console

Expected behavior

No error

Screenshots or Videos

No response

Operating System Version

Windows 10

Browser

Firefox

Copy link

linear bot commented Jun 21, 2024

@wingkwong
Copy link
Member

I couldn't reproduce the issue. please share a minimal reproducible project for investigation.

@ryo-manba
Copy link
Member

It might be an issue with react-aria.
adobe/react-spectrum#5599

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants