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

TabPanel: props can not be kebab-case #5338

Open
Anubarak opened this issue Feb 26, 2024 · 0 comments · May be fixed by #5546
Open

TabPanel: props can not be kebab-case #5338

Anubarak opened this issue Feb 26, 2024 · 0 comments · May be fixed by #5546
Labels
Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible

Comments

@Anubarak
Copy link

Anubarak commented Feb 26, 2024

Describe the bug

As Like this one
#1263

Some props like content-class or content-style still cannot be kebab-case and must be camelCase.

<TabView>
  <!-- does not work -->
  <TabPanel
	content-style="background: red"
	content-class="some-class"
	header="Header I">
	<p class="m-0">styling and class are ignored</p>
  </TabPanel>
  
  <!-- works -->
  <TabPanel
	contentStyle="background: red"
	contentClass="some-class"
	header="Header II">
	  <p class="m-0">styling works</p>
  </TabPanel>

</TabView>

Reproducer

https://stackblitz.com/edit/scv6yh?file=src%2FApp.vue

PrimeVue version

3.49.1

Vue version

3.x

Language

TypeScript

Build / Runtime

Vite

Browser(s)

No response

Steps to reproduce the behavior

See props on the first TabPanel and on the second TabPanel.
CamelCase Props work (2nd), kebab-case do not work (1st)

Expected behavior

Both should work as per Vue rules

@Anubarak Anubarak added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Feb 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant