2 Microsoft Edge Community

%3CLINGO-SUB%20id%3D%22lingo-sub-1114353%22%20slang%3D%22en-US%22%3E2%20Microsoft%20Edge%20Community%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1114353%22%20slang%3D%22en-US%22%3E%3CUL%3E%3CLI%3E%3CFONT%20size%3D%224%22%3E%3CSTRONG%3EProblem%3A%3C%2FSTRONG%3E%3C%2FFONT%3E%3C%2FLI%3E%3C%2FUL%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThere%20are%202%20Microsoft%20Edge%20communities%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20one%3A%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fmicrosoft-edge%2Fct-p%2FMicrosoftEdge%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fmicrosoft-edge%2Fct-p%2FMicrosoftEdge%3C%2FA%3E%3C%2FP%3E%3CP%3Ewas%20created%20for%20the%20UWP%20Edge%20browser%20that%20is%20%3CU%3Enow%20called%20Legacy%20Edge%3C%2FU%3E%20%3CEM%3EBy%20Microsoft%20and%20everyone%3C%2FEM%3E%3CU%3E%3CBR%20%2F%3E%3C%2FU%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnd%20this%20one%3A%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fmicrosoft-edge-insider%2Fct-p%2FMicrosoftEdgeInsider%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fmicrosoft-edge-insider%2Fct-p%2FMicrosoftEdgeInsider%3C%2FA%3E%3C%2FP%3E%3CP%3Ewas%20recently%20created%20for%20the%20new%20Microsoft%20Edge%20browser%20(Chromium-based)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20seen%20new%20users%20posting%20on%20the%20former%20community%20about%20the%20new%20Edge%20browser%20because%20both%20of%20them%20have%20similar%20names.%20the%20developers%20of%20the%20new%20Chromium%20based%20Edge%20browser%20are%20only%20available%20and%20active%20on%20the%20new%20community%2C%20at%20least%20that's%20how%20it%20looks%20like.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CUL%3E%3CLI%3E%3CFONT%20size%3D%224%22%3E%3CSTRONG%3ESolution%3A%3C%2FSTRONG%3E%3C%2FFONT%3E%3C%2FLI%3E%3C%2FUL%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eit%20would%20be%20better%20if%20this%20community%3A%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fmicrosoft-edge%2Fct-p%2FMicrosoftEdge%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fmicrosoft-edge%2Fct-p%2FMicrosoftEdge%3C%2FA%3E%3C%2FP%3E%3CP%3Ewas%20called%20%22(Legacy)%20Microsoft%20Edge%22%20instead%20of%20%22Microsoft%20Edge%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eand%20in%20its%20description%2C%20it%20would%20be%20clearly%20stated%20that%20it%20is%20about%20the%20UWP%20Edge%20browser%20that%20is%20based%20on%20EdgeHTML%20engine.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnd%20this%20community%3A%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fmicrosoft-edge-insider%2Fct-p%2FMicrosoftEdgeInsider%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fmicrosoft-edge-insider%2Fct-p%2FMicrosoftEdgeInsider%3C%2FA%3E%3C%2FP%3E%3CP%3Ewould%20be%20called%20%22Microsoft%20Edge%20stable%20%2B%20Insider%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eand%20in%20its%20description%20it%20would%20be%20clearly%20stated%20that%20it%20is%20about%20both%20stable%2Ffinal%20and%20insider%20channels%20of%20new%20Edge%20browser%20that%20is%20based%20on%20Chromium%20engine.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3EPlus%20these%20changes%3A%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CUL%3E%3CLI%3EAdd%20special%20**mandatory%20colorful%20tags%20when%20new%20users%20want%20to%20create%20a%20post%20so%20their%20posts%20will%20be%20easily%20identified%20when%20they%20are%20about%20the%20stable%20channel%20(%3CA%20href%3D%22https%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fedge%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3Enon-insider%20Chromium%20based%20Edge%20browser%3C%2FA%3E).%3C%2FLI%3E%3CLI%3Eby%20mandatory%20tagging%2C%20I%20mean%20a%20user%20should%20always%20choose%20a%20tag%20(%3CSTRONG%3E%3CFONT%20color%3D%22%230000FF%22%3EStable%3C%2FFONT%3E%2F%3CFONT%20color%3D%22%2300FFFF%22%3EBeta%3C%2FFONT%3E%2F%3CFONT%20color%3D%22%2300FF00%22%3EDeveloper%3C%2FFONT%3E%2F%3CFONT%20color%3D%22%23FF9900%22%3ECanary%3C%2FFONT%3E%3C%2FSTRONG%3E)%20before%20they%20can%20submit%20their%20post.%20the%20colors%20above%20reflect%20the%20correct%20tag%20color%20of%20%3CA%20href%3D%22https%3A%2F%2Fwww.microsoftedgeinsider.com%2Fen-us%2Fdownload%2F%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Eeach%203%20Insider%20channels.%3C%2FA%3E%3C%2FLI%3E%3CLI%3EAlso%20add%20a%20tag%20(%3CSTRONG%3E%3CFONT%20color%3D%22%23808080%22%3EGeneral%3C%2FFONT%3E%3C%2FSTRONG%3E)%20for%20users%20that%20want%20to%20ask%20questions%20and%20discuss%20something%20that%20is%20not%20related%20to%20any%20of%20the%20channels%20but%20about%20the%20overall%20Edge%20browser%20experience.%3C%2FLI%3E%3C%2FUL%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E**%20the%20reason%20for%20tags%20being%20mandatory%20is%20that%20there%20has%20been%20numerous%20times%20when%20a%20user%20posts%20a%20question%2Fbug%2Fproblem%20about%20the%20new%20Edge%20browser%20and%20they%20forget%20to%20mention%20the%20channel%20they%20are%20using.%20so%20the%20person%20who%20wants%20to%20help%20them%20needs%20to%20first%20ask%20which%20channel%20they%20are%20using.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eanother%20reason%20for%20mandatory%20tagging%20is%20that%2C%20even%20if%20the%20user%20posting%20a%20topic%20about%20the%20new%20Edge%20browser%2C%20did%20mention%20the%20version%20number%20he%2Fshe%20is%20using%2C%20it%20still%20needs%20to%20be%20tagged%20and%20mentioned%20which%20channel%20it%20is%20on.%3C%2FP%3E%3CP%3E%3CSTRONG%3Ebecause%20the%20same%20version%20number%20of%20the%20Edge%20browser%20can%2Fwill%20be%20used%20in%204%20different%20channels%20during%20a%20period%20of%20time%2C%20respectively.%20%3C%2FSTRONG%3Ethis%20has%20happened%20between%20Canary%2FDev%20and%20between%20Beta%2FStable%20channels.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1114353%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ECommunity%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1133394%22%20slang%3D%22en-US%22%3ERE%3A%202%20Microsoft%20Edge%20Community%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1133394%22%20slang%3D%22en-US%22%3EThanks%20for%20the%20suggestion.%20I've%20passed%20it%20along%20to%20the%20Edge%20Insiders%20team.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1134270%22%20slang%3D%22en-US%22%3ERE%3A%202%20Microsoft%20Edge%20Community%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1134270%22%20slang%3D%22en-US%22%3EGreat%2C%20thank%20you!%3C%2FLINGO-BODY%3E
Honored Contributor
  • Problem:

 

