Edge Bug

%3CLINGO-SUB%20id%3D%22lingo-sub-1477890%22%20slang%3D%22en-US%22%3EEdge%20Bug%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1477890%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20new%20form%20controls%20are%20looking%20great%2C%20the%20only%20bad%20thing%20about%20it%20is%20the%20black%20border%20around%20the%20edges%2C%20now%20in%20Chromium%20this%20can%20be%20fixed%20by%20turning%20it%20off%20in%20the%20flags%20or%20going%20into%20an%20extension%20and%20styling%20it%20away.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERight%20now%20I%20can't%20use%20edge%20with%20these%20disgusting%20black%20borders%20around%20form%20inputs%2C%20is%20there%20a%20way%20of%20turning%20these%20new%20%22Form%20control%22%20absolutely%20puke-inducing%20black%20borders%3F%20It%20has%20ruined%20all%20UX%20designs%20of%20all%20websites%20I've%20been%20to.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1492985%22%20slang%3D%22en-US%22%3ERe%3A%20Edge%20Bug%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1492985%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F705095%22%20target%3D%22_blank%22%3E%40JustKato%3C%2FA%3E%26nbsp%3BThanks%20for%20reaching%20out%2C%20and%20welcome%20to%20our%20Insider%20community.%20That%20black%20border%20is%20actually%20an%20intentional%2C%20and%20important%2C%20feature%20rather%20than%20a%20bug!%20As%20one%20of%20our%20program%20managers%20%3CA%20title%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fdiscussions%2Fsome-bugs-and-suggestions-with-the-latest-versions-canary%2Fm-p%2F1307052%2Fhighlight%2Ftrue%23M28913%22%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fdiscussions%2Fsome-bugs-and-suggestions-with-the-latest-versions-canary%2Fm-p%2F1307052%2Fhighlight%2Ftrue%23M28913%22%20target%3D%22_self%22%3Ewrote%20here%3A%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3E%22With%20regards%20to%20the%20black%20bar%20on%20focusable%20elements%20this%20change%20is%20by%20design%20and%20was%20tested%20with%20end%20users.%20From%20an%20aesthetics%20perspective%20the%20change%20was%20roughly%20a%2050%2F50%20split%20for%2Fagainst%20but%20it%20was%20more%20preferred%20by%20users%20that%20have%20a%20need%20for%20higher%20contrast%20colors.%20Because%20of%20our%20focus%20on%20accessibility%20we%20decided%20that%20it%20broke%20the%20tie.%20We%20go%20over%20this%20change%20in%20our%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fblogs.windows.com%2Fmsedgedev%2F2019%2F10%2F15%2Fform-controls-microsoft-edge-chromium%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Eblog%20post%3C%2FA%3E%26nbsp%3Babout%20the%20updated%20form%20controls.%20This%20change%20has%20landed%20in%20Chromium%20itself%20and%20will%20be%20visible%20in%20Chrome%20started%20in%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fblog.chromium.org%2F2020%2F03%2Fupdates-to-form-controls-and-focus.html%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Eversion%2083%3C%2FA%3E.%20And%20Firefox%20is%20also%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fbugzilla.mozilla.org%2Fshow_bug.cgi%3Fid%3D1626512%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Econsidering%3C%2FA%3E%26nbsp%3Baligning%20with%20our%20adjustment%20too%20due%20to%20the%20accessibility%20benefits.%22%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIt's%20important%20for%20us%20to%20make%20the%20web%20accessible%20for%20everyone.%20Since%20we%20know%20there%20will%20always%20be%20a%20variety%20of%20UI%2FUX%20aesthetic%20preferences%2C%20we%20chose%20to%20align%20with%20a%20Microsoft%20value%20and%20side%20with%20increasing%20accessibility.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EHopefully%20this%20adds%20some%20helpful%20context%20to%20the%20feature%2C%20and%20please%20let%20us%20know%20if%20you%20have%20any%20further%20feedback.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CI%3EFawkes%20(they%2Fthem)%3CBR%20%2F%3E%3CBR%20%2F%3EProject%20%26amp%3B%20Community%20Manager%20-%20Microsoft%20Edge%3CI%3E%3C%2FI%3E%3C%2FI%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1493012%22%20slang%3D%22en-US%22%3ERe%3A%20Edge%20Bug%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1493012%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F484598%22%20target%3D%22_blank%22%3E%40fawkes%3C%2FA%3E%26nbsp%3BActually%2C%20it's%20quite%20easy%20to%20cater%20for%20accessibility%20and%20keep%20usual%20borders%20etc.%20for%20the%20majority%20of%20users.%20Add%20an%20easily%20accessible%20switch%20(button%2C%20symbol%20...)%20that%20switches%20all%20of%20Edge%20in%20and%20out%20of%20an%20accessibility%20mode.%20Et%20voila%2C%20you%20have%20the%20best%20for%20everyone%20as%20he%2Fshe%20chooses.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1493391%22%20slang%3D%22en-US%22%3ERe%3A%20Edge%20Bug%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1493391%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F47674%22%20target%3D%22_blank%22%3E%40Kai%20Sch%C3%A4tzl%3C%2FA%3E%26nbsp%3BThat's%20a%20fair%20point%20as%20well%3B%20we%20often%20opt%20for%20giving%26nbsp%3B%20I%20am%20unsure%20if%20adding%20an%20option%20to%20toggle%20that%20UI%20on%2Foff%20is%20being%20considered%2C%20so%20it%20would%20be%20great%20if%20you%20can%20submit%20feedback%20through%20the%20browser%20(Shift%2BAlt%2BI%2C%20or%20%22%3CEM%3E...%22%20menu%26gt%3B%22Help%20and%20Feedback%22%26gt%3B%22Send%20feedback.%22%3C%2FEM%3E)%20Out%20of%20curiosity%2C%20where%20do%20you%20think%20the%20ideal%20location%20would%20be%20for%20such%20a%20switch%3F%20If%20it%20was%20in%20the%20Settings%20menu%2C%20most%20users%20might%20have%20challenges%20with%20finding%20it.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CI%3EFawkes%20(they%2Fthem)%3CBR%20%2F%3EProgram%20Manager%20%26amp%3B%20Community%20Manager%20-%20Microsoft%20Edge%3CI%3E%3C%2FI%3E%3C%2FI%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1493662%22%20slang%3D%22en-US%22%3ERe%3A%20Edge%20Bug%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1493662%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F484598%22%20target%3D%22_blank%22%3E%40fawkes%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWow%2C%20that%20is%20embarrassing...%20Why%20enable%20accessibility%20options%20by%20default%3F%20This%20completely%20ruins%20any%20UX%20Design%20of%20any%20website%2C%20it%20looks%20truly%20horrible%20and%20disgusting%2C%20even%20made%20me%20switch%20away%20from%20edge%20and%20back%20to%20Firefox.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhy%20not%20make%20it%20an%20option%20in%20the%20settings%3F%20I%20don't%20see%20color%20blind%20accessibility%20options%20enabled%20by%20default%2C%20I%20don't%20see%20default%20font-sizes%20of%201000%25%20for%20accessibility%2C%20why%20THIS%3F%20Why%20not%20one%20of%20the%20other%20100000000%20things%20that%20you%20guys%20could%20have%20changed%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETruly%20disgusting%20and%20embarrassing%20from%20the%20chromium%20project.%20I'll%20just%20recommend%20to%20my%20clients%20to%20switch%20to%20Firefox%20in%20the%20meanwhile%2C%20this%20is%20repulsive.%20I%20am%20getting%20100s%20of%20tickets%20every%20day%20because%20you%20guys%20made%20this%20change%2C%20funny%20part%3F%20Can't%20even%20turn%20it%20off%20in%20the%20new%20edge%2C%20works%20in%20chromium%2C%20but%20people%20actually%20started%20using%20edge%20only%20to%20instantly%20abandon%20it%20because%20of%20this...%20Kind%20of%20ironic.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

