Steps to reproduce
- Create an input with a disabled="disabled" attribute.
- Add CSS attribute selector styling (input[disabled]) to see styling triggered by the disabled attribute.
Comments and activity
- Microsoft Edge Team
Changed Assigned To to “James M.”
Changed Steps to Reproduce
Changed Assigned To to “bbrinza”
Changed Status to “Not reproducible”
I am Dev in Microsoft and I work for Azure B2C Team. Didn’t find a way to file the bug internally so choose to followup here.
Our product has encounterred a similar issue on rendering such attribute on the page. As tested, the attribute works just fine, it is just that the attribute does not show on the Edge UI. It shows up in all other major Browsers.
Here is the original stackoverflow filed by our customer and the reply was from me:
For the background info:
Our page is dynamically generated with the help of handlebar.js, handlebar is a dynamic template tool which consumes data in JSON format and generate the html based on that JSON. Once the HTML is generated, we will insert them into the default template in browser.
For further information, please contact me using my alias: xingzho.
I was able to reproduce by first setting a button attribute to disabled in html, disabled="disabled". Then disabling again with jquery .prop() method, $(‘button’).prop('disabled’, true);. This completely removes the disabled attribute, which of course removes any disabled styles that were declared. However, the button property is disabled, it just won’t visually appear that way. In Chrome/Firefox the disabled attribute is still present in html after setting property to disabled in js.
This does not reproduce well in jsfiddle, you have to hover over the button to see the effect. https://jsfiddle.net/j05xm2wf/ Locally using a .html file shows the bug immediately.