There are 2 Microsoft Edge communities:

 

This one:

https://techcommunity.microsoft.com/t5/microsoft-edge/ct-p/MicrosoftEdge

was created for the UWP Edge browser that is now called Legacy Edge By Microsoft and everyone

 

And this one:

https://techcommunity.microsoft.com/t5/microsoft-edge-insider/ct-p/MicrosoftEdgeInsider

was recently created for the new Microsoft Edge browser (Chromium-based)

 

I've seen new users posting on the former community about the new Edge browser because both of them have similar names. the developers of the new Chromium based Edge browser are only available and active on the new community, at least that's how it looks like.

 

 

  • Solution:

 

 

it would be better if this community:

https://techcommunity.microsoft.com/t5/microsoft-edge/ct-p/MicrosoftEdge

was called "(Legacy) Microsoft Edge" instead of "Microsoft Edge"

 

and in its description, it would be clearly stated that it is about the UWP Edge browser that is based on EdgeHTML engine.

 

And this community:

https://techcommunity.microsoft.com/t5/microsoft-edge-insider/ct-p/MicrosoftEdgeInsider

would be called "Microsoft Edge stable + Insider"

 

and in its description it would be clearly stated that it is about both stable/final and insider channels of new Edge browser that is based on Chromium engine.

 

Plus these changes:

 

  • Add special **mandatory colorful tags when new users want to create a post so their posts will be easily identified when they are about the stable channel (non-insider Chromium based Edge browser).
  • by mandatory tagging, I mean a user should always choose a tag (Stable/Beta/Developer/Canary) before they can submit their post. the colors above reflect the correct tag color of each 3 Insider channels.
  • Also add a tag (General) for users that want to ask questions and discuss something that is not related to any of the channels but about the overall Edge browser experience.

 

** the reason for tags being mandatory is that there has been numerous times when a user posts a question/bug/problem about the new Edge browser and they forget to mention the channel they are using. so the person who wants to help them needs to first ask which channel they are using.

 

another reason for mandatory tagging is that, even if the user posting a topic about the new Edge browser, did mention the version number he/she is using, it still needs to be tagged and mentioned which channel it is on.

because the same version number of the Edge browser can/will be used in 4 different channels during a period of time, respectively. this has happened between Canary/Dev and between Beta/Stable channels.

 

2 Replies
Thanks for the suggestion. I've passed it along to the Edge Insiders team.
Great, thank you!