The new form controls are looking great, the only bad thing about it is the black border around the edges, now in Chromium this can be fixed by turning it off in the flags or going into an extension and styling it away.

 

Right now I can't use edge with these disgusting black borders around form inputs, is there a way of turning these new "Form control" absolutely puke-inducing black borders? It has ruined all UX designs of all websites I've been to.

4 Replies
Highlighted

@JustKato Thanks for reaching out, and welcome to our Insider community. That black border is actually an intentional, and important, feature rather than a bug! As one of our program managers wrote here:

 

"With regards to the black bar on focusable elements this change is by design and was tested with end users. From an aesthetics perspective the change was roughly a 50/50 split for/against but it was more preferred by users that have a need for higher contrast colors. Because of our focus on accessibility we decided that it broke the tie. We go over this change in our blog post about the updated form controls. This change has landed in Chromium itself and will be visible in Chrome started in version 83. And Firefox is also considering aligning with our adjustment too due to the accessibility benefits."

 

It's important for us to make the web accessible for everyone. Since we know there will always be a variety of UI/UX aesthetic preferences, we chose to align with a Microsoft value and side with increasing accessibility. 

 

Hopefully this adds some helpful context to the feature, and please let us know if you have any further feedback.

 

Fawkes (they/them)
Project & Community Manager - Microsoft Edge

Highlighted

@fawkes Actually, it's quite easy to cater for accessibility and keep usual borders etc. for the majority of users. Add an easily accessible switch (button, symbol ...) that switches all of Edge in and out of an accessibility mode. Et voila, you have the best for everyone as he/she chooses.

Highlighted

@Kai Schätzl That's a fair point as well; we often opt for giving  I am unsure if adding an option to toggle that UI on/off is being considered, so it would be great if you can submit feedback through the browser (Shift+Alt+I, or "..." menu>"Help and Feedback">"Send feedback.") Out of curiosity, where do you think the ideal location would be for such a switch? If it was in the Settings menu, most users might have challenges with finding it.

 

Fawkes (they/them)
Program Manager & Community Manager - Microsoft Edge

Highlighted

@fawkes 

Wow, that is embarrassing... Why enable accessibility options by default? This completely ruins any UX Design of any website, it looks truly horrible and disgusting, even made me switch away from edge and back to Firefox.

 

Why not make it an option in the settings? I don't see color blind accessibility options enabled by default, I don't see default font-sizes of 1000% for accessibility, why THIS? Why not one of the other 100000000 things that you guys could have changed?

 

Truly disgusting and embarrassing from the chromium project. I'll just recommend to my clients to switch to Firefox in the meanwhile, this is repulsive. I am getting 100s of tickets every day because you guys made this change, funny part? Can't even turn it off in the new edge, works in chromium, but people actually started using edge only to instantly abandon it because of this... Kind of ironic.