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

Styling select without div("selectnodiv" suggestion/example) #3953

Open
NXTwoThou opened this issue Dec 30, 2024 · 0 comments
Open

Styling select without div("selectnodiv" suggestion/example) #3953

NXTwoThou opened this issue Dec 30, 2024 · 0 comments

Comments

@NXTwoThou
Copy link

This is about Bulma feature suggestion.

Overview of the problem

I'm using Bulma version [1.0.3]

Description

Create another class that may be used in place of having to wrap select in a div.

`

One
Two `

During a lull, I've been tasked with seeing about updating some of our older sites that used Bulma pre-1.0.0. I've made a lot of headway, but am absolutely blocked by select needing to be in a div around a select element. These older sites are ASP.NET v4 webform style. So the asp:DropDownList controls have a single CssClass="select". This worked(somehow) for pre-1.0.0, but not working at all for 1.0.3. The smallest of these projects has 783 asp:DropDownList controls and I was authorized to mess with the css files, but not touch every part of the software.

I got around two issues with the following:

.select { font-size: var(--bulma-control-size); } .selectnodiv { @extend .select; background-color: hsl(var(--bulma-input-h),var(--bulma-input-s),calc(var(--bulma-input-background-l) + var(--bulma-input-background-l-delta))); color: hsl(var(--bulma-input-h),var(--bulma-input-s),var(--bulma-input-color-l)); border-color: var(--bulma-input-border-color); border-radius: var(--bulma-input-radius); }

I understand from reading previous issues that one of the primary reasons for wrapping in a div is so you can get icon and some additional styling. For those of us not interested in those features, it adds some additional complexity that we don't need.

Even if you don't consider this suggestion, I'm posting my work around in case someone else runs into my same issue. Hopefully they aren't having to maintain decade old code bases though.

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

No branches or pull requests

1 participant