Why take away the simple Script Editor / Embed web page in modern?

%3CLINGO-SUB%20id%3D%22lingo-sub-29060%22%20slang%3D%22en-US%22%3EWhy%20take%20away%20the%20simple%20Script%20Editor%20%2F%20Embed%20web%20page%20in%20modern%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-29060%22%20slang%3D%22en-US%22%3E%3CP%3EWhy%20are%20we%20losing%20the%20simple%20%22script%20editor%22%20%2F%20%22embed%22%20capability%20in%20modern%20sharepoint.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20understand%20SPFX%20is%20the%20future%2C%20and%20that%20I%20will%20have%20to%20learn%20all%20of%20that%20stuff%20at%20some%20point%2C%20but%20even%20glancing%20at%20some%20of%20the%20basic%20tutorials%2C%20it%20is%20like%20a%20giant%20process%20if%20I%20wanted%20to%20have%20just%20the%20simpliest%20little%20snippet%20of%20javascript%2Fhtml%2Fcss.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAs%20someone%20that%20never%20touches%20visual%20studio%20but%20has%20done%20so%20many%20simple%20scripts%2C%20it%20just%20seems%20like%20a%20lot%20of%20extra%20work%20for%20some%20simple%20little%20use%20cases.%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-29060%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3E2016%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EDeveloper%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-121211%22%20slang%3D%22en-US%22%3ERe%3A%20Why%20take%20away%20the%20simple%20Script%20Editor%20%2F%20Embed%20web%20page%20in%20modern%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-121211%22%20slang%3D%22en-US%22%3E%3CP%3EYou%20can%20use%20this%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2FSharePoint%2Fsp-dev-fx-webparts%2Ftree%2Fmaster%2Fsamples%2Freact-script-editor%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fgithub.com%2FSharePoint%2Fsp-dev-fx-webparts%2Ftree%2Fmaster%2Fsamples%2Freact-script-editor%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWorks%20fine!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-77364%22%20slang%3D%22en-US%22%3ERe%3A%20Why%20take%20away%20the%20simple%20Script%20Editor%20%2F%20Embed%20web%20page%20in%20modern%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-77364%22%20slang%3D%22en-US%22%3EI'll%20have%20to%20find%20another%20thread%20where%20we%20talked%20about%20this%2C%20but%20it%20is%20possible%2C%20Mikael%20Svenson%20put%20one%20together%2C%20and%20I%20have%20been%20able%20to%20easily%20port%20some%20existing%20stuff%20into%20it%2C%20with%20virtually%20no%20effort.%20So%20that%20is%20a%20win%20in%20my%20book.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-77355%22%20slang%3D%22en-US%22%3ERe%3A%20Why%20take%20away%20the%20simple%20Script%20Editor%20%2F%20Embed%20web%20page%20in%20modern%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-77355%22%20slang%3D%22en-US%22%3E%3CP%3EHI%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F637%22%20target%3D%22_blank%22%3E%40Brent%20Ellis%3C%2FA%3E%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EInitially%20I%20would%20agree%20with%20you%2C%20however%20having%20thought%20baout%20this%20for%20a%20bit%2C%20it%20might%20quite%20well%20be%20possible%20to%20create%20an%20SPFx%20Script%20web%20part.%20A%20web%20part%20with%20an%20additonal%20web%20part%20proporty%20containing%20the%20javascript%20of%20link%20to%20a%20javascript%20isn't%20too%20complicated%20to%20implement.%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-77344%22%20slang%3D%22en-US%22%3ERe%3A%20Why%20take%20away%20the%20simple%20Script%20Editor%20%2F%20Embed%20web%20page%20in%20modern%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-77344%22%20slang%3D%22en-US%22%3EThank%20you%20Jeremy%20for%20sharing%20your%20implementation.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-51318%22%20slang%3D%22en-US%22%3ERe%3A%20Why%20take%20away%20the%20simple%20Script%20Editor%20%2F%20Embed%20web%20page%20in%20modern%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-51318%22%20slang%3D%22en-US%22%3E%3CP%3ELittle%20late%20on%20the%20party%20but%20I%20ran%20into%20this%20as%20well.%20%26nbsp%3BTo%20resolve%20I%20ended%20up%20creating%20a%20modern%20web%20part%20in%20the%20SharePoint%20Framework%20that%20works%20on%20both%20Modern%20%26amp%3B%20Classic%20pages.%20%26nbsp%3BTo%20install%20you'll%20need%20to%20have%20the%20App%20Catalog%20deployed.%20%26nbsp%3BYou%20can%20either%20download%20my%20compiled%20package%20or%20build%20your%20own%20by%20cloning%20the%20github%20repo.%20In%20the%20next%20day%20or%202%26nbsp%3BI'll%20add%20an%26nbsp%3Boption%20for%20HTML%20to%20render%20natively%20on%20the%20page%20as%20well.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E*Update%2C%20I%20added%20the%20HTML%20editor%20%26amp%3B%20a%20screenshot%20below%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20title%3D%22Web%20Part%20Package%20Download%22%20href%3D%22https%3A%2F%2F1drv.ms%2Fu%2Fs!AslLVEUksauZg7QZeDg1vjLKw-kGnw%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3EWeb%20Part%20Package%20Download%3C%2FA%3E%26nbsp%3B-%26nbsp%3B%3CA%20title%3D%22Github%20Repo%22%20href%3D%22https%3A%2F%2Fgithub.com%2Fjcoleman-pcprofessional%2FTrue-Script-Editor%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3EGithub%20Repo%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20title%3D%22Setup%20App%20Catalog%22%20href%3D%22http%3A%2F%2Fblog.codeasite.com%2Fitem%2F55-how-to-add-an-app-catalog-to-sharepoint-online-to-make-custom-apps-available%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3ESetup%20App%20Catalog%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20blue%20splash%20tile%20will%20dissapear%20once%20you%20add%20any%20of%20the%205%20options%3A%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F11602i3DE92697277118AC%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22full.png%22%20title%3D%22full.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3BNew%20HTML%20Editor%20added%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F11604iF79978985736D2EC%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22True-Script-Editor.png%22%20title%3D%22True-Script-Editor.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-33217%22%20slang%3D%22en-US%22%3ERe%3A%20Why%20take%20away%20the%20simple%20Script%20Editor%20%2F%20Embed%20web%20page%20in%20modern%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-33217%22%20slang%3D%22en-US%22%3EFor%20anyone%20interested%2C%20starting%20a%20lobby%20to%20bring%20back%20SEWP%20in%20modern%20sharepoint.%3CBR%20%2F%3E%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fsharepoint.uservoice.com%2Fforums%2F329214-sites-and-collaboration%2Fsuggestions%2F17290130-bring-back-script-editor-web-part-in-modern-shar%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsharepoint.uservoice.com%2Fforums%2F329214-sites-and-collaboration%2Fsuggestions%2F17290130-bring-back-script-editor-web-part-in-modern-shar%3C%2FA%3E%3CBR%20%2F%3E______________%3CBR%20%2F%3E%3CBR%20%2F%3EThe%20Script%20Editor%20Web%20Part%20has%20been%20replaced%20by%20the%20Content%20Editor%20(which%20does%20a%20very%20limited%20iframe)%20and%20the%20new%20SPFX%20stuff.%20I%20am%20not%20a%20developer%2C%20but%20knowledgeable%20in%20HTML%2C%20Javascript%2C%20CSS.%20The%20SEWP%20met%20some%20very%20complex%20use%20cases%20(targeted%20for%20replacement%20by%20SPFX)%2C%20but%20also%20some%20very%20simple%20use%20cases.%3CBR%20%2F%3E%3CBR%20%2F%3EExample%3A%20Insert%20a%20formatted%20single%20HTML%20button%2C%20something%20that%20is%20big%2C%20draws%20attention%2C%20and%20encourages%20the%20user%20to%20click%20it%20to%20start%20an%20action.%3CBR%20%2F%3E%3CBR%20%2F%3EWhat%20might%20be%20just%202%20lines%20of%20code%2C%20has%20now%20turned%20into%20(what%20looks%20like)%20hundreds%20of%20files%20of%20deployment%2C%20installing%20all%20kinds%20of%20tools%20that%20I%20have%20never%20heard%20of%20or%20know%20what%20they%20are%20actually%20doing%20in%20the%20background.%3CBR%20%2F%3E%3CBR%20%2F%3EI%20am%20finding%20SPFX%20to%20be%20specifically%20geared%20toward%20professional%20developers%20and%20limiting%20%22citizen%22%20developers%20from%20adding%20just%20simple%20things%20to%20SharePoint%20pages.%20I%20am%20trying%20to%20learn%20it%2C%20but%20there%20are%20so%20many%20things%20above%20my%20head%20at%20this%20point%2C%20and%20my%20role%20is%20not%20to%20be%20a%20full-time%20developer.%3CBR%20%2F%3E%3CBR%20%2F%3EThis%20is%20to%20lobby%20to%20bring%20back%20the%20Script%20Editor%20Web%20Part%20to%20meet%20simple%20use%20cases%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-29200%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Why%20take%20away%20the%20simple%20Script%20Editor%20%2F%20Embed%20web%20page%20in%20modern%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-29200%22%20slang%3D%22en-US%22%3EEy%20Brent%2C%3CBR%20%2F%3EYou%20can%20expect%20something%20coming%20in%20the%20new%20SPFx%2C%20but%20for%20now%20there%20is%20nothing%20we%20can%20share%20with%20you%20about%20how%20to%20replace%20Script%20Editor%20WebPart%20features%20in%20the%20modern%20SPO%20pages...just%20remember%20that%20SPFx%20is%20in%20preview%20and%20evolving%20really%20fast%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-29117%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Why%20take%20away%20the%20simple%20Script%20Editor%20%2F%20Embed%20web%20page%20in%20modern%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-29117%22%20slang%3D%22en-US%22%3EQuoting%20for%20reference%3CBR%20%2F%3E%3CBR%20%2F%3E%22There%20are%20a%20couple%20of%20downsides%20to%20this%20approach%2C%20though.%20First%2C%20while%20you%20can%20package%20up%20your%20solution%20so%20that%20end%20users%20can%20drop%20the%20control%20onto%20the%20page%2C%20there%20isn%E2%80%99t%20really%20an%20easy%20way%20to%20provide%20configuration%20options.%20Additionally%2C%20the%20end%20user%20can%20edit%20the%20page%20and%20modify%20the%20script%2C%20breaking%20the%20web%20part.%20Another%20big%20problem%20is%20that%20the%20script%20editor%20web%20part%20is%20not%20marked%20as%20%22Safe%20For%20Scripting%22.%20Most%20self-service%20site%20collections%20(my-sites%2C%20team%20sites%2C%20group%20sites%2C%20etc.)%20have%20a%20feature%20known%20as%20%22NoScript%22%20enabled.%20Technically%2C%20it%20is%20the%20removal%20of%20Add%2FCustomize%20Pages%20(ACP)%20permission%20in%20SharePoint.%20What%20this%20means%20for%20a%20developer%20though%2C%20is%20that%20the%20script%20editor%20web%20part%20will%20be%20blocked%20from%20executing%20on%20these%20sites.%22%3CBR%20%2F%3E%3CBR%20%2F%3EBoo.%20So%20in%20my%20opinion%2C%20Microsoft%20has%20swung%20too%20far%20on%20the%20pendulum%20swing%20in%20the%20trying%20to%20protect%20users.%20Over%20complicating%20things%20to%20try%20and%20stop%20a%20problem%20that%20most%20I%20think%20would%20argue%20is%20not%20really%20a%20problem.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-29109%22%20slang%3D%22en-US%22%3ERE%3A%20Why%20take%20away%20the%20simple%20Script%20Editor%20%2F%20Embed%20web%20page%20in%20modern%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-29109%22%20slang%3D%22en-US%22%3EAlso%20Brent%20if%20you%20haven't%20watched%20BRK2115%2C%20THR2153%2C%20or%20BRK2114%20on%20SPFx%20from%20MSIgnite%2C%20I%20highly%20recommend%20them.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-29104%22%20slang%3D%22en-US%22%3ERE%3A%20Why%20take%20away%20the%20simple%20Script%20Editor%20%2F%20Embed%20web%20page%20in%20modern%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-29104%22%20slang%3D%22en-US%22%3EThere%20was%20something%20posted%20on%20the%20Script%20Editor%20web%20part%20missing%20from%20SPFx%20posted%20on%20Microsoft's%20GitHub%20page%3A%20%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2FSharePoint%2Fsp-dev-docs%2Fwiki%2FWhy-SPFx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fgithub.com%2FSharePoint%2Fsp-dev-docs%2Fwiki%2FWhy-SPFx%3C%2FA%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-29091%22%20slang%3D%22en-US%22%3ERe%3A%20Why%20take%20away%20the%20simple%20Script%20Editor%20%2F%20Embed%20web%20page%20in%20modern%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-29091%22%20slang%3D%22en-US%22%3EI%20don't%20believe%20it%20can%20be%20done%20in%20Modern%20SharePoint.%20(someone%20correct%20me%20if%20i%20am%20wrong)%2C%20but%20if%20I%20wanted%20to%20do%20something%20like%20described%20below%2C%20I%20would%20have%20to%20do%20all%20kinds%20of%20stuff%20with%20SPFX%20just%20to%20make%20it%20happen.%3CBR%20%2F%3E%3CBR%20%2F%3EHere%20is%20a%20simple%20use%20case%3A%3CBR%20%2F%3E%3CBR%20%2F%3EI%20want%20to%20embed%20a%20button%20to%20make%20it%20look%20a%20certain%20way%20on%20a%20SharePoint%20page%2C%20so%20I%20might%20do%20something%20like%20this%3A%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSTYLE%3E%26amp%3Bamp%3Bamp%3Bamp%3Blt%3BBR%20%2F%26amp%3Bamp%3Bamp%3Bamp%3Bgt%3B.mystyle%7B%20color%3Ablue%20%7D%26amp%3Bamp%3Bamp%3Bamp%3Blt%3BBR%20%2F%26amp%3Bamp%3Bamp%3Bamp%3Bgt%3B.mystyle%3Ahover%7B%20color%3Awhite%20%7D%26amp%3Bamp%3Bamp%3Bamp%3Blt%3BBR%20%2F%26amp%3Bamp%3Bamp%3Bamp%3Bgt%3B%3C%2FSTYLE%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CA%20href%3D%22%26quot%3Bmy%22%20link%3D%22%22%20here%3D%22%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3EClick%20here%20to%20access%20application%20X%3C%2FA%3E%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-29074%22%20slang%3D%22en-US%22%3ERe%3A%20Why%20take%20away%20the%20simple%20Script%20Editor%20%2F%20Embed%20web%20page%20in%20modern%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-29074%22%20slang%3D%22en-US%22%3E%3CP%3EHey%20Brent.%20Just%20to%20clarify%20you're%20acknowledging%20that%20it%20still%20can%20be%20done%2C%20but%20it's%20just%20too%20difficult%20(making%20sure%20we%20can%20bring%20this%20to%20the%20SHarePoint%20team).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFrom%20my%20non-coder%20experience%20the%20embed%20is%20better%20than%20it%20has%20been%20in%20the%20past.%20What%20are%20you%20trying%20to%20achieve%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Valued Contributor

