Disabled=disabled attribute render bug

Not reproducible Issue #13581348

Details

Author
Robin B.
Created
Sep 5, 2017
Privacy
This issue is public.
Found in
  • Microsoft Edge
Found in build #
15.15063
Reports
Reported by 4 people

Sign in to watch or report this issue.

Steps to reproduce

See 

  1. Create an input with a disabled="disabled" attribute.
  2. Add CSS attribute selector styling (input[disabled]) to see styling triggered by the disabled attribute.
  3. Now set the disabled property to ‘true’ via javascript. The styling is gone.

Attachments

0 attachments

    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 tried to reproduce the issue in https://jsfiddle.net/8onzzdsj/ and https://jsfiddle.net/8onzzdsj/1/ but could not find a repro. Please reopen and add details if you think the issue is still valid.

    • 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:
      https://stackoverflow.microsoft.com/questions/104829/b2c-custom-ui-disable-attribute-on-edge-browser

      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.

      Thanks.

    You need to sign in to your Microsoft account to add a comment.

    Sign in