FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

feat(button): add input modifier by christiemolloy · Pull Request #2005 · patternfly/patternfly · GitHub

feat(button): add input modifier - #2005

Merged
mcoker merged 15 commits into
patternfly:masterfrom
christiemolloy:iss1926
Sep 19, 2019
Merged

feat(button): add input modifier#2005
mcoker merged 15 commits into
patternfly:masterfrom
christiemolloy:iss1926

Conversation

Copy link
Copy Markdown
Member

closes #1926

As per @mcoker suggestion, added a new modifier to the button component that styles it for use in with an input.

Also updated the clipboard copy component, context selector component and input component to now use this button.

patternfly-build commented Jul 1, 2019
edited
Loading

Copy link
Copy Markdown
Collaborator

Deploy preview for pf-next ready!

Built with commit ad6c56c

https://deploy-preview-2005--pf-next.netlify.com

@@ -1,4 +1,4 @@
<button class="pf-c-clipboard-copy__group-toggle{{#if clipboard-copy-group-toggle--modifier}} {{clipboard-copy-group-toggle--modifier}}{{/if}}"
<div class="pf-c-clipboard-copy__group-toggle{{#if clipboard-copy-group-toggle--modifier}} {{clipboard-copy-group-toggle--modifier}}{{/if}}"

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

@mcoker @mattnolting I removed the hbs file for pf-c-clipboard-copy__group-copy because it was only just a wrapper. I didn't remove the hbs for pf-c-clipboard-copy__group-toggle because its used to determine whether its expanded or not, what do you both think about that?

mcoker commented Jul 1, 2019

Copy link
Copy Markdown
Contributor

Would we also want to use this variation of the button as the dropdown (and components like it) toggle with left/right padding changes?

// --pf-c-clipboard-copy__group-toggle--active--BorderBottomColor: var(--pf-global--active-color--100);
// --pf-c-clipboard-copy__group-toggle--focus--BorderBottomWidth: var(--pf-global--BorderWidth--md);
// --pf-c-clipboard-copy__group-toggle--focus--BorderBottomColor: var(--pf-global--active-color--100);
--pf-c-clipboard-copy__group-toggle--c-button--m-expanded--BorderBottomWidth: var(--pf-global--BorderWidth--md);

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

I wonder if we should add a modifier to the button for this, like pf-m-expanded/selected/active or something like that, since I imagine we will want to apply these styles in other contexts, too?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

My take was that the button should just hold the generic hover, active and focus styles, and then components that use the button can add their own modifiers since they're specific to that component, and we can't forsee all of the modifier names. But what is your main reasoning for adding these modifiers to the button I'm open to adding them.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

The name is the tricky part, but it's a common form control display for active/focus - the thicker, blue bottom border. We would also use it for expanded as the dropdown toggle, too, if we use it there.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

So are you suggesting adding pf-m-expanded to the button since we know we're going to be using that in the clipboard copy at least.

  --pf-c-button--m-input--m-expanded--BorderBottomWidth: var(--pf-global--BorderWidth--md);
  --pf-c-button--m-input--m-expanded--BorderBottomColor: var(--pf-global--active-color--100);

pf-m-selected/active: not sure about these classes because I think the active/focus styles cover these, or am I missing something?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

Yep, that's it. We can always not since it's only used here for now, and add it later if we end up using it elsewhere (like the dropdown or other components). It just looks like a state this type of button would need.

Also what's the reasoning behind pf-m-input as the modifier name? Is it because the intended use is always going to be "for use in with an input." (as in connected to an input?) I wonder if that's going to end up being limiting.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

Added the expanded modifier to the button.. @mceledonia do you have any ideas for a name for this button?

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

@christiemolloy Is this for the overall modifier to change styling to input group? If so, maybe something like input-group-button or something specific like that. Maybe something that rolls off the tongue a bit better :)

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

Its for these buttons, thanks for the suggestion!

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

@mceledonia on second thought, if we use this button in the individual dropdown/select etc. then i dont know if input-group-button would be correct, since it wouldn't be part of an input. Maybe a name that refers to the style more so the usage?

