Home

The old extension store website need to be replaced

%3CLINGO-SUB%20id%3D%22lingo-sub-1182276%22%20slang%3D%22en-US%22%3EThe%20old%20extension%20store%20website%20need%20to%20be%20replaced%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1182276%22%20slang%3D%22en-US%22%3E%3CP%3EUsing%20Microsoft%20Bing%2C%20searching%20for%20an%20extension%20like%20ublock%20origin%2C%20shows%20me%20this%20result%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20image-alt%3D%22gfdgd.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F172042i904623495BA05A5D%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%22gfdgd.png%22%20alt%3D%22gfdgd.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ethis%20is%20the%20link%3A%20%3CA%20href%3D%22https%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fp%2Fublock-origin%2F9nblggh444l4%3Factivetab%3Dpivot%3Aoverviewtab%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fp%2Fublock-origin%2F9nblggh444l4%3Factivetab%3Dpivot%3Aoverviewtab%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eit%20is%20the%20old%20extension%20store%20belonging%20to%20legacy%20Edge.%3C%2FP%3E%3CP%3Ethe%20new%20one%20is%20here%3A%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fmicrosoftedge.microsoft.com%2Faddons%2Fdetail%2Fodfafepnkmbhccpbejgmiehpchacaeak%3Fhl%3Den-US%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fmicrosoftedge.microsoft.com%2Faddons%2Fdetail%2Fodfafepnkmbhccpbejgmiehpchacaeak%3Fhl%3Den-US%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eso%20either%20automatically%20redirect%20URLs%20to%20the%20new%20store%20or%20just%20retire%20that%20old%20store.%20it's%20confusing%20for%20people%20who%20are%20not%20tech%20savvy.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1182276%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3Eextensions%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EFeedback%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Eproblem%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Estore%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Ewebsite%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1182520%22%20slang%3D%22en-US%22%3ERe%3A%20The%20old%20extension%20store%20website%20need%20to%20be%20replaced%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1182520%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F310193%22%20target%3D%22_blank%22%3E%40HotCakeX%3C%2FA%3E%26nbsp%3BAnd%20how%20do%20you%20suggest%20legacy%20Edge%20users%20to%20install%20extensions%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1182623%22%20slang%3D%22en-US%22%3ERe%3A%20The%20old%20extension%20store%20website%20need%20to%20be%20replaced%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1182623%22%20slang%3D%22en-US%22%3EAnd%20How%20do%20you%20suggest%20new%20Edge%20users%20don't%20get%20misled%20by%20these%20search%20results%3F%3CBR%20%2F%3Ethere%20is%20a%20reason%20why%20Microsoft%20calls%20EdgeHTML%20Legacy.%20you%20shouldn't%20expect%20the%20experience%20to%20be%20the%20same.%3CBR%20%2F%3Ethe%20Legacy%20Edge%20is%20only%20staying%20for%20compatibility%20purposes.%20compatibility%20means%20only%20its%20engine%2C%20EdgeHTML%2C%20not%20the%20old%20extensions%20that%20it%20used%20and%20they%20are%20all%20available%20for%20the%20new%20Edge.%3CBR%20%2F%3Ealso%20Legacy%20Edge%20extensions%20can%20be%20installed%20from%20Windows%20store.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1182699%22%20slang%3D%22en-US%22%3ERe%3A%20The%20old%20extension%20store%20website%20need%20to%20be%20replaced%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1182699%22%20slang%3D%22en-US%22%3EThe%20problem%20is%20that%20the%20stable%20channel%20of%20the%20new%20Edge%20isn't%20available%20on%20Windows%2010%201507-1809.%20Removing%20links%20to%20the%20legacy%20extensions%20in%20the%20search%20means%20that%20these%20extensions%20should%20be%20removed.%20For%20example%2C%20I%20can%20not%20update%20to%201903%20on%20some%20of%20my%20computers%20because%20there%20is%20not%20GPU%20driver%20what%20works%20with%201903.%20The%20search%20results%2C%20actually%2C%20ranks%20by%20popularity%2C%20and%20you%20can%20do%20nothing%20until%20market%20share%20of%20the%20ChrEdge%20will%20exceed%20the%20market%20share%20of%20the%20old%20one.%20Removing%20the%20legacy%20extensions%20would%20be%20a%20big%20fault.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1182708%22%20slang%3D%22en-US%22%3ERe%3A%20The%20old%20extension%20store%20website%20need%20to%20be%20replaced%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1182708%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F505175%22%20target%3D%22_blank%22%3E%40msekmfb1%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CDIV%20class%3D%22lia-spoiler-container%22%3E%3CA%20class%3D%22lia-spoiler-link%22%20href%3D%22%23%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3ESpoiler%3C%2FA%3E%3CNOSCRIPT%3E(Highlight%20to%20read)%3C%2FNOSCRIPT%3E%3CDIV%20class%3D%22lia-spoiler-border%22%3E%3CDIV%20class%3D%22lia-spoiler-content%22%3E%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F505175%22%20target%3D%22_blank%22%3E%40msekmfb1%3C%2FA%3E%26nbsp%3Bwrote%3A%3CBR%20%2F%3EThe%20problem%20is%20that%20the%20stable%20channel%20of%20the%20new%20Edge%20isn't%20available%20on%20Windows%2010%201507-1809.%20Removing%20links%20to%20the%20legacy%20extensions%20in%20the%20search%20means%20that%20these%20extensions%20should%20be%20removed.%20For%20example%2C%20I%20can%20not%20update%20to%201903%20on%20some%20of%20my%20computers%20because%20there%20is%20not%20GPU%20driver%20what%20works%20with%201903.%20The%20search%20results%2C%20actually%2C%20ranks%20by%20popularity%2C%20and%20you%20can%20do%20nothing%20until%20market%20share%20of%20the%20ChrEdge%20will%20exceed%20the%20market%20share%20of%20the%20old%20one.%20Removing%20the%20legacy%20extensions%20would%20be%20a%20big%20fault.%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%3C%2FDIV%3E%3CNOSCRIPT%3E%3CDIV%20class%3D%22lia-spoiler-noscript-container%22%3E%3CDIV%20class%3D%22lia-spoiler-noscript-content%22%3E%26nbsp%3Bwrote%3AThe%20problem%20is%20that%20the%20stable%20channel%20of%20the%20new%20Edge%20isn't%20available%20on%20Windows%2010%201507-1809.%20Removing%20links%20to%20the%20legacy%20extensions%20in%20the%20search%20means%20that%20these%20extensions%20should%20be%20removed.%20For%20example%2C%20I%20can%20not%20update%20to%201903%20on%20some%20of%20my%20computers%20because%20there%20is%20not%20GPU%20driver%20what%20works%20with%201903.%20The%20search%20results%2C%20actually%2C%20ranks%20by%20popularity%2C%20and%20you%20can%20do%20nothing%20until%20market%20share%20of%20the%20ChrEdge%20will%20exceed%20the%20market%20share%20of%20the%20old%20one.%20Removing%20the%20legacy%20extensions%20would%20be%20a%20big%20fault.%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FNOSCRIPT%3E%3C%2FDIV%3E%3C%2FDIV%3E%3CP%3EThat's%20Perfectly%20Ok.%3CBR%20%2F%3Ethose%20versions%20are%20obsolete%2C%20out%20dated%20and%20not%20to%20be%20used%20by%20anyone.%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F13853%2Fwindows-lifecycle-fact-sheet%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F13853%2Fwindows-lifecycle-fact-sheet%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1182790%22%20slang%3D%22en-US%22%3ERe%3A%20The%20old%20extension%20store%20website%20need%20to%20be%20replaced%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1182790%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F310193%22%20target%3D%22_blank%22%3E%40HotCakeX%3C%2FA%3E%26nbsp%3BMicrosoft%20cannot%20get%20rid%20of%20the%20legacy%20Edge%20at%20least%20because%20it%20tied%20with%20Windows%20like%20no%20one%20component%2C%20even%20more%20than%20IE%2C%20for%20example%2C%20taskbar%20search%20box%2C%201909%2B%20explorer%20search%20(that's%20why%20it's%20too%20bad)%20and%20more%20of%20other%20UI%20parts%20is%20rendering%20using%20EdgeHTML.%20Windows%20team%2C%20as%20I%20know%2C%20no%20longer%20develops%20Edge%2C%20and%20it's%20too%20easy%20to%20remove%2Fdamage%20a%20Chromium%20distribution%2C%20what%20the%20new%20Edge%20is.%20That's%20a%20reason%20why%20the%20legacy%20Edge%20will%20always%20be%20present%20in%20Windows%2010.%20I%20enabled%20side-by-side%20experience%20because%20I%20need%20the%20legacy%20Edge%20for%20many%20reasons%2C%20so%20I%20need%20the%20extensions%2C%20and%20there%20no%20way%20to%20install%20them%20besides%20Microsoft%20Store.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1182797%22%20slang%3D%22en-US%22%3ERe%3A%20The%20old%20extension%20store%20website%20need%20to%20be%20replaced%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1182797%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F505175%22%20target%3D%22_blank%22%3E%40msekmfb1%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CDIV%20class%3D%22lia-spoiler-container%22%3E%3CA%20class%3D%22lia-spoiler-link%22%20href%3D%22%23%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3ESpoiler%3C%2FA%3E%3CNOSCRIPT%3E(Highlight%20to%20read)%3C%2FNOSCRIPT%3E%3CDIV%20class%3D%22lia-spoiler-border%22%3E%3CDIV%20class%3D%22lia-spoiler-content%22%3E%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F505175%22%20target%3D%22_blank%22%3E%40msekmfb1%3C%2FA%3E%26nbsp%3Bwrote%3A%3CBR%20%2F%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F310193%22%20target%3D%22_blank%22%3E%40HotCakeX%3C%2FA%3E%26nbsp%3BMicrosoft%20cannot%20get%20rid%20of%20the%20legacy%20Edge%20at%20least%20because%20it%20tied%20with%20Windows%20like%20no%20one%20component%2C%20even%20more%20than%20IE%2C%20for%20example%2C%20taskbar%20search%20box%2C%201909%2B%20explorer%20search%20(that's%20why%20it's%20too%20bad)%20and%20more%20of%20other%20UI%20parts%20is%20rendering%20using%20EdgeHTML.%20Windows%20team%2C%20as%20I%20know%2C%20no%20longer%20develops%20Edge%2C%20and%20it's%20too%20easy%20to%20remove%2Fdamage%20a%20Chromium%20distribution%2C%20what%20the%20new%20Edge%20is.%20That's%20a%20reason%20why%20the%20legacy%20Edge%20will%20always%20be%20present%20in%20Windows%2010.%20I%20enabled%20side-by-side%20experience%20because%20I%20need%20the%20legacy%20Edge%20for%20many%20reasons%2C%20so%20I%20need%20the%20extensions%2C%20and%20there%20no%20way%20to%20install%20them%20besides%20Microsoft%20Store.%3C%2FP%3E%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%3C%2FDIV%3E%3CNOSCRIPT%3E%3CDIV%20class%3D%22lia-spoiler-noscript-container%22%3E%3CDIV%20class%3D%22lia-spoiler-noscript-content%22%3E%26nbsp%3Bwrote%3A%26nbsp%3BMicrosoft%20cannot%20get%20rid%20of%20the%20legacy%20Edge%20at%20least%20because%20it%20tied%20with%20Windows%20like%20no%20one%20component%2C%20even%20more%20than%20IE%2C%20for%20example%2C%20taskbar%20search%20box%2C%201909%2B%20explorer%20search%20(that's%20why%20it's%20too%20bad)%20and%20more%20of%20other%20UI%20parts%20is%20rendering%20using%20EdgeHTML.%20Windows%20team%2C%20as%20I%20know%2C%20no%20longer%20develops%20Edge%2C%20and%20it's%20too%20easy%20to%20remove%2Fdamage%20a%20Chromium%20distribution%2C%20what%20the%20new%20Edge%20is.%20That's%20a%20reason%20why%20the%20legacy%20Edge%20will%20always%20be%20present%20in%20Windows%2010.%20I%20enabled%20side-by-side%20experience%20because%20I%20need%20the%20legacy%20Edge%20for%20many%20reasons%2C%20so%20I%20need%20the%20extensions%2C%20and%20there%20no%20way%20to%20install%20them%20besides%20Microsoft%20Store.%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FNOSCRIPT%3E%3C%2FDIV%3E%3C%2FDIV%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThat's%20unrelated.%3C%2FP%3E%3CP%3Elike%20it%20is%20tied%20with%20Windows%20like%20no%20one%20component%3F%20Microsoft%20Edge%20is%20just%20a%20browser.%20the%20Windows%20search%20uses%20something%20called%20Webview%20that%20also%20happens%20to%20be%20using%20EdgeHTML%2C%20for%20now.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ethe%20transition%20from%20Webview%201%20(EdgeHTML)%20to%20Webview%202%20(Chromium)%20is%20already%20being%20planned%3A%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoft-edge%2Fhosting%2Fwebview2%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoft-edge%2Fhosting%2Fwebview2%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ethese%20are%20still%20unrelated.%20%3CA%20href%3D%22http%3A%2F%2Fwww.Microsoft.com%2FEdge%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ewww.Microsoft.com%2FEdge%3C%2FA%3E%20points%20to%20the%20new%20Edge%2C%20Not%20the%20legacy%20Edge.%3C%2FP%3E%3CP%3Epeople%20who%20are%20not%20tech%20savvy%2C%20when%20search%20for%20an%20extension%2C%20shouldn't%20be%20misled%20by%20an%20extension%20that%20is%20for%20legacy%20Edge.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1182840%22%20slang%3D%22en-US%22%3ERe%3A%20The%20old%20extension%20store%20website%20need%20to%20be%20replaced%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1182840%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F310193%22%20target%3D%22_blank%22%3E%40HotCakeX%3C%2FA%3E%3C%2FP%3E%3CP%3EI%20misread%20your%20previous%20message.%3C%2FP%3E%3CP%3EIt's%20actually%26nbsp%3Bclosely%20connected%20with%20Windows%2C%20not%20the%20entire%20browser%2C%20but%20the%20rendering%20and%20JS%20engine.%20I%20see%20no%20way%20to%20replace%20it%20with%20the%20WebView2%2C%20in%20respect%20that%20WebView%20is%20needed%20for%20other%20purposes.%20Replacing%20the%20current%20rendering%20of%20system%20components%20using%20EdgeHTML%20with%20the%20new%20engine%20that%20constantly%20updates%20independent%20from%20the%20Windows%20lifecycle%20may%20broke%20that%20components%20anytime%2C%20search%2C%20for%20example%2C%20so%20Edge%20will%20never%20be%20removed%20from%20Windows.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1182864%22%20slang%3D%22en-US%22%3ERe%3A%20The%20old%20extension%20store%20website%20need%20to%20be%20replaced%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1182864%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F505175%22%20target%3D%22_blank%22%3E%40msekmfb1%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CDIV%20class%3D%22lia-spoiler-container%22%3E%3CA%20class%3D%22lia-spoiler-link%22%20href%3D%22%23%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3ESpoiler%3C%2FA%3E%3CNOSCRIPT%3E(Highlight%20to%20read)%3C%2FNOSCRIPT%3E%3CDIV%20class%3D%22lia-spoiler-border%22%3E%3CDIV%20class%3D%22lia-spoiler-content%22%3E%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F505175%22%20target%3D%22_blank%22%3E%40msekmfb1%3C%2FA%3E%26nbsp%3Bwrote%3A%3CBR%20%2F%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F310193%22%20target%3D%22_blank%22%3E%40HotCakeX%3C%2FA%3E%3C%2FP%3E%3CP%3EI%20misread%20your%20previous%20message.%3C%2FP%3E%3CP%3EIt's%20actually%26nbsp%3Bclosely%20connected%20with%20Windows%2C%20not%20the%20entire%20browser%2C%20but%20the%20rendering%20and%20JS%20engine.%20I%20see%20no%20way%20to%20replace%20it%20with%20the%20WebView2%2C%20in%20respect%20that%20WebView%20is%20needed%20for%20other%20purposes.%20Replacing%20the%20current%20rendering%20of%20system%20components%20using%20EdgeHTML%20with%20the%20new%20engine%20that%20constantly%20updates%20independent%20from%20the%20Windows%20lifecycle%20may%20broke%20that%20components%20anytime%2C%20search%2C%20for%20example%2C%20so%20Edge%20will%20never%20be%20removed%20from%20Windows.%3C%2FP%3E%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%3C%2FDIV%3E%3CNOSCRIPT%3E%3CDIV%20class%3D%22lia-spoiler-noscript-container%22%3E%3CDIV%20class%3D%22lia-spoiler-noscript-content%22%3E%26nbsp%3Bwrote%3AI%20misread%20your%20previous%20message.It's%20actually%26nbsp%3Bclosely%20connected%20with%20Windows%2C%20not%20the%20entire%20browser%2C%20but%20the%20rendering%20and%20JS%20engine.%20I%20see%20no%20way%20to%20replace%20it%20with%20the%20WebView2%2C%20in%20respect%20that%20WebView%20is%20needed%20for%20other%20purposes.%20Replacing%20the%20current%20rendering%20of%20system%20components%20using%20EdgeHTML%20with%20the%20new%20engine%20that%20constantly%20updates%20independent%20from%20the%20Windows%20lifecycle%20may%20broke%20that%20components%20anytime%2C%20search%2C%20for%20example%2C%20so%20Edge%20will%20never%20be%20removed%20from%20Windows.%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FNOSCRIPT%3E%3C%2FDIV%3E%3C%2FDIV%3E%3CP%3EYou're%20free%20to%20think%20whatever%20you%20want%20my%20friend.%20that's%20not%20my%20concern%20neither%20is%20it%20related%20to%20my%20post.%3C%2FP%3E%3CP%3Eyou're%20neither%20a%20Windows%20developer%20nor%20Windows%20is%20an%20open%20source%20software%2C%20so%20it's%20normal%20for%20you%20not%20seeing%20a%20way%20to%20replace%20WebView.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1182893%22%20slang%3D%22en-US%22%3ERe%3A%20The%20old%20extension%20store%20website%20need%20to%20be%20replaced%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1182893%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F310193%22%20target%3D%22_blank%22%3E%40HotCakeX%3C%2FA%3EMy%20words%20will%20be%20proved%20after%20a%20while.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1182956%22%20slang%3D%22en-US%22%3ERe%3A%20The%20old%20extension%20store%20website%20need%20to%20be%20replaced%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1182956%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F505175%22%20target%3D%22_blank%22%3E%40msekmfb1%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F505175%22%20target%3D%22_blank%22%3E%40msekmfb1%3C%2FA%3E%26nbsp%3Bwrote%3A%3CBR%20%2F%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F310193%22%20target%3D%22_blank%22%3E%40HotCakeX%3C%2FA%3EMy%20words%20will%20be%20proved%20after%20a%20while.%3C%2FP%3E%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe'll%20see%20%3B)%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1188526%22%20slang%3D%22en-US%22%3ERe%3A%20The%20old%20extension%20store%20website%20need%20to%20be%20replaced%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1188526%22%20slang%3D%22en-US%22%3EThe%20easy%20way%20to%20do%20it%20is%20to%20combine%20the%20extensions%20in%20the%20same%20store%2C%20so%20whenever%20you%20choose%20an%20extension%20to%20install%20you%20would%20be%20able%20to%20choose%20to%20install%20it%20on%20Chromium%20Edge%20or%20Legacy%20(if%20available%20on%20both)%20or%20the%20version%20of%20Edge%20where%20it%20is%20available.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1188624%22%20slang%3D%22en-US%22%3ERe%3A%20The%20old%20extension%20store%20website%20need%20to%20be%20replaced%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1188624%22%20slang%3D%22en-US%22%3ECombination%20sounds%20good%20too%2C%20they%20should%20do%20it%20in%20a%20way%20that%20search%20engines%20give%20more%20priority%20to%20the%20new%20extensions%20for%20Chromium%20based%20Edge.%3CBR%20%2F%3Ewhen%20you%20search%20in%20Google%20or%20Bing%20to%20download%20Edge%2C%20it%20doesn't%20take%20you%20to%20legacy%20Edge%20download%20page%2C%20it%20takes%20you%20to%20the%20New%20Edge%2C%20so%20extensions%20should%20do%20the%20same%20as%20well.%3CBR%20%2F%3Eotherwise%20it%20is%20inconsistent%20and%20confusing.%3C%2FLINGO-BODY%3E
Honored Contributor

