The card footer actions needs to be updated to match the new design document.

Fixing security vulnerability issue (given by Github). https://github.com/hafslundnett/hdd-style/network/dependencies

• Pixel bug when using color highlights (first row top left)
• Make sure that the table padding is always consistent (this should be tested).

• Shadows need to be removed.
• Button states need to be defined (idle, hover, active, disabled)
• Make sure to reduce the amount of available colors to the once defined in the design document.

Something to do with positioning. Font-awesome overriding the posistion attribute. Checked in bug from HAL-Components.

In mdm, the loading spinner don't appear at all

The release-build only handles upload of files to Azure CDN, but it could potentially handle the packaging and release of a new version as well. By doing this as part of the build, we could automate updating package-version and CDN-url based on the release-branch number, reducing the number of manual operations needed to roll out a new version.

When a button is pressed, the active style gets applied to the button. When the mouse button is released however, the button keeps the active styling until the user clicks away. The active style should only be applied to the button while it is being pressed.

Currently are all fontawesome font files located in the 'hdd-theme' (/webfonts/...) project. We should move these webfonts to a public locations in order to use this project in a prod environment.

🐞 Bug Report

Affected element

Radiobutton

Is this a regression?

Not sure, but think it is caused by the content-box -> border-box update

Description

The border that defines a picked radiobutton is different (the border is not fully a circle and weirdly placed in the radiobutton) on different on different zooms and different in the form-fields documentation and the radio-button documentation.

🔬 Minimal Reproduction (code)

🔥 Exception or Error

    Radio buttons
    
        
        
        Picked
    
    
        
        
        Unpicked
    

🌍 Your Environment

Mac, Chrome

HDD Version:
10.0.2

Anything else relevant?
Not specific to browser, but the bug differ from browser to browser

New component grouped button. This should allow to group buttons together to for example create a confirm edit (https://computas.invisionapp.com/share/NFISX8VGZ5Q#/screens/288828943) or to group 2 buttons together (needing input from Victoria)

What do you guys thing do we need a separate component or is the current card component offering enough functionalities? https://github.com/hafslundnett/hdd-style/wiki/Card

• The current tooltips need to be renamed to small-menu.
• Building tooltip as in specs
• The current tooltip by default shows only up when hovering on the object. But should have the plausibilities for mutations like: no-hover, is-active

Padding gets lost, and text goes out of tooltip content body if word is to long.

Style checkboxes and radio buttons according to styleguide

Final check to check for usability, accessibility and the markup. Let's try to make some test pages

• Login
• Dashboard
• User profile with a table
• At minimum do a check with lighthouse or axe-core plugin. Preferably go through a11y checklist: https://a11yproject.com/checklist

• Separate the data colors from the main set of colors. These should not be used outside of data graphs.
• Updating already existing colors
• Discussion about how to reuse colors (mixin, classes functions etc.)

.bg-primary
.color-primary

color: color('primary');
color: data-color('green');

Currently we have for background colors the .background-colors class group maybe we have to rename this.

Use overflow-x: auto; instead of overflow-x: scroll; for .hdd-card_scroll-wrapper to only show scrollbar if content is overflowing. I'm guessing this is a good default behaviour, since it's not often you want to show the grey disabled horizontal scrollbars?

There were a lot of variable/main imports in various components. variable/main imports typography, which imports FA. Sass isn't clever about imports so this makes duplicate references to stuff. I think we rather have to be mindful about the order we include stuff from the main files. Imports arent needed for components if they have been included prior in a main file (at least for the main bundle),