Why are we losing the simple "script editor" / "embed" capability in modern sharepoint.

 

I understand SPFX is the future, and that I will have to learn all of that stuff at some point, but even glancing at some of the basic tutorials, it is like a giant process if I wanted to have just the simpliest little snippet of javascript/html/css.

 

As someone that never touches visual studio but has done so many simple scripts, it just seems like a lot of extra work for some simple little use cases.

 

 

12 Replies
Highlighted

Hey Brent. Just to clarify you're acknowledging that it still can be done, but it's just too difficult (making sure we can bring this to the SHarePoint team).

 

From my non-coder experience the embed is better than it has been in the past. What are you trying to achieve?

Highlighted
I don't believe it can be done in Modern SharePoint. (someone correct me if i am wrong), but if I wanted to do something like described below, I would have to do all kinds of stuff with SPFX just to make it happen.

Here is a simple use case:

I want to embed a button to make it look a certain way on a SharePoint page, so I might do something like this:

<style>
.mystyle{ color:blue }
.mystyle:hover{ color:white }
</style>

<a href="my link here" class="mystyle">Click here to access application X</a>
Highlighted
There was something posted on the Script Editor web part missing from SPFx posted on Microsoft's GitHub page: https://github.com/SharePoint/sp-dev-docs/wiki/Why-SPFx
Highlighted
Also Brent if you haven't watched BRK2115, THR2153, or BRK2114 on SPFx from MSIgnite, I highly recommend them.
Highlighted
Quoting for reference