Using Microsoft Bing, searching for an extension like ublock origin, shows me this result

 

 

 

gfdgd.png

 

 

 

this is the link: https://www.microsoft.com/en-us/p/ublock-origin/9nblggh444l4?activetab=pivot:overviewtab

 

it is the old extension store belonging to legacy Edge.

the new one is here:

https://microsoftedge.microsoft.com/addons/detail/odfafepnkmbhccpbejgmiehpchacaeak?hl=en-US

 

so either automatically redirect URLs to the new store or just retire that old store. it's confusing for people who are not tech savvy.

 

 

12 Replies
Highlighted

@HotCakeX And how do you suggest legacy Edge users to install extensions?

Highlighted
And How do you suggest new Edge users don't get misled by these search results?
there is a reason why Microsoft calls EdgeHTML Legacy. you shouldn't expect the experience to be the same.
the Legacy Edge is only staying for compatibility purposes. compatibility means only its engine, EdgeHTML, not the old extensions that it used and they are all available for the new Edge.
also Legacy Edge extensions can be installed from Windows store.
Highlighted
The problem is that the stable channel of the new Edge isn't available on Windows 10 1507-1809. Removing links to the legacy extensions in the search means that these extensions should be removed. For example, I can not update to 1903 on some of my computers because there is not GPU driver what works with 1903. The search results, actually, ranks by popularity, and you can do nothing until market share of the ChrEdge will exceed the market share of the old one. Removing the legacy extensions would be a big fault.
Highlighted

