Tag: css

CSS in the Style Tag — Part 6

Hi Everyone! Welcome to the 6th and final post in the HTML series.  If you have just stumbled onto this post, use the links below to catch up on the series.

Intro to HTML 

HTML Tag Attributes

Using CSS in HTML

Containers and Style Attributes

HTML for Lists

 CSS with Style

This post picks up where post 4 left off with CSS.  To review, CSS can be written in 3 ways  4 ways (updated 4/24/2018).

  1. Inside an HTML tag using the style attribute (see post Containers and Style Attributes).
  2. Inside a style tag.
  3. Inside JavaScript in a Text Area.
  4. In a separate CSS file.

Now, if you are new to HTML and CSS, I recommend starting with a style attribute and then moving up to CSS inside a style tag before graduating to JavaScript in external style sheets.  Style tags are easy to edit, copy and paste, and share.  You will also be able to create a reusable CSS template for all DXPs, and formatting will be a thing of the past.  It’s magical!  Furthermore, CSS opens up formatting for pieces of the application that have no GUI.  In other words, the only way to format it is with CSS.

Now, it is bound to happen that as you get better at CSS, you write more of it.  At that point, it might make sense to store the CSS in a separate file and reference the file in the Text Area, but not if you need to edit frequently.  I’ve always just kept my CSS in the DXP.  There is also the option of creating a CSS style sheet with JavaScript.  This is demonstrated in this Data Shop Talk post.  Scroll down to “Insert a Style Sheet”.

This blog post is going to focus on CSS in a style tag.  I will break it down into 4 parts.

  1. Example of CSS in a style tag
  2. Explanation of the basic syntax and rules
  3. Other syntax and rules
  4. Explanation of how to decipher the “Spotfire” elements

CSS Example

Let’s start off with an example so you have a frame of reference.  Download this Ruths.ai template NFL Expectancy Win Calculator.  (Note: The button says subscriber-only, but click it anyway.  It will take you to a different website.  You might have to create an account, but the template is free.).  Go to the Expected Wins Page.  In the Pythagorean Win Expectancy Text Area, right-click and select Edit HTML to see the code… A LOT of code.  Scroll down in the sample template to make sure you know where the end is.  I’ve taken a small screenshot below.  This was all written by Lucas Wood of Ruths.ai.

In this example, the code is controlling the appearance of the entire template.  It can be copied and pasted into other DXPs to achieve the same look and feel.  Next, let’s look at the rules and structure for writing this type of code.

CSS Syntax

I’ve mentioned them before, and I’ll mention them again — W3Schools is a great resource for learning HTML, CSS, and JavaScript.  The image below is from their site that demonstrates the basic syntax.

It’s very simple syntax that consists of a selector and a declaration block.  The declaration block uses property-value pairs where the property and value are separated by a colon and multiple property-value pairs are separated by semi-colons.  The declaration block itself is wrapped in squiggly braces.

Now, selectors are important.  They find HTML elements and format all elements of that type on a page (or in our case, in a Text Area or DXP file).  This is the efficiency I have been talking about.  CSS formats everything with one block of code so you don’t have to format individual elements (like buttons) or add attributes to all HTML tags to format them.

There are many different types of CSS selectors, and you should definitely review them at  W3Schools .  Here is a simple example of an element selector.  The “p” references the <p> tag, and the selector is selecting all of the <p> tagged content and formatting it.


Here is an example of a class selector from the Ruths.ai template.  The selector is looking for the .sf-element-page-tab class.  It will select all page tabs and change the border and padding accordingly.


Now that you know the basic syntax, let’s look at some specific code in the template that might not yet make sense.  For example, you may be wondering what @import and !important are doing.

Other Rules & Syntax


CSS also utilizes “at-rules”.  The “@import” is an example of an “at-rule”.  At-rules are special instructions that control how styles are applied.  In the case of this example, @import is pulling in a Google font.  Other examples include @media, @font-face.


