Loading...
Important Notice - Forums is archived

To simplify things and help our users to be more productive, we have archived the current forum and focus our efforts on helping developers on Stack Overflow. You can post new questions on Stack Overflow or join our Discord channel.

Product icon
TUTORIAL

Vaadin lets you build secure, UX-first PWAs entirely in Java.
Free ebook & tutorial.

splitpanel splitter hiding

Narasimha Y
10 years ago Mar 24, 2012 7:09am
Mathias Clerc
10 years ago Mar 26, 2012 5:10am
Narasimha Y
10 years ago Mar 27, 2012 6:52am
Mathias Clerc
10 years ago Mar 27, 2012 7:02am
Narasimha Y
10 years ago Mar 27, 2012 7:40am
Mathias Clerc
10 years ago Mar 28, 2012 7:21am
Narasimha Y
10 years ago Mar 29, 2012 9:46am
Lucas Genzelis
10 years ago Apr 12, 2012 10:50pm
Mathias Clerc
10 years ago Apr 13, 2012 12:03am

The component may be same but the css classes attached to it are not, so the selector does not work anymore.

For the reason of the .v-app is that you need a more specific CSS selector in your theme in order to override an existing style.
For instance if in the base theme (let's say reindeer) you have :

.someClass{
  color:blue;
}

And you write in your theme :

.someClass{
  color:yellow;
}

The text will stay blue because reindeer is applied first and your selector is not any more specific than the original.

Now the base themes never use the .v-app selector and .v-app is always present in a vaadin application.
So in order not to try to guess whether or not your CSS will be applied and spend time debugging to know why only part of it was applied, I find it easier to prefix everything by .v-app.

.v-app .someClass{
  color:yellow;
}

Will make the text yellow even in the previous case.

Lucas Genzelis
10 years ago Apr 13, 2012 6:17am