@msekmfb1 

Spoiler

@msekmfb1 wrote:
The problem is that the stable channel of the new Edge isn't available on Windows 10 1507-1809. Removing links to the legacy extensions in the search means that these extensions should be removed. For example, I can not update to 1903 on some of my computers because there is not GPU driver what works with 1903. The search results, actually, ranks by popularity, and you can do nothing until market share of the ChrEdge will exceed the market share of the old one. Removing the legacy extensions would be a big fault.

That's Perfectly Ok.
those versions are obsolete, out dated and not to be used by anyone.

https://support.microsoft.com/en-us/help/13853/windows-lifecycle-fact-sheet

Highlighted

@HotCakeX Microsoft cannot get rid of the legacy Edge at least because it tied with Windows like no one component, even more than IE, for example, taskbar search box, 1909+ explorer search (that's why it's too bad) and more of other UI parts is rendering using EdgeHTML. Windows team, as I know, no longer develops Edge, and it's too easy to remove/damage a Chromium distribution, what the new Edge is. That's a reason why the legacy Edge will always be present in Windows 10. I enabled side-by-side experience because I need the legacy Edge for many reasons, so I need the extensions, and there no way to install them besides Microsoft Store.

Highlighted

@msekmfb1 

 

Spoiler

@msekmfb1 wrote:

