Exit Classic Experience link in document library within Add-In Webs?

%3CLINGO-SUB%20id%3D%22lingo-sub-222390%22%20slang%3D%22en-US%22%3EExit%20Classic%20Experience%20link%20in%20document%20library%20within%20Add-In%20Webs%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-222390%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOur%26nbsp%3Badd-in%2Fapp%20includes%20a%20document%20library%20instance%20used%20for%20storing%20customisable%20image%20assets.%20A%20few%20months%20ago%20the%20%22Exit%20classic%20experience%22%20link%20started%20appearing%20at%20the%20top%20of%20the%20list%20view%20pages%2C%20however%20the%20link%20does%20nothing.%20I%20thought%20it%20was%26nbsp%3Ba%20glitch%20that%20would%20go%20away%2C%20however%20it%26nbsp%3Bpersists%20even%20in%20newly-installed%20copies%20of%20our%20add-in%2C%20and%20a%20recent%20bug-fix%20we%20submitted%20to%20Microsoft%20just%20got%20rejected%20because%20the%20link%20made%20the%20add-in%20%22look%20incomplete%22.%20We%20had%20to%20remove%20all%20UI%20references%20and%20page%20links%20to%20the%20library%2C%26nbsp%3Bas%20a%20measure%20to%20prevent%20the%20testers%20from%20seeing%20the%20offending%20link.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhy%20does%20this%20link%20appear%20here%2C%20and%20what%20can%20we%20do%20to%26nbsp%3Bremove%20it%3F%20We%20are%20using%20classic%20Declarative%20XML%20(elements.xml)%20to%20define%20the%20library%20instance%20(ListInstance)%2C%20provisioning%20it%20within%20the%20App%20Web.%20We%26nbsp%3Bdid%20not%20write%20our%20own%20template%2C%20and%20the%20ListInstance%20schema%20doesn't%20seem%20to%20provide%20access%20to%20any%20properties%20that%20would%20show%2Fhide%20the%20Modern%20Experience.%20We%20do%20not%20define%20the%20list%20view%20pages%20ourselves%2C%20and%20so%20we%20do%20not%20seem%20to%20have%20the%20abilty%20to%20serve%20CSS%20to%20simply%20hide%20the%20link.%20And%20App%20Web%20means%20we%20do%20not%20have%20access%20to%20a%20List%20Settings%20or%20Site%20Settings%20page.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Senior Member

Hello,

 

Our add-in/app includes a document library instance used for storing customisable image assets. A few months ago the "Exit classic experience" link started appearing at the top of the list view pages, however the link does nothing. I thought it was a glitch that would go away, however it persists even in newly-installed copies of our add-in, and a recent bug-fix we submitted to Microsoft just got rejected because the link made the add-in "look incomplete". We had to remove all UI references and page links to the library, as a measure to prevent the testers from seeing the offending link.

 

Why does this link appear here, and what can we do to remove it? We are using classic Declarative XML (elements.xml) to define the library instance (ListInstance), provisioning it within the App Web. We did not write our own template, and the ListInstance schema doesn't seem to provide access to any properties that would show/hide the Modern Experience. We do not define the list view pages ourselves, and so we do not seem to have the abilty to serve CSS to simply hide the link. And App Web means we do not have access to a List Settings or Site Settings page.

0 Replies