Each line of CSS in the template has “!important” at the end of it.  “!important” establishes priority.  It is telling SPotfire this code takes precedence over any other formatting that might be in the template, such as formatting in HTML tags or formatting from the set theme.  The exclamation mark is called a delimiter token, and “important” is a keyword.


You may also have noticed that a line can be commented out with a forward slash and an asterisk.

Okay, that was a lot of talk about syntax.  However, there is still more to learn.  Next, we are going to talk about how to decipher the classes used by Spotfire. For example, if we want to change the active page tab color, how do we know to write “.sf-element-page-tab.sfpc-active”?

CSS for Spotfire

To figure this out, you can use the Developer Tools native to the application.  Developer Tools are NOT turned on by default, so to even see the menu, go to Tools > Options > Application > Scroll to the bottom and check the box for Show Development menu.  Now, you will see this menu in Tools.

Select Developer Tools, and a popup window appears. Click on the button that looks like this  to inspect page elements.  Now, move the mouse around the DXP and hover over elements to get the element names. I’ve taken some screenshots below for example.  I realize these screenshots aren’t the best.  I actually tried to make a video, but when you move and hover, stuff is constantly flashing on the screen.  It was painful to watch.





Now, take note that an element can have multiple classes.  Each class is denoted by a period, such as “.sf-element” and “.sf-element-visual-title”.  The element “.sf-element” is a referring to something less specific than “.sf-element.sf-element-visual-title”, and “sf.element.sf-element-visual-title.sfpc-top” is even more specific.

For example, for the element shown below, to format the text box, use “sf-element-text-area”.  You don’t need to dig all the way into “sfpc-first.row”.


You’ll get better identifying the right element and class with practice and trial and error.

Final Notes

I know this is turning out to be quite a long post, but just hold on.  I’m about to wrap it up.  There are just a few more things to note.  First, in order to have CSS apply to an entire DXP, you need to have the <style> tag and accompanying CSS in at least one Text Area on each page. With that said, be careful when you edit.  You might drive yourself crazy trying to figure out why the CSS isn’t doing what you want when there are conflicting pieces of code on different pages.

Well, that wraps it up.  Thanks for sticking with me to the end.  Clearly, there is much more to learn about CSS than one blog post can handle, but this will get you started.





Guest Spotfire blogger residing in Whitefish, MT.  Working for SM Energy’s Advanced Analytics and Emerging Technology team!

Using CSS in Spotfire HTML — Part 3

This is part 3 of my HTML series.  The first week, I explained the basics of HTML tags in this post.  Post number two discussed tag attributes.  This week, we are going to cover formatting with CSS.

To set the stage for this post, here is a simple example clearly demonstrating where we are going.  In the Text Area below,  2 lines are duplicated.  As you can see, the lines look the same, but the code is different.  One is using CSS, and one is not.  That’s what this post is all about.

Now, let’s talk about what CSS is and why it’s important.

What is CSS?

CSS stands for Cascading Style Sheets, and it is used to specify the format or style of content provided by the HTML.  This might be confusing because it is possible to specify formatting with HTML tags.  After all, some of the tags I pointed out in the Intro were tags for formatting, like <b>, <i>, <em>, <strong>, and <font>.  That’s what italics and bold are — Formatting!

Really, this was all just one giant mistake in coding history.   HTML was not intended to be used for formatting.  As W3School notes:

“HTML was created to describe the content of a web page, like:

<h1>This is a heading</h1>

<p>This is a paragraph.</p>

When tags like <font>, and color attributes were added to the HTML 3.2 specification, it started a nightmare for web developers. Development of large websites, where fonts and color information were added to every single page, became a long and expensive process. To solve this problem, the World Wide Web Consortium (W3C) created CSS.”

Why use CSS?

The answer to that question is simple — EFFICIENCY.  CSS is how Ruths.ai and Big Mountain Analytics are able to quickly produce beautiful templates.  We definitely aren’t formatting each and every button or Text Area.  That takes too long.