@HotCakeX Microsoft cannot get rid of the legacy Edge at least because it tied with Windows like no one component, even more than IE, for example, taskbar search box, 1909+ explorer search (that's why it's too bad) and more of other UI parts is rendering using EdgeHTML. Windows team, as I know, no longer develops Edge, and it's too easy to remove/damage a Chromium distribution, what the new Edge is. That's a reason why the legacy Edge will always be present in Windows 10. I enabled side-by-side experience because I need the legacy Edge for many reasons, so I need the extensions, and there no way to install them besides Microsoft Store.


 

That's unrelated.

like it is tied with Windows like no one component? Microsoft Edge is just a browser. the Windows search uses something called Webview that also happens to be using EdgeHTML, for now.

 

the transition from Webview 1 (EdgeHTML) to Webview 2 (Chromium) is already being planned:

https://docs.microsoft.com/en-us/microsoft-edge/hosting/webview2

 

these are still unrelated. www.Microsoft.com/Edge points to the new Edge, Not the legacy Edge.

people who are not tech savvy, when search for an extension, shouldn't be misled by an extension that is for legacy Edge.

 

 

Highlighted

@HotCakeX

I misread your previous message.

It's actually closely connected with Windows, not the entire browser, but the rendering and JS engine. I see no way to replace it with the WebView2, in respect that WebView is needed for other purposes. Replacing the current rendering of system components using EdgeHTML with the new engine that constantly updates independent from the Windows lifecycle may broke that components anytime, search, for example, so Edge will never be removed from Windows.

