Input field in alerts

[danielmavila]

My alerts have been rendering with a random fieldset in the html, I am not using type "input" for any of these.

sweetAlert({
    type: 'success'
    title: 'Report Archived'
    text: 'Report has been archived."
})

[TomTasche]

check the element in your browser's developer tools. you probably have a stylesheet saying "input { display: block !important; }" somewhere

[adrianricardo]

I had a similar issue caused by foundation css rules

[masonfox]

I am having this issue as well. It seems to be coming from the Foundation CSS file. I went through commenting things in and out and still couldn't find a solution.

If anyone has a fix, it would be much appreciated.

[TomTasche]

Assign a customClass to the dialog and then insert a css-file with the following rule at the end of your html-body:
.custom-dialog-class input {
display: none;
}

[dlombardi]

so whats the fix here?

[TomTasche]

#351 (comment)

[ElranZiggi]

Throw this css in

.sweet-alert fieldset input {
display: none;
}

[mbarwick83]

The fix should really be in SweetAlert's main CSS, no? .sweet-alert input {display:none!IMPORTANT}

[beastybeast]

Related to #534

[t4t5]

Fixed in 2.0, thanks to the fact that each modal now renders from scratch instead.