Skip to main content

SASS Mixin for Creating CSS Triangles

I feel like one of the most common shapes that we can reliably create with CSS vs images is the triangle.

One of the reasons for this is that it works as far back as IE7 (IE6 works, but doesn't support background-color: transparent). Another is how frequently a little triangle icon can be used (e.g., ascending/descending buttons, expanding menus, open/close state, etc.)

I'm not going to cover the techniques of creating triangles with CSS. That's been done already, and probably better than I would do it.

What I'm going to share with you, is a little SASS mixin that I've been using to generate triangles.

See the Pen SASS Triangles by Thomas Pietrosanti (@Rykus0) on CodePen.

I'm using a SASS placeholder (%triangle-base) as a base to contain the common styles. This makes it easy to extend without generating tons of extra code each time I want to make a triangle. When this compiles, it creates a rule that applies to all of the extending classes (CSS syntax using a comma delimited list of class names).

%triangle-base {
    display: inline-block;
    height:  0;
    width:   0;
    padding: 0;

    overflow: hidden;
    text-indent: 100%;

    border-style: solid;
    border-color: transparent;
}
Output example:
.triangle-n, .triangle-e, .triangle-s, .triangle-w {
    display: inline-block;
    height:  0;
    width:   0;
    padding: 0;

    overflow: hidden;
    text-indent: 100%;

    border-style: solid;
    border-color: transparent;
}

Then I use a mixin for the specific parts, mainly the border-widths and colors. My mixin is preset for 8 different directions, using an abbreviated compass direction. You could change this to suite your style. I am also just using the height/width as the vertical height/width of the bounding box. I plan to, at some point, do the math so that the height/width corresponds to the actual height/width of the triangle.

@mixin triangle( $direction, $color, $width, $height ) {
 @extend %triangle-base;

 @if $direction == 'n' {
  border-width: 0 $width/2 $height;
  border-bottom-color: $color;

 } @else if $direction == 'e' {
  border-width: $width/2 0 $width/2 $height;
  border-left-color: $color;

 } @else if $direction == 's' {
  border-width: $height $width/2 0;
  border-top-color: $color;

 } @else if $direction == 'w' {
  border-width: $width/2 $height $width/2 0;
  border-right-color: $color;

 } @else if $direction == 'ne' {
  border-width: $height 0 0 $width;
  border-top-color: $color;

 } @else if $direction == 'se' {
  border-width: 0 0 $height $width;
  border-bottom-color: $color;

 } @else if $direction == 'sw' {
  border-width: 0 $width $height 0;
  border-bottom-color: $color;

 } @else if $direction == 'nw' {
  border-width: $height $width 0 0;
  border-top-color: $color;

 }
}

Comments

Popular posts from this blog

Element.focus() in IE9 running Jasmine tests with Karma

I recently udpated our Jasmine unit tests to run in Karma ; expanding our browser coverage, adding code coverage reports , and using fixtures for testing DOM manipulation . One of my tests kept failing in IE9, but only when I ran from the console. If I attempted to debug in the browser, everything passed. It turns out that IE9 (at least) needed a few ms to catch it's breath before correctly focusing on the starting element. To do this, I just added a 100ms delay before each test ran (Using Jasmine 2.3). beforeEach(function(done){ loadFixtures('myfixture.html'); // Setting focus in IE requires a delay to work correctly! setTimeout(function(){ done(); }, 100); });

CSS line-height Units Explained

In Chris Coyier's recent article, " Fun with line-height! ", he mentions that we often use unitless values for line-height so that it's proportional to the font size. This is only part of the story, and I was reminded of a Stack Overflow question that got me investigating more about how line-height worked with regards to the various CSS units. If you're declaring the line-height on each element, you won't notice any difference. But if you're not crazy and using the first C of CSS (that's 'Cascading', by the way), then the inherited line-height might not work the way you expect. Disclaimer: This is my understanding after doing some research and testing. I may not be completely correct. TL;DR When using a relative unit (em, %), the line-height is calculated based on the font size of the element where the line-height is defined. This line-height is then inherited, unchanged, by each of its descendants. So we end up with a line...

Flags vs Vendor Prefixes for Experimental CSS

Google recently announced that it will be switching Chrome's rendering engine to a fork of Webkit, called “Blink”. If you're interested, you can read their blog post about Blink . One of the changes we will be seeing in Blink, is the use of browser flags in place of vendor prefixes . What this means, is that rather than prefixing experimental CSS with -webkit-, -moz-, -ms-, -o-, -khtml-, etc.; We will be required to enable these attributes using a flag in the browser (like the ones currently at chrome://flags). If you ask me, both ways have their advantages and disadvantages. Though, in the end, I lean towards the flags over the vendor prefixes, and here's why: #1 Code Bloat On average, using CSS with vendor prefixes requires writing it 5 times . Every time you use it . #2 Future Friendly Eventually, prefixed code will be replaced by the unprefixed code. #3 Browser Dev Friendly Browsers tend to continue to support the prefixed code, even if it doesn...