SOLVED

Renamed classes in components/blacklist - Upstream Chromium

%3CLINGO-SUB%20id%3D%22lingo-sub-1903609%22%20slang%3D%22en-US%22%3ERenamed%20classes%20in%20components%2Fblacklist%20-%20Upstream%20Chromium%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1903609%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20there%20-%20I%20noticed%20that%20as%20of%20version%2087%20in%20Chrome%2C%20the%20following%20upstream%20changes%20have%20been%20made%20in%20Chromium%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fchromium-review.googlesource.com%2Fc%2Fchromium%2Fsrc%2F%2B%2F2234793%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3ERename%20classes%20in%20components%2Fblacklist%20to%20use%20more%20inclusive%20names.%20(I8a1a7d7b)%20%C2%B7%20Gerrit%20Code%20Review%20(googlesource.com)%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20wondering%20if%20these%20will%20make%20their%20way%20into%20Edge%20so%20we%20can%20plan%20importing%20new%20ADMX%20files%20accordingly.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1903918%22%20slang%3D%22en-US%22%3ERe%3A%20Renamed%20classes%20in%20components%2Fblacklist%20-%20Upstream%20Chromium%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1903918%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F343894%22%20target%3D%22_blank%22%3E%40lexcyn%3C%2FA%3E%26nbsp%3BHello!%26nbsp%3B%20Thanks%20for%20reaching%20out!%26nbsp%3B%20I%20can%20see%20our%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2FDeployEdge%2Fmicrosoft-edge-policies%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3Epolicy%20documentation%26nbsp%3B%3C%2FA%3Ehas%20been%20updated%20to%20say%20%22blocklist%22%20and%20%22allowlist%22%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAre%20you%20seeing%20differently%20in%20the%20ADMX%20files%3F%26nbsp%3B%20Let%20me%20know%20if%20you%20are%20having%20an%20issue%20and%20I'll%20check%20with%20our%20team.%26nbsp%3B%20Thanks!%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CEM%3E-Kelly%3C%2FEM%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Contributor

Hi there - I noticed that as of version 87 in Chrome, the following upstream changes have been made in Chromium:

 

Rename classes in components/blacklist to use more inclusive names. (I8a1a7d7b) · Gerrit Code Review...

 

I'm wondering if these will make their way into Edge so we can plan importing new ADMX files accordingly.

 

Thanks!

3 Replies
best response confirmed by lexcyn (Contributor)
Solution

@lexcyn Hello!  Thanks for reaching out!  I can see our policy documentation has been updated to say "blocklist" and "allowlist" 

 

Are you seeing differently in the ADMX files?  Let me know if you are having an issue and I'll check with our team.  Thanks! 

 

-Kelly

@Kelly_Y thank you for the quick response! You know what, I probably should have checked before I posted. It seems our polices were always block/allow - we were just frazzled at the Chrome changes today since we only update our ADMX files quarterly or if there are any major changes.

 

Thanks for confirming :)

@lexcyn Great!  Thanks for following up and glad to hear everything is OK! 

 

-Kelly