Highlighted

@msekmfb1 

Spoiler

@msekmfb1 wrote:

@HotCakeX

I misread your previous message.

It's actually closely connected with Windows, not the entire browser, but the rendering and JS engine. I see no way to replace it with the WebView2, in respect that WebView is needed for other purposes. Replacing the current rendering of system components using EdgeHTML with the new engine that constantly updates independent from the Windows lifecycle may broke that components anytime, search, for example, so Edge will never be removed from Windows.


You're free to think whatever you want my friend. that's not my concern neither is it related to my post.

you're neither a Windows developer nor Windows is an open source software, so it's normal for you not seeing a way to replace WebView.

 

 

Highlighted

@HotCakeXMy words will be proved after a while.

Highlighted

@msekmfb1 


@msekmfb1 wrote:

@HotCakeXMy words will be proved after a while.


 

We'll see ;)

Highlighted
The easy way to do it is to combine the extensions in the same store, so whenever you choose an extension to install you would be able to choose to install it on Chromium Edge or Legacy (if available on both) or the version of Edge where it is available.
Highlighted
Combination sounds good too, they should do it in a way that search engines give more priority to the new extensions for Chromium based Edge.
when you search in Google or Bing to download Edge, it doesn't take you to legacy Edge download page, it takes you to the New Edge, so extensions should do the same as well.
otherwise it is inconsistent and confusing.