bullhorn / novo-elements Goto Github PK

Create a demo for a custom component passed as the results for Chips/Picker.

Caret is off

The chips should clear the value after selecting an option from the dropdown. Also, the dropdown position is off (should be below the input).

Update all the things.

In Firefox, you can type letters and chars into the number only fields. Even though they are type="number" it is not respected. We should use a filter or something to ensure they function the same.

Note: for support questions, please use one of these channels: Chat: BullhornOSS Gitter

I'm submitting a ...

• bug report
• feature request
• question about the decisions made in the repository

What is the current behavior?

Using [disabled]="x" removes the disabled attribute from the host button tag

What is the expected behavior?

Need to add "disabled" host attribute

Note: for support questions, please use one of these channels: Chat: BullhornOSS Gitter

I'm submitting a ...

• bug report
• feature request
• question about the decisions made in the repository

What is the current behavior?

Inline novo-toast elements are tied to *ngIf to show or hide. Time properties on inline novo-toast elements are set to null.

What is the expected behavior?

Use a timer attribute on inline novo-toast elements to control show or hide. timer attribute should allow for a time in ms or for indefinite.

What is the motivation / use case for changing the behavior?

• Added/improved functionality

Note: for support questions, please use one of these channels: Chat: BullhornOSS Gitter

I'm submitting a ...

• bug report
• feature request
• question about the decisions made in the repository

What is the current behavior?

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via

https://plnkr.co or similar. (TODO - make a starter plnkr)

What is the expected behavior?

What is the motivation / use case for changing the behavior?

Please tell us about your environment:

• Angular version: 2.0.0-beta.X
• Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]

Other information

(e.g. detailed explanation, screenshots, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)

Right now these auto close, should be an input if you want auto close or not, defaulting to false. autoclose="true" / autoclose="false"

When using the Picker, the searchTerm is not bound back to the novo-picker element at all.

Note: for support questions, please use one of these channels: Chat: BullhornOSS Gitter

I'm submitting a ...

• bug report
• feature request
• question about the decisions made in the repository

What is the current behavior?

section.primary is transparent

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via

https://plnkr.co or similar. (TODO - make a starter plnkr)

What is the expected behavior?

The top bar should not be transparent when position:fixed

What is the motivation / use case for changing the behavior?

I would like to make a sticky header in mobile which is made up of 3 sections

[BTN] [HEADER] [BTN] <- should be sticky to top (position:fixed)
[SECTION] <- should slide under header when user scrolls
[TAB SECTION] <- should become sticky under HEADER (becomes fixed at certain point)

The top bar uses the section.primary class and currently has no background color so it is transparent when the section content slides under it.

What I would like is the background color to also be applied to section.primary to allow me to have this functionality.

Please tell us about your environment:

• Angular version: 2.0.0-beta.X
• Ionic 2
• Browser: all

Other information

I'm submitting a FEATURE REQUEST

What is the current behavior?

Forms do not have a disabled state.

What is the expected behavior?

Implement disabled state to look like

Make code coverage go off of source code rather then the transpiled code.

See: https://github.com/douglasduteil/isparta or something similiar

When filtering on the Table and hitting "Clear" it should close the filter box.

The inline toast (when using as component and not via service) still has the z-index of 9999, making it appear over the modals (z1000). If it is used inline, the zindex should not be 9999.

I'm submitting a BUG REPORT

What is the current behavior?

An optional parameter to make row selection done via a checkbox in an Actions columns.

Use the new router

There is weird extra padding/margin on the picker/chips dropdown.

Searching does not work in Firefox, the autocompletes do not show up.

Make sure every folder has appropriate spec/README files and are filled out correctly before 1.0 release.

Currently, the toast will animate down and if the toast is of the same type it will animate down correctly. However, if you have toasts that are different they still animate down. Video url below:

http://recordit.co/0zU49Usdmu

Footer should just be another

• put all toast/tooltips back in (ColorDemo, etc..)
• remove dummy text

Update to use the new forms. This will take a bit of refactoring of our Form component.

For i18n and localization support, all strings within the elements need a configuration so that they can be overwritten. This might include support for number formats and dates as well (we are using moment, so we make sure we aren't manipulating things after converting from moment).