mattnolting left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

As a side note here, I think changing to 2px/blue on hover looks better than the current black to blue change, which isn't very noticeable. Then in the case of the dropdown arrow, leaving the 2px blue style active. If we made this change it would apply to all buttons/inputs/dropdowns that use this style, something to consider.

Should the :hover weight be 2px ^^?

@@ -3,11 +3,15 @@ Editable
{{#> clipboard-copy clipboard-copy--id="3"}}
{{#> clipboard-copy-group}}
{{#> clipboard-copy-group-toggle clipboard-copy-group-toggle--attribute=(concat 'id="toggle-' clipboard-copy--id '" aria-labelledby="toggle-' clipboard-copy--id ' text-input-' clipboard-copy--id '" aria-controls="content-' clipboard-copy--id '"')}}

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

Is there a reason we don't just add the group-toggle class and all of the attributes to the button, like we did with the group-copy button?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

I added a comment here about it: #2005 (comment)
but i think its possible to give it a try

christiemolloy commented Jul 2, 2019
edited
Loading

Copy link
Copy Markdown
Member Author

As a side note here, I think changing to 2px/blue on hover looks better than the current black to blue change, which isn't very noticeable. Then in the case of the dropdown arrow, leaving the 2px blue style active. If we made this change it would apply to all buttons/inputs/dropdowns that use this style, something to consider.

Should the :hover weight be 2px ^^?

@mattnolting yep I added a variable for the hover weight: --pf-c-button--m-input--hover--BorderBottomWidth can you see it

christiemolloy commented Jul 2, 2019
edited
Loading

Copy link
Copy Markdown
Member Author

Would we also want to use this variation of the button as the dropdown (and components like it) toggle with left/right padding changes?

@mceledonia do you have an opinion here?
@mcoker I don't see why we couldn't, but it would likely be a breaking change and take a lot of consideration it might get tricky, because when we do it for dropdown, should we also do it for select? and then some selects are built with a div.

Copy link
Copy Markdown

@christiemolloy Yeah we would want this styling for all interactive elements in an input group, so both buttons and dropdowns!

mcoker commented Jul 10, 2019

Copy link
Copy Markdown
Contributor

Yeah we would want this styling for all interactive elements in an input group

@mceledonia what about for use outside of an input group, could this variation of the button be used as the toggle for standalone dropdown, select, options menu, etc components? The style is

@matthewcarleton has also mentioned there is interest from products in a primary button style toggle for dropdown toggles, too. If we support that, I think it makes sense that the toggle for those components is a variation of our button, whether it's the style we're adding in this PR, the primary button, etc.

Copy link
Copy Markdown
Contributor

just to add to what @mcoker is saying, this issue is tracking what's been seen as a useful addition on the product side. #1872

Copy link
Copy Markdown
Member Author

@mcoker @mattnolting should I make this not a breaking change by putting back in the code for copy to clipboard etc. or do you want to leave this until the breaking change period?

Copy link
Copy Markdown
Member

@christiemolloy I don't see the problem with calling this 'input'. An input group is always used to supply an input, right? That may be from a text field as in the search or a select list.

Regarding the disabled question, keep in mind that if this will be disabled then the entire input group will show disabled, i.e. it does not make any sense to allow the user to type into the search field and then have the action/input disabled. Don't know if this changes any thinking on this, but wanted to make sure that we are thinking of the entire input group as one thing.

Copy link
Copy Markdown
Member Author

@mcarrano I'm not sure if we could say that pf-m-input would hold when its used in a dropdown component?

Copy link
Copy Markdown
Collaborator

@christiemolloy I don't see the problem with calling this 'input'. An input group is always used to supply an input, right? That may be from a text field as in the search or a select list.

@mcarrano Also can be used with textareas, html selects, dropdown, custom select, other things down the road. That's why we thought pf-m-control worked, because it implies that it controls something, but not necessarily always an input :)

Copy link
Copy Markdown
Member

@christiemolloy @mattnolting I must be missing a use case here. In what circumstances would this be used as part of a dropdown, a text area, or another control? I though this was specific to an input group of things built from an input group like a Touchspin.

Copy link
Copy Markdown
Member Author

Sorry about not communicating fully. The potential plan down the road would be to replace the button in the dropdown, select, context selector etc components with this button, as they all share exactly the same styles. This will allow us to reuse a lot of code and make it easier to update all components that use this button @mcarrano

Copy link
Copy Markdown
Member

@christiemolloy Thanks for the clarification. I understand better now. I'd say go with pf-m-control unless someone has a better idea.

}

&.pf-m-control {
position: relative;

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

this comes with .pf-c-button


&.pf-m-control {
position: relative;
border: none;

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

same ^

position: relative;
border: none;

&::before {

mcoker Sep 17, 2019
edited
Loading

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

any reason you're using ::before instead of ::after? Seems like you would get most of the definitions for free, then you can just redefine --pf-c-button--BorderWidth and handle the border-color somehow. Either the way you have it where you define a new border-color property for the control modifier, or you could separate the default border: var(--pf-c-button--BorderWidth) solid var(--pf-c-button--BorderColor); into border: var(--pf-c-button--BorderWidth) solid; and border-color: var(--pf-c-button--BorderColor);, then define:

--pf-c-button--m-control--before--BorderColor: var(--pf-c-button--m-control--before--BorderTopColor) var(--pf-c-button--m-control--before--BorderRightColor) var(--pf-c-button--m-control--before--BorderBottomColor) var(--pf-c-button--m-control--before--BorderLeftColor);

then redefine --pf-c-button--BorderColor: var(--pf-c-button--m-control--before--BorderColor); in &.pf-m-control {}

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

Ah the reason I used before instead of after was because I based it off the clipboard-copy-group-copy, but after definitely makes sense in this case. Updated.

background-color: var(--pf-c-button--m-control--disabled--BackgroundColor);

&::before {
--pf-c-button--m-control--before--BorderBottomColor: var(--pf-c-button--m-control--before--BorderTopColor);

mcoker Sep 17, 2019
edited
Loading

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

This works for me, though we could also be safe and create --pf-c-button--m-control--disabled--before--BorderBottomColor, which allows flexbility for this to be its own var if we want to change it in the future without a breaking change. Or if you go with the approach above and create --pf-c-button--m-control--before--BorderColor, then you could create --pf-c-button--m-control--disabled--before--BorderColor and just redefine --pf-c-button--m-control--before--BorderColor: var(--pf-c-button--m-control--disabled--before--BorderColor) here and you wouldn't have to write out the pseudo class selector.

| `.pf-m-plain` | `.pf-c-button` | Modifies for icon styles. This button has no background or border, uses a standard text color, and is used for `.pf-m-plain` icon buttons such as close, expand, kebab, etc. |
| `.pf-m-inline` | `.pf-c-button.pf-m-link` | Modifies for inline styles. This button is presented similar to a normal link, has no padding, and is displayed inline with other inline content. |
| `.pf-m-block` | `.pf-c-button` | Creates a block level button. |
| `.pf-m-control` | `.pf-c-button` | Modifies for control styles. **Note: ** This modifier should only be used when using buttons in the Input or ClipboardCopy components. |

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality
Suggested change
| `.pf-m-control` | `.pf-c-button` | Modifies for control styles. **Note: ** This modifier should only be used when using buttons in the Input or ClipboardCopy components. |
| `.pf-m-control` | `.pf-c-button` | Modifies for control styles. **Note:** This modifier should only be used when using buttons in the Input Group or Clipboard Copy components. |

| `.pf-m-inline` | `.pf-c-button.pf-m-link` | Modifies for inline styles. This button is presented similar to a normal link, has no padding, and is displayed inline with other inline content. |
| `.pf-m-block` | `.pf-c-button` | Creates a block level button. |
| `.pf-m-control` | `.pf-c-button` | Modifies for control styles. **Note: ** This modifier should only be used when using buttons in the Input or ClipboardCopy components. |
| `.pf-m-expanded` | `.pf-c-button.pf-m-input` | Modifies an input button to be expanded. |

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

Maybe instead of "to be expanded" change to "for the expanded state" or something. Currently it reads like the button is expandable, instead of representing the expanded state of something else.

{{/button}}
<br><br>
{{#> button button--modifier="pf-m-control"}}
Control button

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

Do you think this variations and "link" and "inline link" above need the word "button" in the examples?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

No I think its redundant, updated all the examples to remove button

{{#> form-control controlType="input" input="true" form-control--attribute=(concat 'type="search"' 'placeholder="Search"' 'id="textInput1"' 'name="textInput1"' 'aria-labelledby="' context-selector--id '-search-button"')}}
{{/form-control}}
{{#> button button--modifier="pf-m-tertiary" button--attribute=(concat 'id="' context-selector--id '-search-button"' 'aria-label="Search menu items"')}}
{{#> button button--modifier="pf-m-input" button--attribute=(concat 'id="' context-selector--id '-search-button"' 'aria-label="Search menu items"')}}

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

the context selector and input group examples should use pf-m-control instead of pf-m-input

mcoker left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

Looks great! Left some feedback, let me know if you have any questions.

--pf-c-button--BorderWidth: var(--pf-c-button--m-control--after--BorderWidth);
--pf-c-button--BorderColor: var(--pf-c-button--m-control--after--BorderTopColor) var(--pf-c-button--m-control--after--BorderRightColor) var(--pf-c-button--m-control--after--BorderBottomColor) var(--pf-c-button--m-control--after--BorderLeftColor);

border-radius: unset;

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

Any reason we wouldn't just use 0 here? We use unset very sparingly, and in this context, while it will still evaluate to initial (which is 0 for this property) we could just set that directly since we don't want it to have a border-radius.

{{#> button button--modifier="pf-m-control"}}
Control
{{/button}}
{{#> button button--modifier="pf-m-control" button--attribute='aria-label="copy input"'}}

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality
Suggested change
{{#> button button--modifier="pf-m-control" button--attribute='aria-label="copy input"'}}
{{#> button button--modifier="pf-m-control" button--attribute='aria-label="Copy input"'}}

@@ -96,7 +96,7 @@
{{#> input-group}}
{{#> form-control controlType="input" input="true" form-control--attribute='type="text" id="textInput10" name="textInput10" aria-label="input example with popover"'}}

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

super nit - would you mind sentence casing these aria-label values?

Suggested change
{{#> form-control controlType="input" input="true" form-control--attribute='type="text" id="textInput10" name="textInput10" aria-label="input example with popover"'}}
{{#> form-control controlType="input" input="true" form-control--attribute='type="text" id="textInput10" name="textInput10" aria-label="Input example with popover"'}}

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

Updated the file, most of the aria-labels weren't capitalized

mcoker left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

CSS looks great! Left a couple of small comments. Can you also modify the input group so that it doesn't apply the border-radius to .pf-m-control buttons?

mcoker left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

Nice job @christiemolloy!!

mcoker commented Sep 18, 2019

Copy link
Copy Markdown
Contributor

@christiemolloy @mcarrano is the goal to not support the previous ways of attaching buttons to the input group component where we square the borders except for the left side of the first button and right side of the last one? Or are we going to continue to allow that indefinitely?

If we aren't going to allow it, we should create a follow up issue to remove the CSS that does that in a breaking change release.

mcoker merged commit 1d93536 into patternfly:master Sep 19, 2019

Copy link
Copy Markdown
Contributor

🎉 This PR is included in version 2.32.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

maryshak1996 mentioned this pull request Sep 19, 2019
rachael-phillips added a commit that referenced this pull request Sep 27, 2019
# 2019.08 release notes (2019-10-01)
Packages released:
- @patternfly/patternfly@2.x

## Components
- **Charts:** 
  - Adjust padding for pie and donut charts ([#2247](#2247))
  - Set mix-blend-mode for better color contrast ([#2239](#2239))
  - Update area chart opacity ([#2233](#2233))
- **Copy to clipboard:** Wrapped code in pre which allows the code to preserve line-breaks and spaces and also applies styling such as the monospace font. ([#2260](#2260))
- **Data list:** Make data list borders consistent with table ([#2289](#2289))
- **Data toolbar:** 
  - Updated clear button mods ([#2248](#2248))
  - Added in examples for expandable ([#2273](#2273))
- **Flex layout:** Wrapped flex items, update css ([#2214](#2214))
- **Wizard:**
  - Re-enabled wizard modal demos ([#2259](#2259))
  - Updated in page wizard demos to use dark sidebar/nav ([#2296](#2296))
- **Navigation:** Added styling updates to dark nav ([#2283](#2283))
- **Page:** Added ability to keep sidebar collapsed between sizes ([#2264](#2264))
- **Pagination:** Added compact variation ([#2275](#2275))
- **Radio:** Updated the radio component example to single components ([#2231](#2231))
- **Table:**
  - Fixed a11y issues in org documentation/html/table ([#2282](#2282))
  - Added empty and loading state table demos ([#2254](#2254))
- **Tooltip:** Added text align left modifier ([#2284](#2284))
- **Select:**
  - Added typeahead form wrapper, udpated css ([#2255](#2255))
  - Add top expanded example ([#2026](#2026))
- **Chip group:** Add overflow to group ([#2278](#2278))
- **Button:** Add control modifier ([#2005](#2005))

## Other
- **Shield:** Added missing components, missing var to brand docs js ([#2263](#2263))
redallen pushed a commit that referenced this pull request Oct 1, 2019
* Create 2019.08 release notes (2019-10-01)

Adding new release notes

* Update 2019.08 release notes (2019-10-01)

# 2019.08 release notes (2019-10-01)
Packages released:
- @patternfly/patternfly@2.x

## Components
- **Charts:** 
  - Adjust padding for pie and donut charts ([#2247](#2247))
  - Set mix-blend-mode for better color contrast ([#2239](#2239))
  - Update area chart opacity ([#2233](#2233))
- **Copy to clipboard:** Wrapped code in pre which allows the code to preserve line-breaks and spaces and also applies styling such as the monospace font. ([#2260](#2260))
- **Data list:** Make data list borders consistent with table ([#2289](#2289))
- **Data toolbar:** 
  - Updated clear button mods ([#2248](#2248))
  - Added in examples for expandable ([#2273](#2273))
- **Flex layout:** Wrapped flex items, update css ([#2214](#2214))
- **Wizard:**
  - Re-enabled wizard modal demos ([#2259](#2259))
  - Updated in page wizard demos to use dark sidebar/nav ([#2296](#2296))
- **Navigation:** Added styling updates to dark nav ([#2283](#2283))
- **Page:** Added ability to keep sidebar collapsed between sizes ([#2264](#2264))
- **Pagination:** Added compact variation ([#2275](#2275))
- **Radio:** Updated the radio component example to single components ([#2231](#2231))
- **Table:**
  - Fixed a11y issues in org documentation/html/table ([#2282](#2282))
  - Added empty and loading state table demos ([#2254](#2254))
- **Tooltip:** Added text align left modifier ([#2284](#2284))
- **Select:**
  - Added typeahead form wrapper, udpated css ([#2255](#2255))
  - Add top expanded example ([#2026](#2026))
- **Chip group:** Add overflow to group ([#2278](#2278))
- **Button:** Add control modifier ([#2005](#2005))

## Other
- **Shield:** Added missing components, missing var to brand docs js ([#2263](#2263))

* Rename 2019.08 release notes (2019-10-01) to 2019.08 release notes (2019-10-01).MD

Added .md file name

* Update 2019.08 release notes (2019-10-01).MD

Co-Authored-By: Michael Coker <35148959+mcoker@users.noreply.github.com>

* alphabetize components
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants


Back | FazBrowse Home | New Git URL