diff --git a/_data/Bulma.json b/_data/Bulma.json
index 4466c00a0..a4682f789 100644
--- a/_data/Bulma.json
+++ b/_data/Bulma.json
@@ -1 +1 @@
-{"Data":{"Bulma-Issues":{"Issues":[{"Id":"2770686131","IsPullRequest":false,"CreatedAt":"2025-01-06T13:40:04","Actor":"AbstractionsAs","Number":"3956","RawContent":null,"Title":"Regression from 0.9.3: Background color for menu","State":"open","Body":"<!-- PLEASE READ THE FOLLOWING INSTRUCTIONS -->\r\n\r\n<!-- Choose one of the following: -->\r\nThis is about **Bulma**.\r\n\r\n<!-- Is it about Bulma or about the Docs? -->\r\n<!-- Is it a bug/feature/question or do you need help? -->\r\n<!-- If it's a bug, is it a browser bug? -->\r\n\r\n### Overview of the problem\r\n\r\n<!-- UNCOMMENT THE APPROPRIATE LINES -->\r\n\r\nThis is about the Bulma **CSS framework**\r\n<!-- This is about the Bulma **Docs** -->\r\nI'm using Bulma **version** 1.0.2\r\n\r\n\r\n### Description\r\n\r\nIn Bulma 0.9.3, you could set the background color of a \"menu\" component, e.g. \"has-background-light\", and it would work as expected. \r\nSince Bulma 1.0, this gives silly results.\r\n\r\n\r\n","Url":"https://github.com/jgthms/bulma/issues/3956","RelatedDescription":"Open issue \"Regression from 0.9.3: Background color for menu\" (#3956)"},{"Id":"2770645702","IsPullRequest":false,"CreatedAt":"2025-01-06T13:18:34","Actor":"sogorgeousman","Number":"3955","RawContent":null,"Title":"The project looks abandoned","State":"open","Body":"Unfortunately, I and the rest of the developers have the impression that the project has been abandoned. Well, **not exactly completely, but noticeably**. Many really important Issues have been waiting for a response for several weeks, acceptable pull requests have not received any feedback.\r\n\r\n#3761\r\n#3954 \r\n#3911\r\n#3886 and many, many other things that I also came across.\r\n\r\nWhy not try to find enthusiasts who are ready to further develop opensource? Or at least post lines in the readme that the project has moved into sluggish development, so that developers do not waste their time waiting for their issues to be resolved and pull requests accepted","Url":"https://github.com/jgthms/bulma/issues/3955","RelatedDescription":"Open issue \"The project looks abandoned\" (#3955)"},{"Id":"2766074344","IsPullRequest":false,"CreatedAt":"2025-01-02T13:54:11","Actor":"AbstractionsAs","Number":"3954","RawContent":null,"Title":"Navbar colors not working after upgrade to Bulma 1.0","State":"open","Body":"<!-- PLEASE READ THE FOLLOWING INSTRUCTIONS -->\r\n\r\n<!-- Choose one of the following: -->\r\nThis is about **Bulma**.\r\n\r\n### Overview of the problem\r\n\r\nAfter upgrading from Bulma 0.9.3 to Bulma 1.0, the navbar behaves differently in two important ways as soon as you add a color:\r\n\r\n1. The \"is-active\" modifier no longer has any visual effect\r\n2. The inverted text colors behave differently. Eg. when using primary, the labels are inverted to white in Bulma 0.9.3, but are black in Bulma 1\r\n\r\n### Steps to Reproduce\r\n\r\n1. Create a navbar\r\n2. Add a few \"navbar-item\"s \r\n3. Set one \"navbar-item\" to \"is-active\"\r\n\r\nAt this point, everything seems to work\r\n\r\n4. Add a color to the navbar, e.g. \"is-primary\"\r\n\r\n### Expected behavior\r\n\r\n1. The avtive item should be styled as active\r\n2. The text should be inverted\r\n\r\n### Actual behavior\r\n\r\n1. The active item is now indistingiushable from the rest\r\n2. The text is black\r\n","Url":"https://github.com/jgthms/bulma/issues/3954","RelatedDescription":"Open issue \"Navbar colors not working after upgrade to Bulma 1.0\" (#3954)"},{"Id":"2763712207","IsPullRequest":false,"CreatedAt":"2024-12-30T21:23:18","Actor":"NXTwoThou","Number":"3953","RawContent":null,"Title":"Styling select without div(\"selectnodiv\" suggestion/example)","State":"open","Body":"This is about Bulma feature suggestion.\r\n\r\n### Overview of the problem\r\nI'm using Bulma **version** [1.0.3]\r\n\r\n### Description\r\n\r\nCreate another class that may be used in place of having to wrap select in a div.\r\n\r\n`\r\n<div class=\"select\">\r\n    <select>\r\n        <option>One</option>\r\n    </select>\r\n</div>\r\n\r\n<select class=\"selectnodiv\">\r\n    <option>Two</option>\r\n</select>\r\n`\r\n\r\nDuring 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.\r\n\r\nI got around two issues with the following:\r\n\r\n`\r\n.select {\r\n    font-size: var(--bulma-control-size);\r\n}\r\n.selectnodiv {\r\n    @extend .select;\r\n    background-color: hsl(var(--bulma-input-h),var(--bulma-input-s),calc(var(--bulma-input-background-l) + var(--bulma-input-background-l-delta)));\r\n    color: hsl(var(--bulma-input-h),var(--bulma-input-s),var(--bulma-input-color-l));\r\n    border-color: var(--bulma-input-border-color);\r\n    border-radius: var(--bulma-input-radius);\r\n}\r\n`\r\n\r\nI 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.\r\n\r\nEven 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.","Url":"https://github.com/jgthms/bulma/issues/3953","RelatedDescription":"Open issue \"Styling select without div(\"selectnodiv\" suggestion/example)\" (#3953)"},{"Id":"2759942855","IsPullRequest":true,"CreatedAt":"2024-12-26T16:32:34","Actor":"Aic-02mz","Number":"3952","RawContent":null,"Title":"Remove outdated Ruby-Sass and Node-Sass dependencies","State":"open","Body":"# Remove outdated Ruby-Sass and Node-Sass dependencies\r\n\r\nThis pull request proposes the removal of outdated dependencies, specifically Ruby-Sass and Node-Sass, to improve the overall maintainability and performance of the repository. Both dependencies are no longer actively supported and  they are both out of  date\r\n\r\nKey Changes:\r\n\r\n<img width=\"631\" alt=\"img2\" src=\"https://github.com/user-attachments/assets/c3a4471d-b9ce-4cd6-9e1d-4719ced4aab9\" />\r\n\r\n\r\n## Removed Ruby-Sass and Node-Sass files:\r\n\r\nRemoved redundant files for the Sass test folder.\r\n\r\n##  Streamlined the test directory:\r\n\r\nThe test directory now only contains Dart-Sass, reducing clutter and complexity.\r\n\r\n## Resolved Node-Sass syntax issues:\r\n\r\nAdjustments have been made to eliminate deprecated syntax.\r\n\r\n## Rationale:\r\n\r\nBoth Ruby-Sass and Node-Sass are no longer actively supported.\r\n\r\nThe repository now fully aligns with modern standards by using Dart-Sass exclusively.\r\n\r\nThis change reduces potential maintenance in the future by removing outdated tools.\r\n\r\n## Testing:\r\n\r\nThis PR primarily involves the clean-up and reorganization of files. No testing was performed, as no new functionality or features were introduced.\r\n\r\n## Before and After:\r\nThe directory now focuses solely on Dart-Sass, which is the preferred and modern standard.\r\n\r\n## Changelog:\r\nNot needed, as this is a clean-up effort.\r\n\r\n## Additional Notes:\r\nThis aligns the repository with current best practices by removing unsupported tools and ensuring a cleaner structure. \r\n\r\n","Url":"https://github.com/jgthms/bulma/pull/3952","RelatedDescription":"Open PR \"Remove outdated Ruby-Sass and Node-Sass dependencies\" (#3952)"},{"Id":"2748804806","IsPullRequest":true,"CreatedAt":"2024-12-18T21:45:11","Actor":"bagedevimo","Number":"3950","RawContent":null,"Title":"Correct the syntax in hero is-bold colour variants","State":"open","Body":"While the prior syntax does produce valid css, it's not quite valid scss and so produces warnings in various pre and post-processing pipelines which various upstream consumers of Bulma may use.\r\n\r\n<!-- PLEASE READ THE FOLLOWING INSTRUCTIONS -->\r\n<!-- DO NOT REBUILD THE CSS OUTPUT IN YOUR PR -->\r\n\r\n<!-- Choose one of the following: -->\r\nThis is a **bugfix**.\r\n\r\n### Proposed solution\r\n\r\nBy using the correct scss syntax, we just prevent downstream warnings and errors, and make this file consistent with the rest of the bulma codebase., for example:\r\n\r\n```\r\n#30 114.5 WARNING in css/partner_portal-d7c813d1.css\r\n#30 114.5 css/partner_portal-d7c813d1.css from Css Minimizer plugin\r\n#30 114.5 postcss-calc:: Lexical error on line 1: Unrecognized text.\r\n#30 114.5 \r\n#30 114.5   Erroneous area:\r\n#30 114.5 1: var(--bulma-hero-h) - $hero-gradient-h-offset\r\n#30 114.5 ^........................^ webpack://./node_modules/bulma/sass/layout/hero.scss:146:12\r\n```\r\n\r\n### Testing Done\r\n\r\nGenerated css output has no difference before and after this change.\r\n\r\n### Changelog updated?\r\n\r\nNo.\r\n","Url":"https://github.com/jgthms/bulma/pull/3950","RelatedDescription":"Open PR \"Correct the syntax in hero is-bold colour variants\" (#3950)"},{"Id":"2740700673","IsPullRequest":false,"CreatedAt":"2024-12-16T04:51:47","Actor":"shohol07","Number":"3949","RawContent":null,"Title":"reload","State":"closed","Body":"<!-- PLEASE READ THE FOLLOWING INSTRUCTIONS -->\r\n\r\n<!-- Choose one of the following: -->\r\nThis is about **Bulma | the Docs**.\r\n\r\n<!-- Is it about Bulma or about the Docs? -->\r\n<!-- Is it a bug/feature/question or do you need help? -->\r\n<!-- If it's a bug, is it a browser bug? -->\r\n\r\n### Overview of the problem\r\n\r\n<!-- UNCOMMENT THE APPROPRIATE LINES -->\r\n\r\n<!-- This is about the Bulma **CSS framework** -->\r\n<!-- This is about the Bulma **Docs** -->\r\n<!-- I'm using Bulma **version** [x.x.x] -->\r\n<!-- My **browser** is: -->\r\n<!-- This is a **Sass** issue: I'm using version [x.x.x] -->\r\n<!-- I am sure this issue is **not a duplicate**? -->\r\n\r\n### Description\r\n\r\n<!-- Description of the bug, enhancement, or question -->\r\n\r\n### Steps to Reproduce\r\n\r\n<!--\r\n1. First Step\r\n2. Second Step\r\n3. and so on...\r\n-->\r\n\r\n### Expected behavior\r\n\r\n<!-- What you expected to happen -->\r\n\r\n### Actual behavior\r\n\r\n<!-- What actually happened -->\r\n","Url":"https://github.com/jgthms/bulma/issues/3949","RelatedDescription":"Closed issue \"reload\" (#3949)"},{"Id":"2736858993","IsPullRequest":false,"CreatedAt":"2024-12-12T20:51:53","Actor":"codyburleson","Number":"3948","RawContent":null,"Title":"SASS deprecation ","State":"open","Body":"This is about **Bulma**.\r\n\r\n### Overview of the problem\r\n\r\n<!-- UNCOMMENT THE APPROPRIATE LINES -->\r\n\r\nThis is about the Bulma **CSS framework**\r\n\r\nI'm using Bulma **version** 1.0.2\r\n\r\nThis is a **Sass** issue: I'm using sass version 1.77.6\r\n\r\nThere are similar open issues related to other versions of Bulma, but this is the only one for Bulma 1.0.2\r\n\r\n### Description\r\n\r\n```\r\nDeprecation Warning: Global built-in functions are deprecated and will be removed in Dart Sass 3.0.0.\r\nUse meta.type-of instead.\r\n\r\nMore info and automated migrator: https://sass-lang.com/d/import\r\n\r\n   ╷\r\n94 │   @if type-of($color) != \"color\" {\r\n   │       ^^^^^^^^^^^^^^^\r\n   ╵\r\n    node_modules/bulma/sass/utilities/functions.scss 94:7           bulmaColorLuminance()\r\n    node_modules/bulma/sass/utilities/functions.scss 128:7          bulmaFindColorInvert()\r\n    node_modules/bulma/sass/utilities/derived-variables.scss 16:15  @forward\r\n    node_modules/bulma/sass/utilities/_index.scss 6:1               @forward\r\n    node_modules/bulma/sass/_index.scss 1:1                         @use\r\n    src/assets/styles.scss 1:1                                      root stylesheet\r\n\r\nDeprecation Warning: Global built-in functions are deprecated and will be removed in Dart Sass 3.0.0.\r\nUse color.red instead.\r\n\r\nMore info and automated migrator: https://sass-lang.com/d/import\r\n\r\n   ╷\r\n99 │     \"red\": red($color),\r\n   │            ^^^^^^^^^^^\r\n   ╵\r\n    node_modules/bulma/sass/utilities/functions.scss 99:12          bulmaColorLuminance()\r\n    node_modules/bulma/sass/utilities/functions.scss 128:7          bulmaFindColorInvert()\r\n    node_modules/bulma/sass/utilities/derived-variables.scss 16:15  @forward\r\n    node_modules/bulma/sass/utilities/_index.scss 6:1               @forward\r\n    node_modules/bulma/sass/_index.scss 1:1                         @use\r\n    src/assets/styles.scss 1:1                                      root stylesheet\r\n\r\nDeprecation Warning: red() is deprecated. Suggestion:\r\n\r\ncolor.channel($color, \"red\", $space: rgb)\r\n\r\nMore info: https://sass-lang.com/d/color-functions\r\n\r\n   ╷\r\n99 │     \"red\": red($color),\r\n   │            ^^^^^^^^^^^\r\n   ╵\r\n    node_modules/bulma/sass/utilities/functions.scss 99:12          bulmaColorLuminance()\r\n    node_modules/bulma/sass/utilities/functions.scss 128:7          bulmaFindColorInvert()\r\n    node_modules/bulma/sass/utilities/derived-variables.scss 16:15  @forward\r\n    node_modules/bulma/sass/utilities/_index.scss 6:1               @forward\r\n    node_modules/bulma/sass/_index.scss 1:1                         @use\r\n    src/assets/styles.scss 1:1                                      root stylesheet\r\n\r\nDeprecation Warning: Global built-in functions are deprecated and will be removed in Dart Sass 3.0.0.\r\nUse color.green instead.\r\n\r\nMore info and automated migrator: https://sass-lang.com/d/import\r\n\r\n    ╷\r\n100 │     \"green\": green($color),\r\n    │              ^^^^^^^^^^^^^\r\n    ╵\r\n    node_modules/bulma/sass/utilities/functions.scss 100:14         bulmaColorLuminance()\r\n    node_modules/bulma/sass/utilities/functions.scss 128:7          bulmaFindColorInvert()\r\n    node_modules/bulma/sass/utilities/derived-variables.scss 16:15  @forward\r\n    node_modules/bulma/sass/utilities/_index.scss 6:1               @forward\r\n    node_modules/bulma/sass/_index.scss 1:1                         @use\r\n    src/assets/styles.scss 1:1                                      root stylesheet\r\n\r\nDeprecation Warning: green() is deprecated. Suggestion:\r\n\r\ncolor.channel($color, \"green\", $space: rgb)\r\n\r\nMore info: https://sass-lang.com/d/color-functions\r\n\r\n    ╷\r\n100 │     \"green\": green($color),\r\n    │              ^^^^^^^^^^^^^\r\n    ╵\r\n    node_modules/bulma/sass/utilities/functions.scss 100:14         bulmaColorLuminance()\r\n    node_modules/bulma/sass/utilities/functions.scss 128:7          bulmaFindColorInvert()\r\n    node_modules/bulma/sass/utilities/derived-variables.scss 16:15  @forward\r\n    node_modules/bulma/sass/utilities/_index.scss 6:1               @forward\r\n    node_modules/bulma/sass/_index.scss 1:1                         @use\r\n    src/assets/styles.scss 1:1                                      root stylesheet\r\n\r\nDeprecation Warning: Global built-in functions are deprecated and will be removed in Dart Sass 3.0.0.\r\nUse color.blue instead.\r\n\r\nMore info and automated migrator: https://sass-lang.com/d/import\r\n\r\n    ╷\r\n101 │     \"blue\": blue($color),\r\n    │             ^^^^^^^^^^^^\r\n    ╵\r\n    node_modules/bulma/sass/utilities/functions.scss 101:13         bulmaColorLuminance()\r\n    node_modules/bulma/sass/utilities/functions.scss 128:7          bulmaFindColorInvert()\r\n    node_modules/bulma/sass/utilities/derived-variables.scss 16:15  @forward\r\n    node_modules/bulma/sass/utilities/_index.scss 6:1               @forward\r\n    node_modules/bulma/sass/_index.scss 1:1                         @use\r\n    src/assets/styles.scss 1:1                                      root stylesheet\r\n\r\nDeprecation Warning: blue() is deprecated. Suggestion:\r\n\r\ncolor.channel($color, \"blue\", $space: rgb)\r\n\r\nMore info: https://sass-lang.com/d/color-functions\r\n\r\n    ╷\r\n101 │     \"blue\": blue($color),\r\n    │             ^^^^^^^^^^^^\r\n    ╵\r\n    node_modules/bulma/sass/utilities/functions.scss 101:13         bulmaColorLuminance()\r\n    node_modules/bulma/sass/utilities/functions.scss 128:7          bulmaFindColorInvert()\r\n    node_modules/bulma/sass/utilities/derived-variables.scss 16:15  @forward\r\n    node_modules/bulma/sass/utilities/_index.scss 6:1               @forward\r\n    node_modules/bulma/sass/_index.scss 1:1                         @use\r\n    src/assets/styles.scss 1:1                                      root stylesheet\r\n\r\nDeprecation Warning: Global built-in functions are deprecated and will be removed in Dart Sass 3.0.0.\r\nUse map.merge instead.\r\n\r\nMore info and automated migrator: https://sass-lang.com/d/import\r\n\r\n    ╷\r\n115 │       $color-rgb: map-merge(\r\n    │ ┌─────────────────^\r\n116 │ │       $color-rgb,\r\n117 │ │       (\r\n118 │ │         $name: $value,\r\n119 │ │       )\r\n120 │ │     );\r\n    │ └─────^\r\n    ╵\r\n    node_modules/bulma/sass/utilities/functions.scss 115:17         bulmaColorLuminance()\r\n    node_modules/bulma/sass/utilities/functions.scss 128:7          bulmaFindColorInvert()\r\n    node_modules/bulma/sass/utilities/derived-variables.scss 16:15  @forward\r\n    node_modules/bulma/sass/utilities/_index.scss 6:1               @forward\r\n    node_modules/bulma/sass/_index.scss 1:1                         @use\r\n    src/assets/styles.scss 1:1                                      root stylesheet\r\n\r\nDeprecation Warning: red() is deprecated. Suggestion:\r\n\r\ncolor.channel($color, \"red\", $space: rgb)\r\n\r\nMore info: https://sass-lang.com/d/color-functions\r\n\r\n   ╷\r\n51 │     (red($value), green($value), blue($value)),\r\n   │      ^^^^^^^^^^^\r\n   ╵\r\n    node_modules/bulma/sass/utilities/css-variables.scss 51:6   register-rgb()\r\n    node_modules/bulma/sass/utilities/css-variables.scss 130:3  register-base-color()\r\n    node_modules/bulma/sass/utilities/css-variables.scss 135:3  generate-basic-palette()\r\n    node_modules/bulma/sass/themes/light.scss 119:7             light-theme()\r\n    node_modules/bulma/sass/themes/_index.scss 11:3             @forward\r\n    node_modules/bulma/sass/_index.scss 2:1                     @use\r\n    src/assets/styles.scss 1:1                                  root stylesheet\r\n\r\nDeprecation Warning: green() is deprecated. Suggestion:\r\n\r\ncolor.channel($color, \"green\", $space: rgb)\r\n\r\nMore info: https://sass-lang.com/d/color-functions\r\n\r\n   ╷\r\n51 │     (red($value), green($value), blue($value)),\r\n   │                   ^^^^^^^^^^^^^\r\n   ╵\r\n    node_modules/bulma/sass/utilities/css-variables.scss 51:19  register-rgb()\r\n    node_modules/bulma/sass/utilities/css-variables.scss 130:3  register-base-color()\r\n    node_modules/bulma/sass/utilities/css-variables.scss 135:3  generate-basic-palette()\r\n    node_modules/bulma/sass/themes/light.scss 119:7             light-theme()\r\n    node_modules/bulma/sass/themes/_index.scss 11:3             @forward\r\n    node_modules/bulma/sass/_index.scss 2:1                     @use\r\n    src/assets/styles.scss 1:1                                  root stylesheet\r\n\r\nWarning: 124 repetitive deprecation warnings omitted.\r\n\r\n✓ 420 modules transformed.\r\nGenerated an empty chunk: \"common/common-typescript\".\r\n```","Url":"https://github.com/jgthms/bulma/issues/3948","RelatedDescription":"Open issue \"SASS deprecation \" (#3948)"},{"Id":"2728031799","IsPullRequest":false,"CreatedAt":"2024-12-09T19:22:18","Actor":"bartrylant","Number":"3947","RawContent":null,"Title":"Add my own variable?","State":"open","Body":"I can't find this anywhere in the docs. I have lots of ecperience with old school css and I just wanted to add a new variable myself. So I went to **utilities/initial-variables.scss**, added my new variable `family-trim` (with a value).\r\n\r\nAdded\r\n```\r\n.#{iv.$helpers-prefix}family-trim {\r\n  font-family: iv.$family-trim !important;\r\n}\r\n```\r\nto **helpers/typography.scss**\r\n\r\nAnd used\r\n```\r\nh1 {\r\n   font-family: cv.getVar(\"family-trim\");\r\n}\r\n```\r\nin **elements/content.scss**\r\nand compiled with dartsass.\r\n\r\nHowever, the css inspector for my h1 element says\r\n```\r\n.content h1  {\r\n    font-family: var(--bulma-family-trim);\r\n}\r\n```\r\n\r\nbut `--bulma-family-trim` is not defined. What did I forget or what did I do wrong?","Url":"https://github.com/jgthms/bulma/issues/3947","RelatedDescription":"Open issue \"Add my own variable?\" (#3947)"},{"Id":"2717781490","IsPullRequest":true,"CreatedAt":"2024-12-04T13:40:58","Actor":"mickverm","Number":"3946","RawContent":null,"Title":"Add $duration to initial-variables","State":"open","Body":"Fixes https://github.com/jgthms/bulma/issues/3945","Url":"https://github.com/jgthms/bulma/pull/3946","RelatedDescription":"Open PR \"Add $duration to initial-variables\" (#3946)"},{"Id":"2717763736","IsPullRequest":false,"CreatedAt":"2024-12-04T13:34:28","Actor":"mickverm","Number":"3945","RawContent":null,"Title":"Add $duration to initial-variables","State":"open","Body":"<!-- PLEASE READ THE FOLLOWING INSTRUCTIONS -->\r\n\r\n<!-- Choose one of the following: -->\r\nThis is about **Bulma**.\r\n\r\n### Overview of the problem\r\n\r\nI'm using Bulma **version** 1.0.2\r\nI am sure this issue is **not a duplicate**\r\n\r\n### Description\r\n\r\nDuration is not configurable via Sass variables.","Url":"https://github.com/jgthms/bulma/issues/3945","RelatedDescription":"Open issue \"Add $duration to initial-variables\" (#3945)"},{"Id":"2715986131","IsPullRequest":false,"CreatedAt":"2024-12-03T21:12:12","Actor":"davetapley","Number":"3944","RawContent":null,"Title":"Navbar broken for certain \"grid is-col-min-...\" and viewport combinations","State":"open","Body":"<!-- PLEASE READ THE FOLLOWING INSTRUCTIONS -->\r\n\r\n<!-- Choose one of the following: -->\r\nThis is about **Bulma**.\r\n\r\n<!-- Is it about Bulma or about the Docs? -->\r\n<!-- Is it a bug/feature/question or do you need help? -->\r\n<!-- If it's a bug, is it a browser bug? -->\r\n\r\n### Overview of the problem\r\n\r\n<!-- UNCOMMENT THE APPROPRIATE LINES -->\r\n\r\nThis is about the Bulma **CSS framework**\r\n<!-- This is about the Bulma **Docs** -->\r\nI'm using Bulma **version** [1.0.2]\r\nMy **browser** is:   Chromium: 131.0.6778.85 (Official Build) (x86_64]\r\n\r\n<!-- This is a **Sass** issue: I'm using version [x.x.x] -->\r\nI am sure this issue is **not a duplicate**\r\n\r\n### Description\r\n\r\nUse devtools set to responsive and observe navbar behaves strangely when narrowing the view port below 600px.\r\n\r\n\r\n### Steps to Reproduce\r\n\r\n```html\r\n<!DOCTYPE html>\r\n<html>\r\n  <head>\r\n    <meta charset=\"utf-8\" />\r\n    <meta name=\"viewport\" content=\"width=device-width, initial-scale=1\" />\r\n    <title>Hello Bulma!</title>\r\n    <link\r\n      rel=\"stylesheet\"\r\n      href=\"https://cdn.jsdelivr.net/npm/bulma@1.0.2/css/bulma.min.css\"\r\n    />\r\n  </head>\r\n  <body>\r\n    <nav class=\"navbar\" style=\"background-color: teal\">\r\n      <span class=\"navbar-item\">Hello Bulma!</span>\r\n    </nav>\r\n    <div class=\"section\">\r\n      <div class=\"grid is-col-min-24\">\r\n        <div class=\"cell\">\r\n          <div class=\"box\">cell one</div>\r\n        </div>\r\n        <div class=\"cell\">\r\n          <div class=\"box\">cell two</div>\r\n        </div>\r\n        <div class=\"cell\">\r\n          <div class=\"box\">cell three</div>\r\n        </div>\r\n      </div>\r\n    </div>\r\n  </body>\r\n</html>\r\n\r\n```\r\n\r\n### Expected behavior\r\n\r\nNavbar covers full width of viewport:\r\n\r\n<img width=\"859\" alt=\"Screenshot_12_3_24__2_08_PM\" src=\"https://github.com/user-attachments/assets/c1615d80-2197-46cc-bee6-1f1140d96c2f\">\r\n\r\n\r\n### Actual behavior\r\n\r\nBelow 600px it does not:\r\n\r\n<img width=\"617\" alt=\"Screenshot_12_3_24__2_07_PM\" src=\"https://github.com/user-attachments/assets/195dbeae-3053-4cfb-af2e-27aef17695ca\">\r\n\r\n","Url":"https://github.com/jgthms/bulma/issues/3944","RelatedDescription":"Open issue \"Navbar broken for certain \"grid is-col-min-...\" and viewport combinations\" (#3944)"},{"Id":"2711036104","IsPullRequest":false,"CreatedAt":"2024-12-02T08:44:28","Actor":"martinskou","Number":"3943","RawContent":null,"Title":"Lag using navbar in Firefox","State":"open","Body":"This is about **Bulma | Firefox.\r\n\r\nIs it a bug or do I need help? \r\n\r\n### Overview of the problem\r\n\r\nThis is about the Bulma **CSS framework**\r\nI'm using Bulma **version** [1.0.2]\r\nMy **browser** is: Firefox 134.0b3\r\n\r\n\r\n### Description\r\n\r\nWhen using the navbar component it experience lag / slowness in the browser response.\r\nEg. when i move the mouse over the navbar, the hover effect is slow to appear.\r\n\r\n### Steps to Reproduce\r\n\r\nUse a navbar \r\n\r\n### Expected behavior\r\n\r\nAlways snappy behaviour.\r\n\r\n### Actual behavior\r\n\r\nMost of the time snappy, but sometimes laggy.\r\n\r\n### Firefox issue\r\n\r\nLooks like a Firefox bug:\r\n\r\nhttps://bugzilla.mozilla.org/show_bug.cgi?id=1926626\r\n\r\n\r\n","Url":"https://github.com/jgthms/bulma/issues/3943","RelatedDescription":"Open issue \"Lag using navbar in Firefox\" (#3943)"},{"Id":"2704883002","IsPullRequest":false,"CreatedAt":"2024-11-29T18:33:01","Actor":"francesco-loreti","Number":"3942","RawContent":null,"Title":"[bulma@^1.0.2 Deprecation Warning] Global built-in functions are deprecated and will be removed in Dart Sass 3.0.0.","State":"closed","Body":"bulma@^1.0.2\r\n\r\n```\r\nDeprecation Warning: Global built-in functions are deprecated and will be removed in Dart Sass 3.0.0.\r\nUse meta.type-of instead.\r\nMore info and automated migrator: https://sass-lang.com/d/import\r\n\r\nDeprecation Warning: blue() is deprecated. Suggestion: color.channel($color, \"blue\", $space: rgb)\r\nDeprecation Warning: red() is deprecated. Suggestion: color.channel($color, \"red\", $space: rgb)\r\nDeprecation Warning: green() is deprecated. Suggestion: color.channel($color, \"green\", $space: rgb)\r\n\r\nDeprecation Warning: Global built-in functions are deprecated and will be removed in Dart Sass 3.0.0.\r\nUse map.merge instead.\r\n\r\n$color-rgb: map-merge(\r\n    │ ┌─────────────────^\r\n116 │ │       $color-rgb,\r\n117 │ │       (\r\n118 │ │         $name: $value,\r\n119 │ │       )\r\n120 │ │     );\r\n    │ └─────^\r\n    ╵\r\n    node_modules\\bulma\\sass\\utilities\\functions.scss 115:17\r\n```","Url":"https://github.com/jgthms/bulma/issues/3942","RelatedDescription":"Closed issue \"[bulma@^1.0.2 Deprecation Warning] Global built-in functions are deprecated and will be removed in Dart Sass 3.0.0.\" (#3942)"},{"Id":"2687776226","IsPullRequest":false,"CreatedAt":"2024-11-28T02:53:00","Actor":"benjamin-dreux","Number":"3939","RawContent":null,"Title":"Checkbox spacing depends on whitespace","State":"closed","Body":"Here is an exemple of what checbox looks without whitespace (in a trimmed html)\r\n\r\n![image](https://github.com/user-attachments/assets/5b2d53c4-0684-4655-9016-e384d2def03a)\r\n\r\nHere is the code attached to id\r\n\r\n<div class=\"field\"><div class=\"control\"><label class=\"checkbox\"><input type=\"checkbox\" name=\"isOrganization\" class=\"checkbox\">Is organization</label></div></div>\r\n\r\nBut as soon as you create white space arround elements like so\r\n\r\n<div class=\"field\">\r\n  <div class=\"control\">\r\n    <label class=\"checkbox\">\r\n      <input type=\"checkbox\" name=\"isOrganization\" class=\"checkbox\">\r\n      Is organization\r\n    </label>\r\n  </div>\r\n</div>\r\n\r\nThen checkbox looks as nice as the documentation\r\n\r\n![image](https://github.com/user-attachments/assets/aed0b6be-7656-4c32-bfa4-6fee0c8c5f82)\r\n\r\nIf your html is generated without empty space that not that cool","Url":"https://github.com/jgthms/bulma/issues/3939","RelatedDescription":"Closed issue \"Checkbox spacing depends on whitespace\" (#3939)"},{"Id":"2624514573","IsPullRequest":true,"CreatedAt":"2024-11-27T16:11:11","Actor":"jnoordsij","Number":"3930","RawContent":null,"Title":"Update various references from master to main brach","State":"closed","Body":"<!-- PLEASE READ THE FOLLOWING INSTRUCTIONS -->\r\n<!-- DO NOT REBUILD THE CSS OUTPUT IN YOUR PR -->\r\n\r\n<!-- Choose one of the following: -->\r\nThis is a **new feature | improvement | bugfix | documentation fix**.\r\n<!-- New feature? Update the CHANGELOG.md too, and eventually the Docs. -->\r\n<!-- Improvement? Explain how and why. -->\r\n<!-- Bugfix? Reference that issue as well. -->\r\n\r\n### Proposed solution\r\n\r\nWhen checking some things when preparing another MR, I noticed some links were out-of-date.\r\nThis MR updates various references from `master` to `main`, given that seems to be the new default branch now.\r\n\r\nNote: https://github.com/jgthms/bulma/blob/main/docs/documentation/start/responsiveness.html still has some `master` references too; these might need to be revised in some way too.\r\n\r\n### Tradeoffs\r\n\r\nN/A\r\n\r\n### Testing Done\r\n\r\nNone.\r\n\r\n<!-- BEFORE SUBMITTING YOUR PR, MAKE SURE TO FOLLOW THESE STEPS: -->\r\n<!-- 1. Pull the latest `master` branch -->\r\n<!-- 2. Make sure your Sass code is compliant with the [Bulma Sass styleguide](https://github.com/jgthms/bulma/blob/master/.github/CONTRIBUTING.md#bulma-sass-styleguide) -->\r\n<!-- 3. Make sure your PR only affects `.sass` or documentation files -->\r\n<!-- 4. [Try your changes](https://github.com/jgthms/bulma/blob/master/.github/CONTRIBUTING.md#try-your-changes). -->\r\n\r\n<!-- How have you confirmed this feature works? -->\r\n<!-- Please explain more than \"Yes\". -->\r\n\r\n### Changelog updated?\r\n\r\nNo.\r\n\r\n<!-- Thanks! -->\r\n","Url":"https://github.com/jgthms/bulma/pull/3930","RelatedDescription":"Closed or merged PR \"Update various references from master to main brach\" (#3930)"},{"Id":"2688027696","IsPullRequest":true,"CreatedAt":"2024-11-27T15:47:28","Actor":"SomethingNew71","Number":"3940","RawContent":null,"Title":"Updates deprecated round functions in Sass Build","State":"closed","Body":"<!-- PLEASE READ THE FOLLOWING INSTRUCTIONS -->\r\n<!-- DO NOT REBUILD THE CSS OUTPUT IN YOUR PR -->\r\n\r\n<!-- Choose one of the following: -->\r\nThis is a **bugfix**.\r\n<!-- New feature? Update the CHANGELOG.md too, and eventually the Docs. -->\r\n<!-- Improvement? Explain how and why. -->\r\n<!-- Bugfix? Reference that issue as well. -->\r\n\r\n### Proposed solution\r\n\r\nFixes some of the errors related to #3907 \r\n\r\n### Testing Done\r\n\r\nNone.\r\n\r\n<!-- BEFORE SUBMITTING YOUR PR, MAKE SURE TO FOLLOW THESE STEPS: -->\r\n<!-- 1. Pull the latest `master` branch -->\r\n<!-- 2. Make sure your Sass code is compliant with the [Bulma Sass styleguide](https://github.com/jgthms/bulma/blob/master/.github/CONTRIBUTING.md#bulma-sass-styleguide) -->\r\n<!-- 3. Make sure your PR only affects `.sass` or documentation files -->\r\n<!-- 4. [Try your changes](https://github.com/jgthms/bulma/blob/master/.github/CONTRIBUTING.md#try-your-changes). -->\r\n\r\n<!-- How have you confirmed this feature works? -->\r\n<!-- Please explain more than \"Yes\". -->\r\n\r\n### Changelog updated?\r\n\r\nNo.\r\n\r\n<!-- Thanks! -->\r\n","Url":"https://github.com/jgthms/bulma/pull/3940","RelatedDescription":"Closed or merged PR \"Updates deprecated round functions in Sass Build\" (#3940)"},{"Id":"2694397955","IsPullRequest":false,"CreatedAt":"2024-11-26T11:52:29","Actor":"apomili","Number":"3941","RawContent":null,"Title":"Section hidden native style is overridden by base/generic","State":"open","Body":"\r\nThis is about **Bulma**.\r\n\r\n\r\n### Overview of the problem\r\n\r\n<!-- UNCOMMENT THE APPROPRIATE LINES -->\r\n\r\n<!-- This is about the Bulma **CSS framework** -->\r\n I'm using Bulma **1.0.2** \r\n My **browser** is: **Chrome**\r\n\r\n### Description\r\n\r\nThe native style of `<section hidden>` is overridden by base/generic.scss\r\n\r\n### Steps to Reproduce\r\n\r\n1. Set on a page a tag section with an hidden attribute like ` <section hidden></section>`\r\n2. Add bulma style with `@use \"bulma/sass/base \"`\r\n3. Inspect console on that tag\r\n\r\n\r\n### Expected behavior\r\n\r\nThe section should have\r\n\r\n```\r\nsection[Attributes Style] {\r\n    display: none;\r\n}\r\n```\r\n\r\n### Actual behavior\r\n\r\nThe section get\r\n\r\n```\r\narticle, aside, figure, footer, header, hgroup, section {\r\n    display: block;\r\n}\r\n```\r\n","Url":"https://github.com/jgthms/bulma/issues/3941","RelatedDescription":"Open issue \"Section hidden native style is overridden by base/generic\" (#3941)"},{"Id":"2681438600","IsPullRequest":false,"CreatedAt":"2024-11-22T00:50:42","Actor":"Kehino","Number":"3938","RawContent":null,"Title":"Inconsistent spacing under form elements","State":"open","Body":"<!-- PLEASE READ THE FOLLOWING INSTRUCTIONS -->\r\n\r\n<!-- Choose one of the following: -->\r\nThis is about **Bulma**. It is a feature request about a behavior that could be considered a bug.\r\n\r\n### Overview of the problem\r\n\r\n<!-- UNCOMMENT THE APPROPRIATE LINES -->\r\n\r\nThis is about the Bulma **CSS framework**\r\n<!-- This is about the Bulma **Docs** -->\r\nI'm using Bulma **version** 1.0.2\r\n<!-- My **browser** is: -->\r\n<!-- This is a **Sass** issue: I'm using version [x.x.x] -->\r\nI am sure this issue is **not a duplicate**.\r\n\r\n### Description\r\n\r\n<!-- Description of the bug, enhancement, or question -->\r\n\r\n![Screenshot 2024-11-22 at 00-46-55 Hello Bulma!](https://github.com/user-attachments/assets/5db171f0-a372-40de-b383-2bf13e1e2d08)\r\n\r\n![Screenshot 2024-11-22 at 00-46-47 Hello Bulma!](https://github.com/user-attachments/assets/f215e296-9993-4f8f-941d-017a7c5fe8c1)\r\n\r\nThe top spacing of the `help` after nested `field`s within a `field` should be identical to the spacing under a `control`.\r\n\r\n### Steps to Reproduce\r\n\r\n<details><summary>Full example</summary>\r\n<p>\r\n\r\n```html\r\n    <div class=\"field\">\r\n    <label class=\"label\">Numéro de téléphone</label>\r\n    <div class=\"control\">\r\n        <input class=\"input\" type=\"tel\" placeholder=\"Numéro de téléphone\" />\r\n    </div>\r\n    <p class=\"help\">Si votre numéro n'est pas un numéro français (+33), précisez l'indicatif. Celui-ci est uniquement utilisé pour la livraison.</p>\r\n    </div>\r\n    <div class=\"field\">\r\n    <label class=\"label\">Dimensions</label>\r\n    <div class=\"field is-grouped\">\r\n        <div class=\"control is-expanded\">\r\n            <div class=\"field has-addons\">\r\n                <div class=\"control\">\r\n                    <a class=\"button is-static\">\r\n                    Hauteur\r\n                    </a>\r\n                </div>\r\n                <div class=\"control is-expanded\">\r\n                    <input class=\"input\" type=\"text\" value=\"56\" />\r\n                </div>\r\n                <div class=\"control\">\r\n                    <a class=\"button is-static\">\r\n                    mm\r\n                    </a>\r\n                </div>\r\n            </div>\r\n        </div>\r\n        <div class=\"control is-expanded\">\r\n        <div class=\"field has-addons\">\r\n            <div class=\"control\">\r\n                <a class=\"button is-static\">\r\n                Largeur\r\n                </a>\r\n            </div>\r\n            <div class=\"control is-expanded\">\r\n                <input class=\"input\" type=\"text\" value=\"56\" />\r\n            </div>\r\n            <div class=\"control\">\r\n                <a class=\"button is-static\">\r\n                mm\r\n                </a>\r\n            </div>\r\n        </div>\r\n        </div>\r\n        <div class=\"control is-expanded\">\r\n        <div class=\"field has-addons\">\r\n            <div class=\"control\">\r\n                <a class=\"button is-static\">\r\n                Longueur\r\n                </a>\r\n            </div>\r\n            <div class=\"control is-expanded\">\r\n                <input class=\"input\" type=\"text\" value=\"56\" />\r\n            </div>\r\n            <div class=\"control\">\r\n                <a class=\"button is-static\">\r\n                mm\r\n                </a>\r\n            </div>\r\n        </div>\r\n        </div>\r\n    </div>\r\n    <p class=\"help\">Les valeurs des trois champs sont liées: lorsque l'une est changée, les autres sont recalculées.</p>\r\n    </div>\r\n``` \r\n\r\n</p>\r\n</details> \r\n\r\n### Expected behavior\r\n\r\nThe top spacing of the `help` after nested `field`s within a `field` should be identical to the spacing under a `control`. This is because these nested `field`s are meant (IMO) as helpers (for `has-addons` or `is-grouped`) and not as spacers in that case.\r\n\r\n### Actual behavior\r\n\r\nThe top spacing of the `help` after nested `field`s within a `field` is currently the one after any `field`.\r\n\r\n### Fix\r\n\r\n(actually not tested...)\r\n\r\n```scss\r\n.field {\r\n    .control + .help, .field + .help {\r\n         padding: var(--bulma-control-padding-vertical); \r\n    }\r\n}\r\n```\r\n","Url":"https://github.com/jgthms/bulma/issues/3938","RelatedDescription":"Open issue \"Inconsistent spacing under form elements\" (#3938)"},{"Id":"2681150031","IsPullRequest":true,"CreatedAt":"2024-11-21T22:31:04","Actor":"brendon","Number":"3937","RawContent":null,"Title":"Add .has-text-weight-extrabold","State":"open","Body":"This is an improvement.\r\n\r\nWe have a variable for `extrabold` font weight so it makes sense to have the typography utility class to use also. \r\n\r\n### Testing Done\r\n\r\nNone.\r\n\r\n### Changelog updated?\r\n\r\nYes.","Url":"https://github.com/jgthms/bulma/pull/3937","RelatedDescription":"Open PR \"Add .has-text-weight-extrabold\" (#3937)"},{"Id":"2673561663","IsPullRequest":false,"CreatedAt":"2024-11-19T21:16:22","Actor":"ragonneau","Number":"3936","RawContent":null,"Title":"`navbar-item` for `<button>`","State":"open","Body":"This is about **Bulma**.\r\n\r\n### Overview of the problem\r\n\r\nThis is about the Bulma **CSS framework**\r\nI am sure this issue is **not a duplicate**\r\n\r\n### Description\r\n\r\nFirst, thank you very much for the framework, very useful !\r\n\r\nThe `navbar-item` class is implemented for `<a>` and `<div>` but not for `<button>`. This would be a great feature, because it is common to have a logout button in a dropdown in the navigation bar, which is generally a POST.\r\n\r\n### Steps to Reproduce\r\n\r\nI give here an example of a navbar with a logout button in a dropdown.\r\n\r\n```html\r\n<nav class=\"navbar is-fixed-top\">\r\n    <div class=\"navbar-brand\">\r\n        <a class=\"navbar-item\" href=\"#\">\r\n            <strong>\r\n                My project\r\n            </strong>\r\n        </a>\r\n        <a role=\"button\" class=\"navbar-burger\" aria-label=\"menu\" aria-expanded=\"false\" data-target=\"navbarMenu\">\r\n            <span aria-hidden=\"true\"></span>\r\n            <span aria-hidden=\"true\"></span>\r\n            <span aria-hidden=\"true\"></span>\r\n            <span aria-hidden=\"true\"></span>\r\n        </a>\r\n    </div>\r\n    <div id=\"navbarMenu\" class=\"navbar-menu\">\r\n        <div class=\"navbar-end\">\r\n            <div class=\"navbar-item has-dropdown\">\r\n                <a class=\"navbar-link\">\r\n                    Welcome user\r\n                </a>\r\n                <div class=\"navbar-dropdown is-right\">\r\n                    <a class=\"navbar-item\">\r\n                        About\r\n                    </a>\r\n                    <hr class=\"navbar-divider\">\r\n                    <form action=\"...\" method=\"post\">\r\n                        <button type=\"submit\" class=\"navbar-item\">\r\n                            Logout\r\n                        </button>\r\n                    </form>\r\n                </div>\r\n            </div>\r\n        </div>\r\n    </div>\r\n</nav>\r\n```\r\n\r\n### Expected behavior\r\n\r\nFrom a user perspective, the \"About\" and \"Logout\" items in the dropdown should render exactly the same way.\r\n\r\n### Actual behavior\r\n\r\nThe placement, padding, etc, works fine, but the over effect is not working for the \"Logout\" button.\r\n","Url":"https://github.com/jgthms/bulma/issues/3936","RelatedDescription":"Open issue \"`navbar-item` for `<button>`\" (#3936)"},{"Id":"2617331511","IsPullRequest":false,"CreatedAt":"2024-11-11T10:32:11","Actor":"simonw","Number":"3926","RawContent":null,"Title":"Documentation heading looks bad at 1016px wide","State":"closed","Body":"### Overview of the problem\r\n\r\nThis is about the Bulma **Docs**\r\n\r\nMy **browser** is: Firefox on macOS\r\n\r\n### Description\r\n\r\n![CleanShot 2024-10-27 at 22 18 43@2x](https://github.com/user-attachments/assets/d89779d8-8cb4-44bf-8390-71088966e262)\r\n\r\n### Steps to Reproduce\r\n\r\nResize browser to around 1016px wide, visit https://bulma.io/documentation/","Url":"https://github.com/jgthms/bulma/issues/3926","RelatedDescription":"Closed issue \"Documentation heading looks bad at 1016px wide\" (#3926)"},{"Id":"2646272903","IsPullRequest":false,"CreatedAt":"2024-11-09T16:29:34","Actor":"benjamin-dreux","Number":"3935","RawContent":null,"Title":"input field with has-addons doesn't play nice with labels","State":"open","Body":"<!-- PLEASE READ THE FOLLOWING INSTRUCTIONS -->\r\n\r\n<!-- Choose one of the following: -->\r\nThis is about **Bulma | the Docs**.\r\n\r\n<!-- Is it about Bulma or about the Docs? -->\r\n<!-- Is it a bug/feature/question or do you need help? -->\r\n<!-- If it's a bug, is it a browser bug? -->\r\n\r\nIt's a bug that doesn't tie to a specific bowser. It can be reproduce with chrome or firefox.\r\n\r\n### Overview of the problem\r\n\r\n<!-- UNCOMMENT THE APPROPRIATE LINES -->\r\n\r\nThis is about the Bulma **CSS framework** \r\n<!-- This is about the Bulma **Docs** -->\r\n<!-- I'm using Bulma **version** [x.x.x] -->\r\n<!-- My **browser** is: -->\r\n<!-- This is a **Sass** issue: I'm using version [x.x.x] -->\r\n<!-- I am sure this issue is **not a duplicate**? -->\r\n\r\n### Description\r\n\r\nWhen creating a form field that has an addons, the controls are put on the same line as the label itself, even if the labels of this form are supposed to be one line upper.\r\n\r\n### Steps to Reproduce\r\n\r\n\r\n```\r\n<form class=\"form\">\r\n  <div class =\"field has-addons\">\r\n    <label class =\"label\">Requested amount</label>\r\n    <p class=\"control\">\r\n      <span class=\"select\">\r\n        <select>\r\n          <option>$</option>\r\n          <option>£</option>\r\n          <option>€</option>\r\n        </select>\r\n      </span>\r\n    </p>\r\n    <p class=\"control\">\r\n      <input class=\"input\" type=\"text\" placeholder=\"Amount of money\">\r\n    </p>\r\n    <p class=\"control\">\r\n      <button class=\"button\">\r\n        Transfer\r\n      </button>\r\n    </p>\r\n  </div>\r\n</form>\r\n```\r\n### Expected behavior\r\n\r\nlabel should be on a distinct line than the inputs by them self\r\n\r\n### Actual behavior\r\n\r\n![image](https://github.com/user-attachments/assets/9f56c3e1-c8d1-4cf4-adf7-a925112b4738)\r\n","Url":"https://github.com/jgthms/bulma/issues/3935","RelatedDescription":"Open issue \"input field with has-addons doesn't play nice with labels\" (#3935)"},{"Id":"2635786749","IsPullRequest":false,"CreatedAt":"2024-11-05T15:31:57","Actor":"Aic-02mz","Number":"3934","RawContent":null,"Title":"Out of date Sass","State":"open","Body":"Removing Ruby Sass and Node Sass. \r\n\r\nThese are both end-of-life and no longer supported.\r\n\r\nDeleting them from the Test Folder and other areas where they are used, would make it easier to read and interpret this GitHub repo. \r\n\r\n<img width=\"296\" alt=\"o \" src=\"https://github.com/user-attachments/assets/f27fb2ec-0ba7-47f7-89ca-984c068a9124\">\r\n<img width=\"403\" alt=\"o  2\" src=\"https://github.com/user-attachments/assets/d64ae0b0-7b5e-4f04-8111-166ffc97ab82\">\r\n\r\n\r\nHere =\r\n<img width=\"616\" alt=\"o  2\" src=\"https://github.com/user-attachments/assets/b9746d94-c5ff-47b9-8d8a-e0e65007b3bf\">\r\n","Url":"https://github.com/jgthms/bulma/issues/3934","RelatedDescription":"Open issue \"Out of date Sass\" (#3934)"},{"Id":"2633245187","IsPullRequest":false,"CreatedAt":"2024-11-04T16:16:25","Actor":"Mario8419","Number":"3933","RawContent":null,"Title":"Update from 0.9.3 to v1 issue","State":"open","Body":"Hello,\r\n\r\nI just updated Bulma from version 0.9.3 to v1.0.0 in my React/Gatsby application. I followed the documentation but am facing several issues. My project uses a .sass file to import and customize Bulma, with \"sass\": \"^1.69.7\".\r\n\r\nHere's my all.sass file:\r\n\r\nsass\r\n@import \"~bulma/sass/utilities/initial-variables\"\r\n\r\n$brand: #2cd1b8\r\n$brand-invert: #fff\r\n$primary: $brand\r\n$family-primary: 'Montserrat'\r\n\r\n// Other custom styles...\r\n\r\n@import \"~bulma\"  // Following the docs, this might not be needed in v1?\r\n\r\nProblems Encountered:\r\n\r\nFor e.g. the custom $family-primary (Montserrat) is not being applied.\r\nSeveral other custom styles, which worked perfectly in version 0.9.3, seem broken or are not being applied at all, for example, button sizes and so on\r\n\r\n\r\nSteps to Reproduce:\r\n\r\nUse the all.sass file as shown above.\r\nRun the project in a React/Gatsby environment.\r\nExpected Behavior:\r\n\r\nCustom styles should work as defined in the .sass file, including the $family-primary.\r\nCurrent Behavior:\r\n\r\nDefault Bulma styles are overriding my custom styles.\r\nFont family and other styles defined via Sass variables are not being applied.\r\nEnvironment:\r\n\r\nBulma version: 1.0.0\r\nSass version: 1.69.7\r\nFramework: React/Gatsby\r\nAdditional Context:\r\n\r\nEverything worked fine with Bulma 0.9.3.\r\nI've gone through the migration guide but couldn't resolve these issues.\r\nAny help or guidance would be appreciated. Thank you!","Url":"https://github.com/jgthms/bulma/issues/3933","RelatedDescription":"Open issue \"Update from 0.9.3 to v1 issue\" (#3933)"},{"Id":"2628740686","IsPullRequest":false,"CreatedAt":"2024-11-01T10:05:37","Actor":"rnkpplr","Number":"3932","RawContent":null,"Title":"Incorrect value for `one-third selectors` e.g.  .columns.is-mobile > .column.is-offset-one-third ","State":"open","Body":"https://github.com/jgthms/bulma/blob/3b63997ad2c614ce438145063833e4b162350852/sass/grid/columns.scss#L108\r\nIf I'm not wrong, `margin-inline-start: 33.3333%;` should be here instead of `margin-inline-start: 0.3333%;` ? And there are a few more `on-third` selectors in the file, which have a value of `0.3333%`\r\n","Url":"https://github.com/jgthms/bulma/issues/3932","RelatedDescription":"Open issue \"Incorrect value for `one-third selectors` e.g.  .columns.is-mobile > .column.is-offset-one-third \" (#3932)"},{"Id":"2624535725","IsPullRequest":true,"CreatedAt":"2024-10-30T15:48:23","Actor":"jnoordsij","Number":"3931","RawContent":null,"Title":"Remove vendor prefixes from sass","State":"open","Body":"<!-- PLEASE READ THE FOLLOWING INSTRUCTIONS -->\r\n<!-- DO NOT REBUILD THE CSS OUTPUT IN YOUR PR -->\r\n\r\n<!-- Choose one of the following: -->\r\nThis is a **new feature | improvement | bugfix | documentation fix**.\r\n<!-- New feature? Update the CHANGELOG.md too, and eventually the Docs. -->\r\n<!-- Improvement? Explain how and why. -->\r\n<!-- Bugfix? Reference that issue as well. -->\r\n\r\n### Proposed solution\r\n\r\nWhen debugging some other issues with placeholders in my application, I noticed some vendor prefixes popping up on attributes where I did not expect them. Then I figured that they are actually hardcoded within the scope of this repository, rather than applied by tooling (e.g. `autoprefixer`).\r\n\r\n*Edit:* for the `::placeholder` mixin, it was actually rendering all the variants *except* for the correct modern `::placeholder` pseudo-element, so this actually might ensure proper behavior across environments that previously did not work.\r\n\r\nThis PR removes the hardcoded vendor-prefixed variants of some properties. The preferred way (I think) should be using tooling to handle this. Although the `README` mentions that `autoprefixer` is used within this repository, it seems it has since been replaced with `cssnano`, which may not include it by default.\r\n\r\nProbably this requires rebuilding `css` too, however the `npm run build` alias mentioned in `CONTRIBUTING.md` no longer exists, so I'm not sure which parts are intended to run on MR submissions.\r\n\r\nNote: I encountered this issue on version `v0.9.4`, but I'm not sure if bugfixes are still welcome for the old version?\r\n\r\n### Tradeoffs\r\n\r\nTheoretically this could cause a change of behavior on legacy browsers. Given the wide availability of the non-prefixed alternatives and the fact that tooling like `autoprefixer` is commonly used, I suspect this will have little to no impact in that regard.\r\n\r\n### Testing Done\r\n\r\nNone.\r\n\r\n<!-- BEFORE SUBMITTING YOUR PR, MAKE SURE TO FOLLOW THESE STEPS: -->\r\n<!-- 1. Pull the latest `master` branch -->\r\n<!-- 2. Make sure your Sass code is compliant with the [Bulma Sass styleguide](https://github.com/jgthms/bulma/blob/master/.github/CONTRIBUTING.md#bulma-sass-styleguide) -->\r\n<!-- 3. Make sure your PR only affects `.sass` or documentation files -->\r\n<!-- 4. [Try your changes](https://github.com/jgthms/bulma/blob/master/.github/CONTRIBUTING.md#try-your-changes). -->\r\n\r\n<!-- How have you confirmed this feature works? -->\r\n<!-- Please explain more than \"Yes\". -->\r\n\r\n### Changelog updated?\r\n\r\nNo.\r\n\r\n<!-- Thanks! -->\r\n","Url":"https://github.com/jgthms/bulma/pull/3931","RelatedDescription":"Open PR \"Remove vendor prefixes from sass\" (#3931)"},{"Id":"2618866991","IsPullRequest":false,"CreatedAt":"2024-10-28T16:07:10","Actor":"kLOsk","Number":"3927","RawContent":null,"Title":"Does Bulma SASS really takes 12s to compile with DART SASS and Gulp?","State":"open","Body":"<!-- PLEASE READ THE FOLLOWING INSTRUCTIONS -->\r\n\r\n<!-- Choose one of the following: -->\r\nThis is about **Bulma**.\r\n\r\n<!-- Is it about Bulma or about the Docs? -->\r\n<!-- Is it a bug/feature/question or do you need help? -->\r\n<!-- If it's a bug, is it a browser bug? -->\r\n\r\n### Overview of the problem\r\n\r\n<!-- UNCOMMENT THE APPROPRIATE LINES -->\r\nThis is about the Bulma **CSS framework**\r\n<!-- This is about the Bulma **Docs** -->\r\nI'm using Bulma **version** [1.0.2]\r\n<!-- My **browser** is: -->\r\nThis is a **Sass** issue: I'm using version [1.58.1]\r\nI am sure this issue is **not a duplicate**\r\n\r\n### Description\r\n\r\n<!-- Description of the bug, enhancement, or question -->\r\n\r\nI'm using Gulp with Bulma and DART SASS. I tried multiple DART SASS versions, but they all end up equally slow, about 12s to compile. I'm working with an i9 MacBook Pro. I would just like a confirmation that this is normal or ideally some advice if this is not normal, what I can do to speed it up? I'm aware of having the option to load fewer modules, but even with fewer modules it still seems very slow. The slow taks in gulp is always the style compilation\r\n\r\n```\r\n[17:00:40] Starting 'styles'...\r\n[Browsersync] 2 files changed (main.css.map, main.css)\r\n[17:00:52] Finished 'styles' after 12 s\r\n[17:06:42] Starting 'styles'...\r\n[Browsersync] 2 files changed (main.css.map, main.css)\r\n[17:06:54] Finished 'styles' after 12 s\r\n```\r\n\r\nThanks\r\n","Url":"https://github.com/jgthms/bulma/issues/3927","RelatedDescription":"Open issue \"Does Bulma SASS really takes 12s to compile with DART SASS and Gulp?\" (#3927)"},{"Id":"2616028337","IsPullRequest":false,"CreatedAt":"2024-10-26T17:43:42","Actor":"leolivier","Number":"3925","RawContent":null,"Title":"Add a class for \"white-space: normal\" ?","State":"open","Body":"### Overview of the problem\r\nThis is about Bulma 1.0.1\r\n\r\nInside a grid, I have some html code like this:\r\n```\r\n<div class=\"cell has-text-centered\">\r\n        <a class=\"button is-dark has-text-wrap\" href=\"/members/xxx/\">\r\n          <figure class=\"image mini-avatar mr-2\">\r\n            <img class=\"is-rounded\" src=\"/media/avatars/an_avatar.jpg\">\r\n          </figure>\r\n          <strong>A Quite Long Name</strong>\r\n        </a>\r\n      </div>\r\n```\r\nWhen the name in the <strong> markers is long, it can expand outside of the cell. But, as there is a mini photo just besides, it could be displayed as multiline.\r\n\r\nI looked at different solutions with the help of Claude Sonnet 3.5:\r\n* add 'is-multiline' class to the \"button\" : no effect at all\r\n* add \"is-flex-wrap-wrap\" class to the button: the line break is after the photo, the text is left unwrapped\r\n* add \"has-text-wrap\" class to the button: no effect\r\n* add \"white-space: normal\" style to the button, and then it works!\r\n\r\nSo I tried to find how to express that with Bulma, but I didn't find any way...\r\nI finally created my own CSS class:\r\n```css\r\n.button-wrap {\r\n  white-space: normal !important\r\n}\r\nWouldn't i be worth having this as a supported Bulma class?","Url":"https://github.com/jgthms/bulma/issues/3925","RelatedDescription":"Open issue \"Add a class for \"white-space: normal\" ?\" (#3925)"},{"Id":"2614449549","IsPullRequest":false,"CreatedAt":"2024-10-25T15:36:13","Actor":"MangelMaxime","Number":"3924","RawContent":null,"Title":"`has-0-cols` for `fixed-grid` should be removed","State":"open","Body":"<!-- PLEASE READ THE FOLLOWING INSTRUCTIONS -->\r\n\r\n<!-- Choose one of the following: -->\r\nThis is about **Bulma**.\r\n\r\n### Overview of the problem\r\n\r\n<!-- UNCOMMENT THE APPROPRIATE LINES -->\r\n\r\nThis is about the Bulma **CSS framework**\r\nThis is about the Bulma **Docs**\r\n<!-- I'm using Bulma **version** [x.x.x] -->\r\n<!-- My **browser** is: -->\r\n<!-- This is a **Sass** issue: I'm using version [x.x.x] -->\r\n<!-- I am sure this issue is **not a duplicate**? -->\r\n\r\n### Description\r\n\r\n<!-- Description of the bug, enhancement, or question -->\r\n\r\n[Fixed Grid documentation](https://bulma.io/documentation/grid/fixed-grid/) mention a `has-0-cols` but at the same time says that columns can go from 1 to 12.\r\n\r\nI think `has-0-cols` does not exist and if it does, then it should be removed from Bulma because minimal column count for a grid is 1.\r\n\r\n","Url":"https://github.com/jgthms/bulma/issues/3924","RelatedDescription":"Open issue \"`has-0-cols` for `fixed-grid` should be removed\" (#3924)"}],"ResultType":"GitHubIssue"}},"RunOn":"2025-01-10T03:30:08.134092Z","RunDurationInMilliseconds":475}
\ No newline at end of file
+{"Data":{"Bulma-Issues":{"Issues":[{"Id":"2781055423","IsPullRequest":true,"CreatedAt":"2025-01-10T20:15:02","Actor":"martinkupa","Number":"3958","RawContent":null,"Title":"[Docs] Mention required order on form controls' modifiers","State":"open","Body":"<!-- PLEASE READ THE FOLLOWING INSTRUCTIONS -->\r\n<!-- DO NOT REBUILD THE CSS OUTPUT IN YOUR PR -->\r\n\r\n<!-- Choose one of the following: -->\r\nThis is a **documentation fix**.  Given the following html\r\n```\r\n    <div class=\"field has-addons\">\r\n        <div class=\"control has-icons-left\">\r\n            <span class=\"icon is-small is-left\">\r\n                <i class=\"fa fa-filter\" aria-hidden=\"true\"></i> \r\n            </span>\r\n            <input class=\"input\" type=\"text\" placeholder=\"Find a repository\">\r\n        </div>\r\n        <div class=\"control\">\r\n            <button class=\"button is-info\">\r\n            Search\r\n          </button>\r\n        </div>\r\n      </div>\r\n```\r\nif the input is not the control's first child the icon disappears when the input is selected.\r\n\r\n### Changelog updated?\r\n\r\nNo.\r\n\r\n\r\n","Url":"https://github.com/jgthms/bulma/pull/3958","RelatedDescription":"Open PR \"[Docs] Mention required order on form controls' modifiers\" (#3958)"},{"Id":"2780592349","IsPullRequest":false,"CreatedAt":"2025-01-10T16:29:55","Actor":"L1feF0rm","Number":"3957","RawContent":null,"Title":"Incompatibility with Alpine.js framework","State":"open","Body":"<!-- PLEASE READ THE FOLLOWING INSTRUCTIONS -->\r\n\r\n<!-- Choose one of the following: -->\r\nThis is about **Bulma**.\r\n\r\n### Overview of the problem\r\n\r\n<!-- UNCOMMENT THE APPROPRIATE LINES -->\r\n\r\nThis is about the Bulma **CSS framework** incompatibility with [Alpine.js](https://alpinejs.dev/) framework\r\nI'm using Bulma **version** 1.0.3\r\nMy **browser** is: Chrome 131\r\nI am sure this issue is **not a duplicate** (or at least i could not find a duplicate)\r\n\r\n### Description\r\n\r\n<!-- Description of the bug, enhancement, or question -->\r\n\r\n### Steps to Reproduce\r\n\r\n1. Use tabs container element with classes `tabs` and `is-toggle` (and optionally `is-toggle-rounded`)\r\n2. Iterate children using alpinejs x-for and template\r\n\r\n[Demo](https://laravel9-php.vercel.app/rickandmortyapi)\r\n\r\n### Expected behavior\r\n\r\nFirst tab should have rounded corners\r\n\r\n### Actual behavior\r\n\r\nFirst tab does not have rounded corners.\r\n\r\nThis is because the first child is actually a template element (inspect the demo) and fails the `.tabs.is-toggle li:first-child a` and `.tabs.is-toggle.is-toggle-rounded li:first-child a` selectors. Would you consider fixing this? I would suggest using `:first-of-type` instead of `:first-child`, or even make a PR if you prefer.\r\n\r\nThank you\r\n","Url":"https://github.com/jgthms/bulma/issues/3957","RelatedDescription":"Open issue \"Incompatibility with Alpine.js framework\" (#3957)"},{"Id":"2770686131","IsPullRequest":false,"CreatedAt":"2025-01-06T13:40:04","Actor":"AbstractionsAs","Number":"3956","RawContent":null,"Title":"Regression from 0.9.3: Background color for menu","State":"open","Body":"<!-- PLEASE READ THE FOLLOWING INSTRUCTIONS -->\r\n\r\n<!-- Choose one of the following: -->\r\nThis is about **Bulma**.\r\n\r\n<!-- Is it about Bulma or about the Docs? -->\r\n<!-- Is it a bug/feature/question or do you need help? -->\r\n<!-- If it's a bug, is it a browser bug? -->\r\n\r\n### Overview of the problem\r\n\r\n<!-- UNCOMMENT THE APPROPRIATE LINES -->\r\n\r\nThis is about the Bulma **CSS framework**\r\n<!-- This is about the Bulma **Docs** -->\r\nI'm using Bulma **version** 1.0.2\r\n\r\n\r\n### Description\r\n\r\nIn Bulma 0.9.3, you could set the background color of a \"menu\" component, e.g. \"has-background-light\", and it would work as expected. \r\nSince Bulma 1.0, this gives silly results.\r\n\r\n\r\n","Url":"https://github.com/jgthms/bulma/issues/3956","RelatedDescription":"Open issue \"Regression from 0.9.3: Background color for menu\" (#3956)"},{"Id":"2770645702","IsPullRequest":false,"CreatedAt":"2025-01-06T13:18:34","Actor":"sogorgeousman","Number":"3955","RawContent":null,"Title":"The project looks abandoned","State":"open","Body":"Unfortunately, I and the rest of the developers have the impression that the project has been abandoned. Well, **not exactly completely, but noticeably**. Many really important Issues have been waiting for a response for several weeks, acceptable pull requests have not received any feedback.\r\n\r\n#3761\r\n#3954 \r\n#3911\r\n#3886 and many, many other things that I also came across.\r\n\r\nWhy not try to find enthusiasts who are ready to further develop opensource? Or at least post lines in the readme that the project has moved into sluggish development, so that developers do not waste their time waiting for their issues to be resolved and pull requests accepted","Url":"https://github.com/jgthms/bulma/issues/3955","RelatedDescription":"Open issue \"The project looks abandoned\" (#3955)"},{"Id":"2766074344","IsPullRequest":false,"CreatedAt":"2025-01-02T13:54:11","Actor":"AbstractionsAs","Number":"3954","RawContent":null,"Title":"Navbar colors not working after upgrade to Bulma 1.0","State":"open","Body":"<!-- PLEASE READ THE FOLLOWING INSTRUCTIONS -->\r\n\r\n<!-- Choose one of the following: -->\r\nThis is about **Bulma**.\r\n\r\n### Overview of the problem\r\n\r\nAfter upgrading from Bulma 0.9.3 to Bulma 1.0, the navbar behaves differently in two important ways as soon as you add a color:\r\n\r\n1. The \"is-active\" modifier no longer has any visual effect\r\n2. The inverted text colors behave differently. Eg. when using primary, the labels are inverted to white in Bulma 0.9.3, but are black in Bulma 1\r\n\r\n### Steps to Reproduce\r\n\r\n1. Create a navbar\r\n2. Add a few \"navbar-item\"s \r\n3. Set one \"navbar-item\" to \"is-active\"\r\n\r\nAt this point, everything seems to work\r\n\r\n4. Add a color to the navbar, e.g. \"is-primary\"\r\n\r\n### Expected behavior\r\n\r\n1. The avtive item should be styled as active\r\n2. The text should be inverted\r\n\r\n### Actual behavior\r\n\r\n1. The active item is now indistingiushable from the rest\r\n2. The text is black\r\n","Url":"https://github.com/jgthms/bulma/issues/3954","RelatedDescription":"Open issue \"Navbar colors not working after upgrade to Bulma 1.0\" (#3954)"},{"Id":"2763712207","IsPullRequest":false,"CreatedAt":"2024-12-30T21:23:18","Actor":"NXTwoThou","Number":"3953","RawContent":null,"Title":"Styling select without div(\"selectnodiv\" suggestion/example)","State":"open","Body":"This is about Bulma feature suggestion.\r\n\r\n### Overview of the problem\r\nI'm using Bulma **version** [1.0.3]\r\n\r\n### Description\r\n\r\nCreate another class that may be used in place of having to wrap select in a div.\r\n\r\n`\r\n<div class=\"select\">\r\n    <select>\r\n        <option>One</option>\r\n    </select>\r\n</div>\r\n\r\n<select class=\"selectnodiv\">\r\n    <option>Two</option>\r\n</select>\r\n`\r\n\r\nDuring 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.\r\n\r\nI got around two issues with the following:\r\n\r\n`\r\n.select {\r\n    font-size: var(--bulma-control-size);\r\n}\r\n.selectnodiv {\r\n    @extend .select;\r\n    background-color: hsl(var(--bulma-input-h),var(--bulma-input-s),calc(var(--bulma-input-background-l) + var(--bulma-input-background-l-delta)));\r\n    color: hsl(var(--bulma-input-h),var(--bulma-input-s),var(--bulma-input-color-l));\r\n    border-color: var(--bulma-input-border-color);\r\n    border-radius: var(--bulma-input-radius);\r\n}\r\n`\r\n\r\nI 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.\r\n\r\nEven 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.","Url":"https://github.com/jgthms/bulma/issues/3953","RelatedDescription":"Open issue \"Styling select without div(\"selectnodiv\" suggestion/example)\" (#3953)"},{"Id":"2759942855","IsPullRequest":true,"CreatedAt":"2024-12-26T16:32:34","Actor":"Aic-02mz","Number":"3952","RawContent":null,"Title":"Remove outdated Ruby-Sass and Node-Sass dependencies","State":"open","Body":"# Remove outdated Ruby-Sass and Node-Sass dependencies\r\n\r\nThis pull request proposes the removal of outdated dependencies, specifically Ruby-Sass and Node-Sass, to improve the overall maintainability and performance of the repository. Both dependencies are no longer actively supported and  they are both out of  date\r\n\r\nKey Changes:\r\n\r\n<img width=\"631\" alt=\"img2\" src=\"https://github.com/user-attachments/assets/c3a4471d-b9ce-4cd6-9e1d-4719ced4aab9\" />\r\n\r\n\r\n## Removed Ruby-Sass and Node-Sass files:\r\n\r\nRemoved redundant files for the Sass test folder.\r\n\r\n##  Streamlined the test directory:\r\n\r\nThe test directory now only contains Dart-Sass, reducing clutter and complexity.\r\n\r\n## Resolved Node-Sass syntax issues:\r\n\r\nAdjustments have been made to eliminate deprecated syntax.\r\n\r\n## Rationale:\r\n\r\nBoth Ruby-Sass and Node-Sass are no longer actively supported.\r\n\r\nThe repository now fully aligns with modern standards by using Dart-Sass exclusively.\r\n\r\nThis change reduces potential maintenance in the future by removing outdated tools.\r\n\r\n## Testing:\r\n\r\nThis PR primarily involves the clean-up and reorganization of files. No testing was performed, as no new functionality or features were introduced.\r\n\r\n## Before and After:\r\nThe directory now focuses solely on Dart-Sass, which is the preferred and modern standard.\r\n\r\n## Changelog:\r\nNot needed, as this is a clean-up effort.\r\n\r\n## Additional Notes:\r\nThis aligns the repository with current best practices by removing unsupported tools and ensuring a cleaner structure. \r\n\r\n","Url":"https://github.com/jgthms/bulma/pull/3952","RelatedDescription":"Open PR \"Remove outdated Ruby-Sass and Node-Sass dependencies\" (#3952)"},{"Id":"2748804806","IsPullRequest":true,"CreatedAt":"2024-12-18T21:45:11","Actor":"bagedevimo","Number":"3950","RawContent":null,"Title":"Correct the syntax in hero is-bold colour variants","State":"open","Body":"While the prior syntax does produce valid css, it's not quite valid scss and so produces warnings in various pre and post-processing pipelines which various upstream consumers of Bulma may use.\r\n\r\n<!-- PLEASE READ THE FOLLOWING INSTRUCTIONS -->\r\n<!-- DO NOT REBUILD THE CSS OUTPUT IN YOUR PR -->\r\n\r\n<!-- Choose one of the following: -->\r\nThis is a **bugfix**.\r\n\r\n### Proposed solution\r\n\r\nBy using the correct scss syntax, we just prevent downstream warnings and errors, and make this file consistent with the rest of the bulma codebase., for example:\r\n\r\n```\r\n#30 114.5 WARNING in css/partner_portal-d7c813d1.css\r\n#30 114.5 css/partner_portal-d7c813d1.css from Css Minimizer plugin\r\n#30 114.5 postcss-calc:: Lexical error on line 1: Unrecognized text.\r\n#30 114.5 \r\n#30 114.5   Erroneous area:\r\n#30 114.5 1: var(--bulma-hero-h) - $hero-gradient-h-offset\r\n#30 114.5 ^........................^ webpack://./node_modules/bulma/sass/layout/hero.scss:146:12\r\n```\r\n\r\n### Testing Done\r\n\r\nGenerated css output has no difference before and after this change.\r\n\r\n### Changelog updated?\r\n\r\nNo.\r\n","Url":"https://github.com/jgthms/bulma/pull/3950","RelatedDescription":"Open PR \"Correct the syntax in hero is-bold colour variants\" (#3950)"},{"Id":"2740700673","IsPullRequest":false,"CreatedAt":"2024-12-16T04:51:47","Actor":"shohol07","Number":"3949","RawContent":null,"Title":"reload","State":"closed","Body":"<!-- PLEASE READ THE FOLLOWING INSTRUCTIONS -->\r\n\r\n<!-- Choose one of the following: -->\r\nThis is about **Bulma | the Docs**.\r\n\r\n<!-- Is it about Bulma or about the Docs? -->\r\n<!-- Is it a bug/feature/question or do you need help? -->\r\n<!-- If it's a bug, is it a browser bug? -->\r\n\r\n### Overview of the problem\r\n\r\n<!-- UNCOMMENT THE APPROPRIATE LINES -->\r\n\r\n<!-- This is about the Bulma **CSS framework** -->\r\n<!-- This is about the Bulma **Docs** -->\r\n<!-- I'm using Bulma **version** [x.x.x] -->\r\n<!-- My **browser** is: -->\r\n<!-- This is a **Sass** issue: I'm using version [x.x.x] -->\r\n<!-- I am sure this issue is **not a duplicate**? -->\r\n\r\n### Description\r\n\r\n<!-- Description of the bug, enhancement, or question -->\r\n\r\n### Steps to Reproduce\r\n\r\n<!--\r\n1. First Step\r\n2. Second Step\r\n3. and so on...\r\n-->\r\n\r\n### Expected behavior\r\n\r\n<!-- What you expected to happen -->\r\n\r\n### Actual behavior\r\n\r\n<!-- What actually happened -->\r\n","Url":"https://github.com/jgthms/bulma/issues/3949","RelatedDescription":"Closed issue \"reload\" (#3949)"},{"Id":"2736858993","IsPullRequest":false,"CreatedAt":"2024-12-12T20:51:53","Actor":"codyburleson","Number":"3948","RawContent":null,"Title":"SASS deprecation ","State":"open","Body":"This is about **Bulma**.\r\n\r\n### Overview of the problem\r\n\r\n<!-- UNCOMMENT THE APPROPRIATE LINES -->\r\n\r\nThis is about the Bulma **CSS framework**\r\n\r\nI'm using Bulma **version** 1.0.2\r\n\r\nThis is a **Sass** issue: I'm using sass version 1.77.6\r\n\r\nThere are similar open issues related to other versions of Bulma, but this is the only one for Bulma 1.0.2\r\n\r\n### Description\r\n\r\n```\r\nDeprecation Warning: Global built-in functions are deprecated and will be removed in Dart Sass 3.0.0.\r\nUse meta.type-of instead.\r\n\r\nMore info and automated migrator: https://sass-lang.com/d/import\r\n\r\n   ╷\r\n94 │   @if type-of($color) != \"color\" {\r\n   │       ^^^^^^^^^^^^^^^\r\n   ╵\r\n    node_modules/bulma/sass/utilities/functions.scss 94:7           bulmaColorLuminance()\r\n    node_modules/bulma/sass/utilities/functions.scss 128:7          bulmaFindColorInvert()\r\n    node_modules/bulma/sass/utilities/derived-variables.scss 16:15  @forward\r\n    node_modules/bulma/sass/utilities/_index.scss 6:1               @forward\r\n    node_modules/bulma/sass/_index.scss 1:1                         @use\r\n    src/assets/styles.scss 1:1                                      root stylesheet\r\n\r\nDeprecation Warning: Global built-in functions are deprecated and will be removed in Dart Sass 3.0.0.\r\nUse color.red instead.\r\n\r\nMore info and automated migrator: https://sass-lang.com/d/import\r\n\r\n   ╷\r\n99 │     \"red\": red($color),\r\n   │            ^^^^^^^^^^^\r\n   ╵\r\n    node_modules/bulma/sass/utilities/functions.scss 99:12          bulmaColorLuminance()\r\n    node_modules/bulma/sass/utilities/functions.scss 128:7          bulmaFindColorInvert()\r\n    node_modules/bulma/sass/utilities/derived-variables.scss 16:15  @forward\r\n    node_modules/bulma/sass/utilities/_index.scss 6:1               @forward\r\n    node_modules/bulma/sass/_index.scss 1:1                         @use\r\n    src/assets/styles.scss 1:1                                      root stylesheet\r\n\r\nDeprecation Warning: red() is deprecated. Suggestion:\r\n\r\ncolor.channel($color, \"red\", $space: rgb)\r\n\r\nMore info: https://sass-lang.com/d/color-functions\r\n\r\n   ╷\r\n99 │     \"red\": red($color),\r\n   │            ^^^^^^^^^^^\r\n   ╵\r\n    node_modules/bulma/sass/utilities/functions.scss 99:12          bulmaColorLuminance()\r\n    node_modules/bulma/sass/utilities/functions.scss 128:7          bulmaFindColorInvert()\r\n    node_modules/bulma/sass/utilities/derived-variables.scss 16:15  @forward\r\n    node_modules/bulma/sass/utilities/_index.scss 6:1               @forward\r\n    node_modules/bulma/sass/_index.scss 1:1                         @use\r\n    src/assets/styles.scss 1:1                                      root stylesheet\r\n\r\nDeprecation Warning: Global built-in functions are deprecated and will be removed in Dart Sass 3.0.0.\r\nUse color.green instead.\r\n\r\nMore info and automated migrator: https://sass-lang.com/d/import\r\n\r\n    ╷\r\n100 │     \"green\": green($color),\r\n    │              ^^^^^^^^^^^^^\r\n    ╵\r\n    node_modules/bulma/sass/utilities/functions.scss 100:14         bulmaColorLuminance()\r\n    node_modules/bulma/sass/utilities/functions.scss 128:7          bulmaFindColorInvert()\r\n    node_modules/bulma/sass/utilities/derived-variables.scss 16:15  @forward\r\n    node_modules/bulma/sass/utilities/_index.scss 6:1               @forward\r\n    node_modules/bulma/sass/_index.scss 1:1                         @use\r\n    src/assets/styles.scss 1:1                                      root stylesheet\r\n\r\nDeprecation Warning: green() is deprecated. Suggestion:\r\n\r\ncolor.channel($color, \"green\", $space: rgb)\r\n\r\nMore info: https://sass-lang.com/d/color-functions\r\n\r\n    ╷\r\n100 │     \"green\": green($color),\r\n    │              ^^^^^^^^^^^^^\r\n    ╵\r\n    node_modules/bulma/sass/utilities/functions.scss 100:14         bulmaColorLuminance()\r\n    node_modules/bulma/sass/utilities/functions.scss 128:7          bulmaFindColorInvert()\r\n    node_modules/bulma/sass/utilities/derived-variables.scss 16:15  @forward\r\n    node_modules/bulma/sass/utilities/_index.scss 6:1               @forward\r\n    node_modules/bulma/sass/_index.scss 1:1                         @use\r\n    src/assets/styles.scss 1:1                                      root stylesheet\r\n\r\nDeprecation Warning: Global built-in functions are deprecated and will be removed in Dart Sass 3.0.0.\r\nUse color.blue instead.\r\n\r\nMore info and automated migrator: https://sass-lang.com/d/import\r\n\r\n    ╷\r\n101 │     \"blue\": blue($color),\r\n    │             ^^^^^^^^^^^^\r\n    ╵\r\n    node_modules/bulma/sass/utilities/functions.scss 101:13         bulmaColorLuminance()\r\n    node_modules/bulma/sass/utilities/functions.scss 128:7          bulmaFindColorInvert()\r\n    node_modules/bulma/sass/utilities/derived-variables.scss 16:15  @forward\r\n    node_modules/bulma/sass/utilities/_index.scss 6:1               @forward\r\n    node_modules/bulma/sass/_index.scss 1:1                         @use\r\n    src/assets/styles.scss 1:1                                      root stylesheet\r\n\r\nDeprecation Warning: blue() is deprecated. Suggestion:\r\n\r\ncolor.channel($color, \"blue\", $space: rgb)\r\n\r\nMore info: https://sass-lang.com/d/color-functions\r\n\r\n    ╷\r\n101 │     \"blue\": blue($color),\r\n    │             ^^^^^^^^^^^^\r\n    ╵\r\n    node_modules/bulma/sass/utilities/functions.scss 101:13         bulmaColorLuminance()\r\n    node_modules/bulma/sass/utilities/functions.scss 128:7          bulmaFindColorInvert()\r\n    node_modules/bulma/sass/utilities/derived-variables.scss 16:15  @forward\r\n    node_modules/bulma/sass/utilities/_index.scss 6:1               @forward\r\n    node_modules/bulma/sass/_index.scss 1:1                         @use\r\n    src/assets/styles.scss 1:1                                      root stylesheet\r\n\r\nDeprecation Warning: Global built-in functions are deprecated and will be removed in Dart Sass 3.0.0.\r\nUse map.merge instead.\r\n\r\nMore info and automated migrator: https://sass-lang.com/d/import\r\n\r\n    ╷\r\n115 │       $color-rgb: map-merge(\r\n    │ ┌─────────────────^\r\n116 │ │       $color-rgb,\r\n117 │ │       (\r\n118 │ │         $name: $value,\r\n119 │ │       )\r\n120 │ │     );\r\n    │ └─────^\r\n    ╵\r\n    node_modules/bulma/sass/utilities/functions.scss 115:17         bulmaColorLuminance()\r\n    node_modules/bulma/sass/utilities/functions.scss 128:7          bulmaFindColorInvert()\r\n    node_modules/bulma/sass/utilities/derived-variables.scss 16:15  @forward\r\n    node_modules/bulma/sass/utilities/_index.scss 6:1               @forward\r\n    node_modules/bulma/sass/_index.scss 1:1                         @use\r\n    src/assets/styles.scss 1:1                                      root stylesheet\r\n\r\nDeprecation Warning: red() is deprecated. Suggestion:\r\n\r\ncolor.channel($color, \"red\", $space: rgb)\r\n\r\nMore info: https://sass-lang.com/d/color-functions\r\n\r\n   ╷\r\n51 │     (red($value), green($value), blue($value)),\r\n   │      ^^^^^^^^^^^\r\n   ╵\r\n    node_modules/bulma/sass/utilities/css-variables.scss 51:6   register-rgb()\r\n    node_modules/bulma/sass/utilities/css-variables.scss 130:3  register-base-color()\r\n    node_modules/bulma/sass/utilities/css-variables.scss 135:3  generate-basic-palette()\r\n    node_modules/bulma/sass/themes/light.scss 119:7             light-theme()\r\n    node_modules/bulma/sass/themes/_index.scss 11:3             @forward\r\n    node_modules/bulma/sass/_index.scss 2:1                     @use\r\n    src/assets/styles.scss 1:1                                  root stylesheet\r\n\r\nDeprecation Warning: green() is deprecated. Suggestion:\r\n\r\ncolor.channel($color, \"green\", $space: rgb)\r\n\r\nMore info: https://sass-lang.com/d/color-functions\r\n\r\n   ╷\r\n51 │     (red($value), green($value), blue($value)),\r\n   │                   ^^^^^^^^^^^^^\r\n   ╵\r\n    node_modules/bulma/sass/utilities/css-variables.scss 51:19  register-rgb()\r\n    node_modules/bulma/sass/utilities/css-variables.scss 130:3  register-base-color()\r\n    node_modules/bulma/sass/utilities/css-variables.scss 135:3  generate-basic-palette()\r\n    node_modules/bulma/sass/themes/light.scss 119:7             light-theme()\r\n    node_modules/bulma/sass/themes/_index.scss 11:3             @forward\r\n    node_modules/bulma/sass/_index.scss 2:1                     @use\r\n    src/assets/styles.scss 1:1                                  root stylesheet\r\n\r\nWarning: 124 repetitive deprecation warnings omitted.\r\n\r\n✓ 420 modules transformed.\r\nGenerated an empty chunk: \"common/common-typescript\".\r\n```","Url":"https://github.com/jgthms/bulma/issues/3948","RelatedDescription":"Open issue \"SASS deprecation \" (#3948)"},{"Id":"2728031799","IsPullRequest":false,"CreatedAt":"2024-12-09T19:22:18","Actor":"bartrylant","Number":"3947","RawContent":null,"Title":"Add my own variable?","State":"open","Body":"I can't find this anywhere in the docs. I have lots of ecperience with old school css and I just wanted to add a new variable myself. So I went to **utilities/initial-variables.scss**, added my new variable `family-trim` (with a value).\r\n\r\nAdded\r\n```\r\n.#{iv.$helpers-prefix}family-trim {\r\n  font-family: iv.$family-trim !important;\r\n}\r\n```\r\nto **helpers/typography.scss**\r\n\r\nAnd used\r\n```\r\nh1 {\r\n   font-family: cv.getVar(\"family-trim\");\r\n}\r\n```\r\nin **elements/content.scss**\r\nand compiled with dartsass.\r\n\r\nHowever, the css inspector for my h1 element says\r\n```\r\n.content h1  {\r\n    font-family: var(--bulma-family-trim);\r\n}\r\n```\r\n\r\nbut `--bulma-family-trim` is not defined. What did I forget or what did I do wrong?","Url":"https://github.com/jgthms/bulma/issues/3947","RelatedDescription":"Open issue \"Add my own variable?\" (#3947)"},{"Id":"2717781490","IsPullRequest":true,"CreatedAt":"2024-12-04T13:40:58","Actor":"mickverm","Number":"3946","RawContent":null,"Title":"Add $duration to initial-variables","State":"open","Body":"Fixes https://github.com/jgthms/bulma/issues/3945","Url":"https://github.com/jgthms/bulma/pull/3946","RelatedDescription":"Open PR \"Add $duration to initial-variables\" (#3946)"},{"Id":"2717763736","IsPullRequest":false,"CreatedAt":"2024-12-04T13:34:28","Actor":"mickverm","Number":"3945","RawContent":null,"Title":"Add $duration to initial-variables","State":"open","Body":"<!-- PLEASE READ THE FOLLOWING INSTRUCTIONS -->\r\n\r\n<!-- Choose one of the following: -->\r\nThis is about **Bulma**.\r\n\r\n### Overview of the problem\r\n\r\nI'm using Bulma **version** 1.0.2\r\nI am sure this issue is **not a duplicate**\r\n\r\n### Description\r\n\r\nDuration is not configurable via Sass variables.","Url":"https://github.com/jgthms/bulma/issues/3945","RelatedDescription":"Open issue \"Add $duration to initial-variables\" (#3945)"},{"Id":"2715986131","IsPullRequest":false,"CreatedAt":"2024-12-03T21:12:12","Actor":"davetapley","Number":"3944","RawContent":null,"Title":"Navbar broken for certain \"grid is-col-min-...\" and viewport combinations","State":"open","Body":"<!-- PLEASE READ THE FOLLOWING INSTRUCTIONS -->\r\n\r\n<!-- Choose one of the following: -->\r\nThis is about **Bulma**.\r\n\r\n<!-- Is it about Bulma or about the Docs? -->\r\n<!-- Is it a bug/feature/question or do you need help? -->\r\n<!-- If it's a bug, is it a browser bug? -->\r\n\r\n### Overview of the problem\r\n\r\n<!-- UNCOMMENT THE APPROPRIATE LINES -->\r\n\r\nThis is about the Bulma **CSS framework**\r\n<!-- This is about the Bulma **Docs** -->\r\nI'm using Bulma **version** [1.0.2]\r\nMy **browser** is:   Chromium: 131.0.6778.85 (Official Build) (x86_64]\r\n\r\n<!-- This is a **Sass** issue: I'm using version [x.x.x] -->\r\nI am sure this issue is **not a duplicate**\r\n\r\n### Description\r\n\r\nUse devtools set to responsive and observe navbar behaves strangely when narrowing the view port below 600px.\r\n\r\n\r\n### Steps to Reproduce\r\n\r\n```html\r\n<!DOCTYPE html>\r\n<html>\r\n  <head>\r\n    <meta charset=\"utf-8\" />\r\n    <meta name=\"viewport\" content=\"width=device-width, initial-scale=1\" />\r\n    <title>Hello Bulma!</title>\r\n    <link\r\n      rel=\"stylesheet\"\r\n      href=\"https://cdn.jsdelivr.net/npm/bulma@1.0.2/css/bulma.min.css\"\r\n    />\r\n  </head>\r\n  <body>\r\n    <nav class=\"navbar\" style=\"background-color: teal\">\r\n      <span class=\"navbar-item\">Hello Bulma!</span>\r\n    </nav>\r\n    <div class=\"section\">\r\n      <div class=\"grid is-col-min-24\">\r\n        <div class=\"cell\">\r\n          <div class=\"box\">cell one</div>\r\n        </div>\r\n        <div class=\"cell\">\r\n          <div class=\"box\">cell two</div>\r\n        </div>\r\n        <div class=\"cell\">\r\n          <div class=\"box\">cell three</div>\r\n        </div>\r\n      </div>\r\n    </div>\r\n  </body>\r\n</html>\r\n\r\n```\r\n\r\n### Expected behavior\r\n\r\nNavbar covers full width of viewport:\r\n\r\n<img width=\"859\" alt=\"Screenshot_12_3_24__2_08_PM\" src=\"https://github.com/user-attachments/assets/c1615d80-2197-46cc-bee6-1f1140d96c2f\">\r\n\r\n\r\n### Actual behavior\r\n\r\nBelow 600px it does not:\r\n\r\n<img width=\"617\" alt=\"Screenshot_12_3_24__2_07_PM\" src=\"https://github.com/user-attachments/assets/195dbeae-3053-4cfb-af2e-27aef17695ca\">\r\n\r\n","Url":"https://github.com/jgthms/bulma/issues/3944","RelatedDescription":"Open issue \"Navbar broken for certain \"grid is-col-min-...\" and viewport combinations\" (#3944)"},{"Id":"2711036104","IsPullRequest":false,"CreatedAt":"2024-12-02T08:44:28","Actor":"martinskou","Number":"3943","RawContent":null,"Title":"Lag using navbar in Firefox","State":"open","Body":"This is about **Bulma | Firefox.\r\n\r\nIs it a bug or do I need help? \r\n\r\n### Overview of the problem\r\n\r\nThis is about the Bulma **CSS framework**\r\nI'm using Bulma **version** [1.0.2]\r\nMy **browser** is: Firefox 134.0b3\r\n\r\n\r\n### Description\r\n\r\nWhen using the navbar component it experience lag / slowness in the browser response.\r\nEg. when i move the mouse over the navbar, the hover effect is slow to appear.\r\n\r\n### Steps to Reproduce\r\n\r\nUse a navbar \r\n\r\n### Expected behavior\r\n\r\nAlways snappy behaviour.\r\n\r\n### Actual behavior\r\n\r\nMost of the time snappy, but sometimes laggy.\r\n\r\n### Firefox issue\r\n\r\nLooks like a Firefox bug:\r\n\r\nhttps://bugzilla.mozilla.org/show_bug.cgi?id=1926626\r\n\r\n\r\n","Url":"https://github.com/jgthms/bulma/issues/3943","RelatedDescription":"Open issue \"Lag using navbar in Firefox\" (#3943)"},{"Id":"2704883002","IsPullRequest":false,"CreatedAt":"2024-11-29T18:33:01","Actor":"francesco-loreti","Number":"3942","RawContent":null,"Title":"[bulma@^1.0.2 Deprecation Warning] Global built-in functions are deprecated and will be removed in Dart Sass 3.0.0.","State":"closed","Body":"bulma@^1.0.2\r\n\r\n```\r\nDeprecation Warning: Global built-in functions are deprecated and will be removed in Dart Sass 3.0.0.\r\nUse meta.type-of instead.\r\nMore info and automated migrator: https://sass-lang.com/d/import\r\n\r\nDeprecation Warning: blue() is deprecated. Suggestion: color.channel($color, \"blue\", $space: rgb)\r\nDeprecation Warning: red() is deprecated. Suggestion: color.channel($color, \"red\", $space: rgb)\r\nDeprecation Warning: green() is deprecated. Suggestion: color.channel($color, \"green\", $space: rgb)\r\n\r\nDeprecation Warning: Global built-in functions are deprecated and will be removed in Dart Sass 3.0.0.\r\nUse map.merge instead.\r\n\r\n$color-rgb: map-merge(\r\n    │ ┌─────────────────^\r\n116 │ │       $color-rgb,\r\n117 │ │       (\r\n118 │ │         $name: $value,\r\n119 │ │       )\r\n120 │ │     );\r\n    │ └─────^\r\n    ╵\r\n    node_modules\\bulma\\sass\\utilities\\functions.scss 115:17\r\n```","Url":"https://github.com/jgthms/bulma/issues/3942","RelatedDescription":"Closed issue \"[bulma@^1.0.2 Deprecation Warning] Global built-in functions are deprecated and will be removed in Dart Sass 3.0.0.\" (#3942)"},{"Id":"2687776226","IsPullRequest":false,"CreatedAt":"2024-11-28T02:53:00","Actor":"benjamin-dreux","Number":"3939","RawContent":null,"Title":"Checkbox spacing depends on whitespace","State":"closed","Body":"Here is an exemple of what checbox looks without whitespace (in a trimmed html)\r\n\r\n![image](https://github.com/user-attachments/assets/5b2d53c4-0684-4655-9016-e384d2def03a)\r\n\r\nHere is the code attached to id\r\n\r\n<div class=\"field\"><div class=\"control\"><label class=\"checkbox\"><input type=\"checkbox\" name=\"isOrganization\" class=\"checkbox\">Is organization</label></div></div>\r\n\r\nBut as soon as you create white space arround elements like so\r\n\r\n<div class=\"field\">\r\n  <div class=\"control\">\r\n    <label class=\"checkbox\">\r\n      <input type=\"checkbox\" name=\"isOrganization\" class=\"checkbox\">\r\n      Is organization\r\n    </label>\r\n  </div>\r\n</div>\r\n\r\nThen checkbox looks as nice as the documentation\r\n\r\n![image](https://github.com/user-attachments/assets/aed0b6be-7656-4c32-bfa4-6fee0c8c5f82)\r\n\r\nIf your html is generated without empty space that not that cool","Url":"https://github.com/jgthms/bulma/issues/3939","RelatedDescription":"Closed issue \"Checkbox spacing depends on whitespace\" (#3939)"},{"Id":"2624514573","IsPullRequest":true,"CreatedAt":"2024-11-27T16:11:11","Actor":"jnoordsij","Number":"3930","RawContent":null,"Title":"Update various references from master to main brach","State":"closed","Body":"<!-- PLEASE READ THE FOLLOWING INSTRUCTIONS -->\r\n<!-- DO NOT REBUILD THE CSS OUTPUT IN YOUR PR -->\r\n\r\n<!-- Choose one of the following: -->\r\nThis is a **new feature | improvement | bugfix | documentation fix**.\r\n<!-- New feature? Update the CHANGELOG.md too, and eventually the Docs. -->\r\n<!-- Improvement? Explain how and why. -->\r\n<!-- Bugfix? Reference that issue as well. -->\r\n\r\n### Proposed solution\r\n\r\nWhen checking some things when preparing another MR, I noticed some links were out-of-date.\r\nThis MR updates various references from `master` to `main`, given that seems to be the new default branch now.\r\n\r\nNote: https://github.com/jgthms/bulma/blob/main/docs/documentation/start/responsiveness.html still has some `master` references too; these might need to be revised in some way too.\r\n\r\n### Tradeoffs\r\n\r\nN/A\r\n\r\n### Testing Done\r\n\r\nNone.\r\n\r\n<!-- BEFORE SUBMITTING YOUR PR, MAKE SURE TO FOLLOW THESE STEPS: -->\r\n<!-- 1. Pull the latest `master` branch -->\r\n<!-- 2. Make sure your Sass code is compliant with the [Bulma Sass styleguide](https://github.com/jgthms/bulma/blob/master/.github/CONTRIBUTING.md#bulma-sass-styleguide) -->\r\n<!-- 3. Make sure your PR only affects `.sass` or documentation files -->\r\n<!-- 4. [Try your changes](https://github.com/jgthms/bulma/blob/master/.github/CONTRIBUTING.md#try-your-changes). -->\r\n\r\n<!-- How have you confirmed this feature works? -->\r\n<!-- Please explain more than \"Yes\". -->\r\n\r\n### Changelog updated?\r\n\r\nNo.\r\n\r\n<!-- Thanks! -->\r\n","Url":"https://github.com/jgthms/bulma/pull/3930","RelatedDescription":"Closed or merged PR \"Update various references from master to main brach\" (#3930)"},{"Id":"2688027696","IsPullRequest":true,"CreatedAt":"2024-11-27T15:47:28","Actor":"SomethingNew71","Number":"3940","RawContent":null,"Title":"Updates deprecated round functions in Sass Build","State":"closed","Body":"<!-- PLEASE READ THE FOLLOWING INSTRUCTIONS -->\r\n<!-- DO NOT REBUILD THE CSS OUTPUT IN YOUR PR -->\r\n\r\n<!-- Choose one of the following: -->\r\nThis is a **bugfix**.\r\n<!-- New feature? Update the CHANGELOG.md too, and eventually the Docs. -->\r\n<!-- Improvement? Explain how and why. -->\r\n<!-- Bugfix? Reference that issue as well. -->\r\n\r\n### Proposed solution\r\n\r\nFixes some of the errors related to #3907 \r\n\r\n### Testing Done\r\n\r\nNone.\r\n\r\n<!-- BEFORE SUBMITTING YOUR PR, MAKE SURE TO FOLLOW THESE STEPS: -->\r\n<!-- 1. Pull the latest `master` branch -->\r\n<!-- 2. Make sure your Sass code is compliant with the [Bulma Sass styleguide](https://github.com/jgthms/bulma/blob/master/.github/CONTRIBUTING.md#bulma-sass-styleguide) -->\r\n<!-- 3. Make sure your PR only affects `.sass` or documentation files -->\r\n<!-- 4. [Try your changes](https://github.com/jgthms/bulma/blob/master/.github/CONTRIBUTING.md#try-your-changes). -->\r\n\r\n<!-- How have you confirmed this feature works? -->\r\n<!-- Please explain more than \"Yes\". -->\r\n\r\n### Changelog updated?\r\n\r\nNo.\r\n\r\n<!-- Thanks! -->\r\n","Url":"https://github.com/jgthms/bulma/pull/3940","RelatedDescription":"Closed or merged PR \"Updates deprecated round functions in Sass Build\" (#3940)"},{"Id":"2694397955","IsPullRequest":false,"CreatedAt":"2024-11-26T11:52:29","Actor":"apomili","Number":"3941","RawContent":null,"Title":"Section hidden native style is overridden by base/generic","State":"open","Body":"\r\nThis is about **Bulma**.\r\n\r\n\r\n### Overview of the problem\r\n\r\n<!-- UNCOMMENT THE APPROPRIATE LINES -->\r\n\r\n<!-- This is about the Bulma **CSS framework** -->\r\n I'm using Bulma **1.0.2** \r\n My **browser** is: **Chrome**\r\n\r\n### Description\r\n\r\nThe native style of `<section hidden>` is overridden by base/generic.scss\r\n\r\n### Steps to Reproduce\r\n\r\n1. Set on a page a tag section with an hidden attribute like ` <section hidden></section>`\r\n2. Add bulma style with `@use \"bulma/sass/base \"`\r\n3. Inspect console on that tag\r\n\r\n\r\n### Expected behavior\r\n\r\nThe section should have\r\n\r\n```\r\nsection[Attributes Style] {\r\n    display: none;\r\n}\r\n```\r\n\r\n### Actual behavior\r\n\r\nThe section get\r\n\r\n```\r\narticle, aside, figure, footer, header, hgroup, section {\r\n    display: block;\r\n}\r\n```\r\n","Url":"https://github.com/jgthms/bulma/issues/3941","RelatedDescription":"Open issue \"Section hidden native style is overridden by base/generic\" (#3941)"},{"Id":"2681438600","IsPullRequest":false,"CreatedAt":"2024-11-22T00:50:42","Actor":"Kehino","Number":"3938","RawContent":null,"Title":"Inconsistent spacing under form elements","State":"open","Body":"<!-- PLEASE READ THE FOLLOWING INSTRUCTIONS -->\r\n\r\n<!-- Choose one of the following: -->\r\nThis is about **Bulma**. It is a feature request about a behavior that could be considered a bug.\r\n\r\n### Overview of the problem\r\n\r\n<!-- UNCOMMENT THE APPROPRIATE LINES -->\r\n\r\nThis is about the Bulma **CSS framework**\r\n<!-- This is about the Bulma **Docs** -->\r\nI'm using Bulma **version** 1.0.2\r\n<!-- My **browser** is: -->\r\n<!-- This is a **Sass** issue: I'm using version [x.x.x] -->\r\nI am sure this issue is **not a duplicate**.\r\n\r\n### Description\r\n\r\n<!-- Description of the bug, enhancement, or question -->\r\n\r\n![Screenshot 2024-11-22 at 00-46-55 Hello Bulma!](https://github.com/user-attachments/assets/5db171f0-a372-40de-b383-2bf13e1e2d08)\r\n\r\n![Screenshot 2024-11-22 at 00-46-47 Hello Bulma!](https://github.com/user-attachments/assets/f215e296-9993-4f8f-941d-017a7c5fe8c1)\r\n\r\nThe top spacing of the `help` after nested `field`s within a `field` should be identical to the spacing under a `control`.\r\n\r\n### Steps to Reproduce\r\n\r\n<details><summary>Full example</summary>\r\n<p>\r\n\r\n```html\r\n    <div class=\"field\">\r\n    <label class=\"label\">Numéro de téléphone</label>\r\n    <div class=\"control\">\r\n        <input class=\"input\" type=\"tel\" placeholder=\"Numéro de téléphone\" />\r\n    </div>\r\n    <p class=\"help\">Si votre numéro n'est pas un numéro français (+33), précisez l'indicatif. Celui-ci est uniquement utilisé pour la livraison.</p>\r\n    </div>\r\n    <div class=\"field\">\r\n    <label class=\"label\">Dimensions</label>\r\n    <div class=\"field is-grouped\">\r\n        <div class=\"control is-expanded\">\r\n            <div class=\"field has-addons\">\r\n                <div class=\"control\">\r\n                    <a class=\"button is-static\">\r\n                    Hauteur\r\n                    </a>\r\n                </div>\r\n                <div class=\"control is-expanded\">\r\n                    <input class=\"input\" type=\"text\" value=\"56\" />\r\n                </div>\r\n                <div class=\"control\">\r\n                    <a class=\"button is-static\">\r\n                    mm\r\n                    </a>\r\n                </div>\r\n            </div>\r\n        </div>\r\n        <div class=\"control is-expanded\">\r\n        <div class=\"field has-addons\">\r\n            <div class=\"control\">\r\n                <a class=\"button is-static\">\r\n                Largeur\r\n                </a>\r\n            </div>\r\n            <div class=\"control is-expanded\">\r\n                <input class=\"input\" type=\"text\" value=\"56\" />\r\n            </div>\r\n            <div class=\"control\">\r\n                <a class=\"button is-static\">\r\n                mm\r\n                </a>\r\n            </div>\r\n        </div>\r\n        </div>\r\n        <div class=\"control is-expanded\">\r\n        <div class=\"field has-addons\">\r\n            <div class=\"control\">\r\n                <a class=\"button is-static\">\r\n                Longueur\r\n                </a>\r\n            </div>\r\n            <div class=\"control is-expanded\">\r\n                <input class=\"input\" type=\"text\" value=\"56\" />\r\n            </div>\r\n            <div class=\"control\">\r\n                <a class=\"button is-static\">\r\n                mm\r\n                </a>\r\n            </div>\r\n        </div>\r\n        </div>\r\n    </div>\r\n    <p class=\"help\">Les valeurs des trois champs sont liées: lorsque l'une est changée, les autres sont recalculées.</p>\r\n    </div>\r\n``` \r\n\r\n</p>\r\n</details> \r\n\r\n### Expected behavior\r\n\r\nThe top spacing of the `help` after nested `field`s within a `field` should be identical to the spacing under a `control`. This is because these nested `field`s are meant (IMO) as helpers (for `has-addons` or `is-grouped`) and not as spacers in that case.\r\n\r\n### Actual behavior\r\n\r\nThe top spacing of the `help` after nested `field`s within a `field` is currently the one after any `field`.\r\n\r\n### Fix\r\n\r\n(actually not tested...)\r\n\r\n```scss\r\n.field {\r\n    .control + .help, .field + .help {\r\n         padding: var(--bulma-control-padding-vertical); \r\n    }\r\n}\r\n```\r\n","Url":"https://github.com/jgthms/bulma/issues/3938","RelatedDescription":"Open issue \"Inconsistent spacing under form elements\" (#3938)"},{"Id":"2681150031","IsPullRequest":true,"CreatedAt":"2024-11-21T22:31:04","Actor":"brendon","Number":"3937","RawContent":null,"Title":"Add .has-text-weight-extrabold","State":"open","Body":"This is an improvement.\r\n\r\nWe have a variable for `extrabold` font weight so it makes sense to have the typography utility class to use also. \r\n\r\n### Testing Done\r\n\r\nNone.\r\n\r\n### Changelog updated?\r\n\r\nYes.","Url":"https://github.com/jgthms/bulma/pull/3937","RelatedDescription":"Open PR \"Add .has-text-weight-extrabold\" (#3937)"},{"Id":"2673561663","IsPullRequest":false,"CreatedAt":"2024-11-19T21:16:22","Actor":"ragonneau","Number":"3936","RawContent":null,"Title":"`navbar-item` for `<button>`","State":"open","Body":"This is about **Bulma**.\r\n\r\n### Overview of the problem\r\n\r\nThis is about the Bulma **CSS framework**\r\nI am sure this issue is **not a duplicate**\r\n\r\n### Description\r\n\r\nFirst, thank you very much for the framework, very useful !\r\n\r\nThe `navbar-item` class is implemented for `<a>` and `<div>` but not for `<button>`. This would be a great feature, because it is common to have a logout button in a dropdown in the navigation bar, which is generally a POST.\r\n\r\n### Steps to Reproduce\r\n\r\nI give here an example of a navbar with a logout button in a dropdown.\r\n\r\n```html\r\n<nav class=\"navbar is-fixed-top\">\r\n    <div class=\"navbar-brand\">\r\n        <a class=\"navbar-item\" href=\"#\">\r\n            <strong>\r\n                My project\r\n            </strong>\r\n        </a>\r\n        <a role=\"button\" class=\"navbar-burger\" aria-label=\"menu\" aria-expanded=\"false\" data-target=\"navbarMenu\">\r\n            <span aria-hidden=\"true\"></span>\r\n            <span aria-hidden=\"true\"></span>\r\n            <span aria-hidden=\"true\"></span>\r\n            <span aria-hidden=\"true\"></span>\r\n        </a>\r\n    </div>\r\n    <div id=\"navbarMenu\" class=\"navbar-menu\">\r\n        <div class=\"navbar-end\">\r\n            <div class=\"navbar-item has-dropdown\">\r\n                <a class=\"navbar-link\">\r\n                    Welcome user\r\n                </a>\r\n                <div class=\"navbar-dropdown is-right\">\r\n                    <a class=\"navbar-item\">\r\n                        About\r\n                    </a>\r\n                    <hr class=\"navbar-divider\">\r\n                    <form action=\"...\" method=\"post\">\r\n                        <button type=\"submit\" class=\"navbar-item\">\r\n                            Logout\r\n                        </button>\r\n                    </form>\r\n                </div>\r\n            </div>\r\n        </div>\r\n    </div>\r\n</nav>\r\n```\r\n\r\n### Expected behavior\r\n\r\nFrom a user perspective, the \"About\" and \"Logout\" items in the dropdown should render exactly the same way.\r\n\r\n### Actual behavior\r\n\r\nThe placement, padding, etc, works fine, but the over effect is not working for the \"Logout\" button.\r\n","Url":"https://github.com/jgthms/bulma/issues/3936","RelatedDescription":"Open issue \"`navbar-item` for `<button>`\" (#3936)"},{"Id":"2617331511","IsPullRequest":false,"CreatedAt":"2024-11-11T10:32:11","Actor":"simonw","Number":"3926","RawContent":null,"Title":"Documentation heading looks bad at 1016px wide","State":"closed","Body":"### Overview of the problem\r\n\r\nThis is about the Bulma **Docs**\r\n\r\nMy **browser** is: Firefox on macOS\r\n\r\n### Description\r\n\r\n![CleanShot 2024-10-27 at 22 18 43@2x](https://github.com/user-attachments/assets/d89779d8-8cb4-44bf-8390-71088966e262)\r\n\r\n### Steps to Reproduce\r\n\r\nResize browser to around 1016px wide, visit https://bulma.io/documentation/","Url":"https://github.com/jgthms/bulma/issues/3926","RelatedDescription":"Closed issue \"Documentation heading looks bad at 1016px wide\" (#3926)"},{"Id":"2646272903","IsPullRequest":false,"CreatedAt":"2024-11-09T16:29:34","Actor":"benjamin-dreux","Number":"3935","RawContent":null,"Title":"input field with has-addons doesn't play nice with labels","State":"open","Body":"<!-- PLEASE READ THE FOLLOWING INSTRUCTIONS -->\r\n\r\n<!-- Choose one of the following: -->\r\nThis is about **Bulma | the Docs**.\r\n\r\n<!-- Is it about Bulma or about the Docs? -->\r\n<!-- Is it a bug/feature/question or do you need help? -->\r\n<!-- If it's a bug, is it a browser bug? -->\r\n\r\nIt's a bug that doesn't tie to a specific bowser. It can be reproduce with chrome or firefox.\r\n\r\n### Overview of the problem\r\n\r\n<!-- UNCOMMENT THE APPROPRIATE LINES -->\r\n\r\nThis is about the Bulma **CSS framework** \r\n<!-- This is about the Bulma **Docs** -->\r\n<!-- I'm using Bulma **version** [x.x.x] -->\r\n<!-- My **browser** is: -->\r\n<!-- This is a **Sass** issue: I'm using version [x.x.x] -->\r\n<!-- I am sure this issue is **not a duplicate**? -->\r\n\r\n### Description\r\n\r\nWhen creating a form field that has an addons, the controls are put on the same line as the label itself, even if the labels of this form are supposed to be one line upper.\r\n\r\n### Steps to Reproduce\r\n\r\n\r\n```\r\n<form class=\"form\">\r\n  <div class =\"field has-addons\">\r\n    <label class =\"label\">Requested amount</label>\r\n    <p class=\"control\">\r\n      <span class=\"select\">\r\n        <select>\r\n          <option>$</option>\r\n          <option>£</option>\r\n          <option>€</option>\r\n        </select>\r\n      </span>\r\n    </p>\r\n    <p class=\"control\">\r\n      <input class=\"input\" type=\"text\" placeholder=\"Amount of money\">\r\n    </p>\r\n    <p class=\"control\">\r\n      <button class=\"button\">\r\n        Transfer\r\n      </button>\r\n    </p>\r\n  </div>\r\n</form>\r\n```\r\n### Expected behavior\r\n\r\nlabel should be on a distinct line than the inputs by them self\r\n\r\n### Actual behavior\r\n\r\n![image](https://github.com/user-attachments/assets/9f56c3e1-c8d1-4cf4-adf7-a925112b4738)\r\n","Url":"https://github.com/jgthms/bulma/issues/3935","RelatedDescription":"Open issue \"input field with has-addons doesn't play nice with labels\" (#3935)"},{"Id":"2635786749","IsPullRequest":false,"CreatedAt":"2024-11-05T15:31:57","Actor":"Aic-02mz","Number":"3934","RawContent":null,"Title":"Out of date Sass","State":"open","Body":"Removing Ruby Sass and Node Sass. \r\n\r\nThese are both end-of-life and no longer supported.\r\n\r\nDeleting them from the Test Folder and other areas where they are used, would make it easier to read and interpret this GitHub repo. \r\n\r\n<img width=\"296\" alt=\"o \" src=\"https://github.com/user-attachments/assets/f27fb2ec-0ba7-47f7-89ca-984c068a9124\">\r\n<img width=\"403\" alt=\"o  2\" src=\"https://github.com/user-attachments/assets/d64ae0b0-7b5e-4f04-8111-166ffc97ab82\">\r\n\r\n\r\nHere =\r\n<img width=\"616\" alt=\"o  2\" src=\"https://github.com/user-attachments/assets/b9746d94-c5ff-47b9-8d8a-e0e65007b3bf\">\r\n","Url":"https://github.com/jgthms/bulma/issues/3934","RelatedDescription":"Open issue \"Out of date Sass\" (#3934)"},{"Id":"2633245187","IsPullRequest":false,"CreatedAt":"2024-11-04T16:16:25","Actor":"Mario8419","Number":"3933","RawContent":null,"Title":"Update from 0.9.3 to v1 issue","State":"open","Body":"Hello,\r\n\r\nI just updated Bulma from version 0.9.3 to v1.0.0 in my React/Gatsby application. I followed the documentation but am facing several issues. My project uses a .sass file to import and customize Bulma, with \"sass\": \"^1.69.7\".\r\n\r\nHere's my all.sass file:\r\n\r\nsass\r\n@import \"~bulma/sass/utilities/initial-variables\"\r\n\r\n$brand: #2cd1b8\r\n$brand-invert: #fff\r\n$primary: $brand\r\n$family-primary: 'Montserrat'\r\n\r\n// Other custom styles...\r\n\r\n@import \"~bulma\"  // Following the docs, this might not be needed in v1?\r\n\r\nProblems Encountered:\r\n\r\nFor e.g. the custom $family-primary (Montserrat) is not being applied.\r\nSeveral other custom styles, which worked perfectly in version 0.9.3, seem broken or are not being applied at all, for example, button sizes and so on\r\n\r\n\r\nSteps to Reproduce:\r\n\r\nUse the all.sass file as shown above.\r\nRun the project in a React/Gatsby environment.\r\nExpected Behavior:\r\n\r\nCustom styles should work as defined in the .sass file, including the $family-primary.\r\nCurrent Behavior:\r\n\r\nDefault Bulma styles are overriding my custom styles.\r\nFont family and other styles defined via Sass variables are not being applied.\r\nEnvironment:\r\n\r\nBulma version: 1.0.0\r\nSass version: 1.69.7\r\nFramework: React/Gatsby\r\nAdditional Context:\r\n\r\nEverything worked fine with Bulma 0.9.3.\r\nI've gone through the migration guide but couldn't resolve these issues.\r\nAny help or guidance would be appreciated. Thank you!","Url":"https://github.com/jgthms/bulma/issues/3933","RelatedDescription":"Open issue \"Update from 0.9.3 to v1 issue\" (#3933)"},{"Id":"2628740686","IsPullRequest":false,"CreatedAt":"2024-11-01T10:05:37","Actor":"rnkpplr","Number":"3932","RawContent":null,"Title":"Incorrect value for `one-third selectors` e.g.  .columns.is-mobile > .column.is-offset-one-third ","State":"open","Body":"https://github.com/jgthms/bulma/blob/3b63997ad2c614ce438145063833e4b162350852/sass/grid/columns.scss#L108\r\nIf I'm not wrong, `margin-inline-start: 33.3333%;` should be here instead of `margin-inline-start: 0.3333%;` ? And there are a few more `on-third` selectors in the file, which have a value of `0.3333%`\r\n","Url":"https://github.com/jgthms/bulma/issues/3932","RelatedDescription":"Open issue \"Incorrect value for `one-third selectors` e.g.  .columns.is-mobile > .column.is-offset-one-third \" (#3932)"},{"Id":"2624535725","IsPullRequest":true,"CreatedAt":"2024-10-30T15:48:23","Actor":"jnoordsij","Number":"3931","RawContent":null,"Title":"Remove vendor prefixes from sass","State":"open","Body":"<!-- PLEASE READ THE FOLLOWING INSTRUCTIONS -->\r\n<!-- DO NOT REBUILD THE CSS OUTPUT IN YOUR PR -->\r\n\r\n<!-- Choose one of the following: -->\r\nThis is a **new feature | improvement | bugfix | documentation fix**.\r\n<!-- New feature? Update the CHANGELOG.md too, and eventually the Docs. -->\r\n<!-- Improvement? Explain how and why. -->\r\n<!-- Bugfix? Reference that issue as well. -->\r\n\r\n### Proposed solution\r\n\r\nWhen debugging some other issues with placeholders in my application, I noticed some vendor prefixes popping up on attributes where I did not expect them. Then I figured that they are actually hardcoded within the scope of this repository, rather than applied by tooling (e.g. `autoprefixer`).\r\n\r\n*Edit:* for the `::placeholder` mixin, it was actually rendering all the variants *except* for the correct modern `::placeholder` pseudo-element, so this actually might ensure proper behavior across environments that previously did not work.\r\n\r\nThis PR removes the hardcoded vendor-prefixed variants of some properties. The preferred way (I think) should be using tooling to handle this. Although the `README` mentions that `autoprefixer` is used within this repository, it seems it has since been replaced with `cssnano`, which may not include it by default.\r\n\r\nProbably this requires rebuilding `css` too, however the `npm run build` alias mentioned in `CONTRIBUTING.md` no longer exists, so I'm not sure which parts are intended to run on MR submissions.\r\n\r\nNote: I encountered this issue on version `v0.9.4`, but I'm not sure if bugfixes are still welcome for the old version?\r\n\r\n### Tradeoffs\r\n\r\nTheoretically this could cause a change of behavior on legacy browsers. Given the wide availability of the non-prefixed alternatives and the fact that tooling like `autoprefixer` is commonly used, I suspect this will have little to no impact in that regard.\r\n\r\n### Testing Done\r\n\r\nNone.\r\n\r\n<!-- BEFORE SUBMITTING YOUR PR, MAKE SURE TO FOLLOW THESE STEPS: -->\r\n<!-- 1. Pull the latest `master` branch -->\r\n<!-- 2. Make sure your Sass code is compliant with the [Bulma Sass styleguide](https://github.com/jgthms/bulma/blob/master/.github/CONTRIBUTING.md#bulma-sass-styleguide) -->\r\n<!-- 3. Make sure your PR only affects `.sass` or documentation files -->\r\n<!-- 4. [Try your changes](https://github.com/jgthms/bulma/blob/master/.github/CONTRIBUTING.md#try-your-changes). -->\r\n\r\n<!-- How have you confirmed this feature works? -->\r\n<!-- Please explain more than \"Yes\". -->\r\n\r\n### Changelog updated?\r\n\r\nNo.\r\n\r\n<!-- Thanks! -->\r\n","Url":"https://github.com/jgthms/bulma/pull/3931","RelatedDescription":"Open PR \"Remove vendor prefixes from sass\" (#3931)"},{"Id":"2618866991","IsPullRequest":false,"CreatedAt":"2024-10-28T16:07:10","Actor":"kLOsk","Number":"3927","RawContent":null,"Title":"Does Bulma SASS really takes 12s to compile with DART SASS and Gulp?","State":"open","Body":"<!-- PLEASE READ THE FOLLOWING INSTRUCTIONS -->\r\n\r\n<!-- Choose one of the following: -->\r\nThis is about **Bulma**.\r\n\r\n<!-- Is it about Bulma or about the Docs? -->\r\n<!-- Is it a bug/feature/question or do you need help? -->\r\n<!-- If it's a bug, is it a browser bug? -->\r\n\r\n### Overview of the problem\r\n\r\n<!-- UNCOMMENT THE APPROPRIATE LINES -->\r\nThis is about the Bulma **CSS framework**\r\n<!-- This is about the Bulma **Docs** -->\r\nI'm using Bulma **version** [1.0.2]\r\n<!-- My **browser** is: -->\r\nThis is a **Sass** issue: I'm using version [1.58.1]\r\nI am sure this issue is **not a duplicate**\r\n\r\n### Description\r\n\r\n<!-- Description of the bug, enhancement, or question -->\r\n\r\nI'm using Gulp with Bulma and DART SASS. I tried multiple DART SASS versions, but they all end up equally slow, about 12s to compile. I'm working with an i9 MacBook Pro. I would just like a confirmation that this is normal or ideally some advice if this is not normal, what I can do to speed it up? I'm aware of having the option to load fewer modules, but even with fewer modules it still seems very slow. The slow taks in gulp is always the style compilation\r\n\r\n```\r\n[17:00:40] Starting 'styles'...\r\n[Browsersync] 2 files changed (main.css.map, main.css)\r\n[17:00:52] Finished 'styles' after 12 s\r\n[17:06:42] Starting 'styles'...\r\n[Browsersync] 2 files changed (main.css.map, main.css)\r\n[17:06:54] Finished 'styles' after 12 s\r\n```\r\n\r\nThanks\r\n","Url":"https://github.com/jgthms/bulma/issues/3927","RelatedDescription":"Open issue \"Does Bulma SASS really takes 12s to compile with DART SASS and Gulp?\" (#3927)"}],"ResultType":"GitHubIssue"}},"RunOn":"2025-01-11T03:30:10.5995348Z","RunDurationInMilliseconds":410}
\ No newline at end of file