search

angular-ui / bootstrap

PLEASE READ THE PROJECT STATUS BELOW. Native AngularJS (Angular) directives for Bootstrap. Smaller footprint (20kB gzipped), no 3rd party JS dependencies (jQuery, bootstrap JS) required. Please read the README.md file before submitting an issue!
http://angular-ui.github.io/bootstrap/
MIT License
14.29k stars 6.73k forks source link

UI Bootstrap Accordion Issue in IE11 only - Input fields that are placed in the Accordian Header are disabled and not accessible #6506

Open shahidmiruk opened 7 years ago

shahidmiruk commented 7 years ago

Bug description:

When disabling the accordion group (uib-accordion-group is-disabled="true") so that the accordion can only be opened by clicking in specific areas (divs/columns), any input field that is placed inside the accordion header is also disabled and not accessible.

In IE10, firefox and chrome, even though the accordion group is disabled, and as a result we can only open the accordion by clicking on specified areas (divs/columns), the input fields themselves are not disabled and one can input values in those fields.

Can someone help fix this for IE11 so that it behaves in the same way as the other browsers i.e. the input fields are enabled and accessible.

Link to minimally-working plunker that reproduces the issue:

https://plnkr.co/edit/gcsC24AbLZjJhVFEXCzN?p=preview

Steps to reproduce the issue:

1- Open the Plunker link provided above. 2- Clicking on the first column will open up the accordion. 3- Clicking on the second column will NOT open the accordion. 4- Click on the 'Edit' link in the second column to display an input field. When viewing the plunker in IE11 this field will be disabled, but in all other browsers and IE10 it is enabled and accessible.

Version of Angular, UIBS, and Bootstrap

Angular: 1.6.1

UIBS: 2.5.0

Bootstrap: 3.3.7

piller187 commented 5 years ago

I'm having the same issue in the same situation. I place a textbox in the accordion header and in IE 11 you can't click in the textbox to give focus. However I found it's not disabled really because I can tab into it as a workaround. Guessing something in the event chain is being stopped before it gets to the input box?