To demonstrate, download this free template from the Ruths.ai Exchange.  In the DXP, right-click on the Text Area in the Terms page, select Edit HTML, and look at the code. It’s using the <style> tag, and CSS attributes control the appearance of the entire DXP.

Now, when building web pages, CSS can control the layout of multiple web pages all at once.  When building DXP files, CSS can control the appearance of multiple text areas and other Spotfire elements (like the legend and your buttons) without having to format each and every one of them individually.  It also opens up the ability to control formatting where there is no GUI, such as with the legend.  Formatting the legend requires HTML/CSS.

How to Use CSS in Spotfire

The DXP example you downloaded uses  CSS with the <style> tag, and that’s perfectly valid.  For a complete understanding, know that there are three ways or places to write CSS.

  1. In a separate CSS file (.css extension) — This is only really applicable to building web pages, so don’t even worry about this.
  2. Inside a style tag — This is what you saw in the DXP download.  This is referred to as “inline style” (knowing the right terms to Google is half the battle).  In web design, this is not considered a best practice, but we aren’t building web pages.
  3. Inside an HTML tag using the style attribute.

Which Method to Use

As a Spotfire users,  you should familiarize yourself with methods 2 and 3.  The next logical question to ask would be — when do I use which method?  Here is a quick summary of the pros and cons of each.

Style Tag


  • Most efficient
  • Reusable across DXP files
  • Write a little or write a lot
  • Able to access what the GUI cannot


  • Need to know how to reference Spotfire elements
  • May take longer to build

Style Attributes


  • Quick and easy to write
  • Can be reused


  • Must be written for individual tags
  • Not as efficient


CSS Syntax

Style Attribute Syntax

The general rules for style attribute syntax are…

  • The style attribute will use property/value pairs.
  • The pair must be in quotes
  • Separate Multiple pairs with a semicolon.
  • Enclose the pair in double quotes.

Style Tag Syntax

Using the style tag, the syntax looks a little bit different.  Note the use of brackets and the reference to specific pieces of Spotfire.  This is where the waters start to get deep again, so I am going to wrap this post up with the example shown below.  A future post will talk about this syntax in more detail.


In conclusion, if you new to HTML and CSS, consider these two suggestions.

  1. Start using the style attribute immediately in your own work.  It’s super easy.
  2. Review the CSS in the template download.  Alter and play with it to develop an understanding of what each element of the code controls in Spotfire.

These two suggestions will go a long way in terms of developing your skills and improving the appearance of your Spotfire projects.  Now, this post is getting a bit long, but I wouldn’t be doing a good job if I didn’t talk about syntax.

As always, thanks for reading and feel free to leave comments!  Lastly, since I haven’t said it since the intro, don’t forget that once you start editing HMTL, you shouldn’t use the Edit Text Area option.  It will wipe out your code.



Guest Spotfire blogger residing in Whitefish, MT.  Working for SM Energy’s Advanced Analytics and Emerging Technology team!

Unscrambling the Spotfire Text Area

  • Are you frustrated with the Spotfire Text Area?
  • Are you just getting started with HTML, CSS, JavaScript, or jQuery?
  • Do you find all the different languages that can be implemented in Text Areas confusing?

Read More

Guest Spotfire blogger residing in Whitefish, MT.  Working for SM Energy’s Advanced Analytics and Emerging Technology team!

Hide elements inside a SpotfireControl

Let’s say you want to remove an item from the dropdown of a SpotfireControl.

You can look inside of a Spotfire Control with the following JavaScript:


<p id="turkey"><SpotfireControl id="b6d7d7d9761649bd9f87f096def91dfb" ></p>

<p id="bacon"></p>


$( document ).ready(function() {

This lets you see the inside of the SpotfireControl. We see that the ‘Variable’ selection is the one that we want to hide. Simply grab the object using the title attribute.


$( document ).ready(function() {


Technical Director at Ruths.ai