"There are a couple of downsides to this approach, though. First, while you can package up your solution so that end users can drop the control onto the page, there isn’t really an easy way to provide configuration options. Additionally, the end user can edit the page and modify the script, breaking the web part. Another big problem is that the script editor web part is not marked as "Safe For Scripting". Most self-service site collections (my-sites, team sites, group sites, etc.) have a feature known as "NoScript" enabled. Technically, it is the removal of Add/Customize Pages (ACP) permission in SharePoint. What this means for a developer though, is that the script editor web part will be blocked from executing on these sites."

Boo. So in my opinion, Microsoft has swung too far on the pendulum swing in the trying to protect users. Over complicating things to try and stop a problem that most I think would argue is not really a problem.
Highlighted
Ey Brent,
You can expect something coming in the new SPFx, but for now there is nothing we can share with you about how to replace Script Editor WebPart features in the modern SPO pages...just remember that SPFx is in preview and evolving really fast
Highlighted
For anyone interested, starting a lobby to bring back SEWP in modern sharepoint.

https://sharepoint.uservoice.com/forums/329214-sites-and-collaboration/suggestions/17290130-bring-ba...
______________

The Script Editor Web Part has been replaced by the Content Editor (which does a very limited iframe) and the new SPFX stuff. I am not a developer, but knowledgeable in HTML, Javascript, CSS. The SEWP met some very complex use cases (targeted for replacement by SPFX), but also some very simple use cases.

