Steps to reproduce
On July 18th a Microsoft Edge Engineer logged my bug directly into the backend.
There is an issue with style.color effecting comboboxes. Please note how you can’t change the selection within the Edge browser. (The JS fiddle works in all other browsers including IE11)
The initial JS fiddle is:
Was wondering if there is an update on the status of this bug, or when this bug may get fixed. (e.g. what priority level was assigned to the bug).
This October 27th i’ll be presenting at the annual Minnesota GIS conference and talking about geospatial web development; additionally at about this same time we’ll be revealing our new software product. Currently I’ve written some JS to test the browser engine and if it is Edge displaying a warning message encouraging users to use either Chrome, Firefox or IE11. For our design this was the easiest stop-gap measure.
We will begin Beta testing soon, with final product release in the fourth quarter. Any updates on the status of this bug would be greatly appreciated.
The work aground for this bug is to replace the js style.color with a css classes, however in our product the css classes are dynamically built via several AI’s. Making adjustments to our AI’s is possible but it will take upwards of 2 days. (writing js code to test the browser engine and display an alert messagebox took under 30min)
As this is an Edge rendering bug we’ve avoided making updates to the AI’s with the hope the bug would be soon fixed.
Comments and activity
- Microsoft Edge Team
Changed Assigned To to “Ibrahim O.”
Changed Assigned To to “Sermet I.”
Changed Assigned To from “Sermet I.” to “Ted D.”
Changed Status to “Confirmed”
Changed Status from “Confirmed” to “Won’t fix”
Does Microsoft have any insight on why this wont be fixed?
Within the comments of stackoverflow the issue priests in (version 12, version 4 was reported)
Please comment out the alert box and test again within Edge.
To the best of my knowledge no design standards were violated, and this JS Fiddle works in IE 10, IE 11, Firefox & Chrome. Only Edge renders it differently.
Thank you for the report,
We have investigated the issue and while it’s a valid issue this is very uncommon pattern. Given the relative priority and severity of the problem we won’t be able to address this in the near future.
All the best,
The MS Edge Team
@Brad E. , Thank-you for the update. And I completely agree that it is an uncommon design (although efficient), was just very surprised some code failed in Edge whereas it used to work in IE11. Apologizes for the crudely thrown together JSFiddle examples. Thanks again for your response.