Add extra classes to min-vh-*

[pythonistical]

Prerequisites

• [X] I have searched for duplicate or closed feature requests
• [X] I have read the contributing guidelines

Proposal

Increase the scope of class min-vh-*. From only having min-vh-100, it should also include-

• min-vh-75
• min-vh-50
• min-vh-25

Motivation and context

The inadequacy of the min-vh-* class is reflected in this Stack Overflow question-https://stackoverflow.com/questions/78636386/min-vh-50-is-not-behaving-as-expected-in-bootstrap-css Ultimately the answer was given in the comments which concluded that Bootstrap doesn't define min-vh-50.

The motivation behind this change is to avoid the alignment problems and confusion that can occur without these classes as demonstrated above.

[julien-deramond]

This topic has been partially discussed in several previous issues, such as issue #29697 and issue #29488. While these issues aren't exactly the same, they are in a similar vein. At that time, the decision was made not to include this feature in the framework.

I'll defer to @mdo, who has more historical context on this matter, to decide whether we should close this feature request.

In the meantime, without adding this to the framework by default, you can define the missing classes using our Utility API.

$utilities: map-merge(
  $utilities,
  (
    "min-viewport-height":
    (
      property: min-height,
      class: min-vh,
      values: (25: 25vh, 50: 50vh, 75: 75vh)
    ) 
  )
);

It will generate the missing classes mentioned in the description of this issue:

.min-vh-25 {
  min-height: 25vh !important;
}
.min-vh-50 {
  min-height: 50vh !important;
}
.min-vh-75 {
  min-height: 75vh !important;
}

[pythonistical]

@mdo @julien-deramond I have noticed, that the same excuse was given in all such feature requests that 'not enough people have requested it', the same reason is once again despite even a SO issue stemming from this. I think the feature should be added to the core as it's not as rare as we think.