Example: Insert a formatted single HTML button, something that is big, draws attention, and encourages the user to click it to start an action.

What might be just 2 lines of code, has now turned into (what looks like) hundreds of files of deployment, installing all kinds of tools that I have never heard of or know what they are actually doing in the background.

I am finding SPFX to be specifically geared toward professional developers and limiting "citizen" developers from adding just simple things to SharePoint pages. I am trying to learn it, but there are so many things above my head at this point, and my role is not to be a full-time developer.

This is to lobby to bring back the Script Editor Web Part to meet simple use cases
Highlighted

Little late on the party but I ran into this as well.  To resolve I ended up creating a modern web part in the SharePoint Framework that works on both Modern & Classic pages.  To install you'll need to have the App Catalog deployed.  You can either download my compiled package or build your own by cloning the github repo. In the next day or 2 I'll add an option for HTML to render natively on the page as well.

 

*Update, I added the HTML editor & a screenshot below

 

Web Part Package Download - Github Repo

 

Setup App Catalog

 

The blue splash tile will dissapear once you add any of the 5 options:

full.png

 New HTML Editor added

True-Script-Editor.png

Highlighted
Thank you Jeremy for sharing your implementation.
Highlighted

HI @Brent Ellis,

 

Initially I would agree with you, however having thought baout this for a bit, it might quite well be possible to create an SPFx Script web part. A web part with an additonal web part proporty containing the javascript of link to a javascript isn't too complicated to implement.

 

 

Highlighted
I'll have to find another thread where we talked about this, but it is possible, Mikael Svenson put one together, and I have been able to easily port some existing stuff into it, with virtually no effort. So that is a win in my book.