Home

UPDATE: Support for Structured/Managed Navigation enabled on Modern Pages in Classic Team Sites

%3CLINGO-SUB%20id%3D%22lingo-sub-57384%22%20slang%3D%22en-US%22%3EUPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-57384%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20everyone!%20Thank%20you%20for%20the%20feedback%20around%20wanting%20to%20move%20to%20the%20%E2%80%9Cmodern%E2%80%9D%20team%20site%20experiences%2C%20and%20needing%20support%20for%20structured%2Fmanaged%20navigation.%20We%E2%80%99re%20pleased%20to%20announce%20that%20we%20have%20addressed%20this%20issue%20and%20will%20be%20rolling%20out%20the%20fix%20to%20the%20worldwide%20production%20environment%20in%20the%20coming%20days.%20%3CU%3EThank%20you%20for%20your%20patience%3C%2FU%3E%20%E2%80%93%20and%20to%20the%20community%20for%20helping%20us%20identify%20some%20issues%20during%20the%20initial%20First%20Release%20preview!%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWith%20this%20update%20if%20you%20have%20enabled%20publishing%20on%20a%20classic%20team%20site%2C%20your%20structured%20or%20managed%20navigation%20will%20now%20render%20correctly%20in%20the%20modern%20experience%20(both%20global%20and%20current%20navigation)%2C%20including%20any%20scoped%20or%20audience-targeted%20links.%20We%20haven%E2%80%99t%20pulled%20all%20the%20classic%20settings%20into%20the%20modern%20panels%20yet%2C%20so%20when%20you%20need%20to%20edit%20the%20navigation%20elements%2C%20the%20edit%20link%20will%20direct%20you%20to%20the%20classic%20settings%20page.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ENavigation%20settings%20on%20a%20classic%20team%20site%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%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%2F12464i38EF8C87015FA2F8%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22areanavigationsettings.png%22%20title%3D%22areanavigationsettings.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ENow%20render%20correctly%20on%20a%20modern%20page%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20803px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F12465iB2EE6EB0A745CA38%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22managednav-global.png%22%20title%3D%22managednav-global.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAdditionally%2C%20subsites%20will%20correctly%20inherit%20from%20the%20parent%20web%20when%20structural%20navigation%20is%20used.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EParent%20site%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20697px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F12466iD3EDDC3D2292157A%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22structurednav-global.png%22%20title%3D%22structurednav-global.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ESubsite%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20701px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F12467iE86326F62E332599%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22structurednav-subsiteinherit.png%22%20title%3D%22structurednav-subsiteinherit.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%20hope%20this%20unblocks%20you%20as%20you%20move%20to%20the%20modern%20user%20experience%20(UX).%20Try%20it%20out%2C%20and%20let%20us%20know%20if%20you%20have%20any%20questions.%20Thanks%2C%20Sean!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-57384%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ESharePoint%20Online%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-266455%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-266455%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Robyn...%20could%20you%20send%20me%20more%20details%3F%26nbsp%3B%20Screenshots%20of%20what%20you%20are%20seeing%20vs.%20what%20you%20see%20on%20the%20web%20would%20be%20great.%26nbsp%3B%20I'll%20message%20you%20my%20email.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-266425%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-266425%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20doesn't%20render%20in%20the%20SharePoint%20App.%20It%20works%20in%20the%20browser%20on%20my%20mobile%20device%2C%20but%20not%20in%20the%20SharePoint%20App%20in%20my%20mobile%20device.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWill%20this%20be%20fixed%2C%20as%20what%20is%20designed%20to%20be%20a%20navigational%20hierarchy%20just%20comes%20across%20as%20a%20long%20list%20when%20using%20the%20App.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%2C%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-217566%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-217566%22%20slang%3D%22en-US%22%3E%3CP%3EPlease%20support%20global%20navigation%20on%20Modern%20Sites%20(not%20just%20modern%26nbsp%3Bexperiences).%26nbsp%3B%20Lack%20of%20global%20navigation%20option%20on%20Communication%20Sites%20and%20other%20modern%20site%20templates%26nbsp%3Bis%20just%20bad%20form.%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20don't%20care%20if%20it%20uses%20a%20new%20interface%20or%20if%20it%20uses%20the%20Term%20Store%2C%20just%20get%20it%20done.%26nbsp%3B%20MS%20should%20just%20buy%20out%20one%20of%20the%203rd%20party%20tools%20like%20it%20usually%20does%20if%20it%20can't%20hire%20proficient%20developers.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-216253%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-216253%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhen%20we%20are%20using%20Modern%20page%2C%20Global%20navigation%20still%20does%20not%20show%20the%20Root%20site.%3C%2FP%3E%3CP%3EFix%20for%20this%20is%20rolled%20out%3F%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20yes%2C%20what%20are%20the%20settings%20that%20needs%20to%20be%20selected%20to%20get%20it%20working.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-201673%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-201673%22%20slang%3D%22en-US%22%3E%3CP%3EYes%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F119118%22%20target%3D%22_blank%22%3E%40Peter-Ross%20Cuthbert%3C%2FA%3E.%20This%20is%20wanting.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20problem%20of%20classic%20navigation%20headers%20in%20modern%20was%20fixed%20when%20I%20raised%20this.%20Ref%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FSharePoint%2FUPDATE-Support-for-Structured-Managed-Navigation-enabled-on%2Fm-p%2F73400%2Fhighlight%2Ftrue%23M6957%26nbsp%3B%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FSharePoint%2FUPDATE-Support-for-Structured-Managed-Navigation-enabled-on%2Fm-p%2F73400%2Fhighlight%2Ftrue%23M6957%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHowever%2C%20the%20modern%20experience%20just%20doesn't%20allow%20headers%20at%20all.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-201668%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-201668%22%20slang%3D%22en-US%22%3E%3CP%3ESorry%20should%20have%20specified%2C%20my%20previous%20message%20is%20only%20in%20relation%20to%20the%20modern%20experience%20pages%20and%20sites%20made%20with%20the%20new%20Team%2FCommunication%2FHub%20template%20that%20don't%20support%20SharePoint%20Server%20Publishing%20features%20and%20thus%20no%20managed%20navigation.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20these%20new%20sites%2C%20you%20only%20have%20access%20to%20%22Edit%20Links%22%20and%20it%20does%20not%20allow%20you%20to%20leave%20an%20item%20without%20a%20link.%20Inputting%20something%20like%20%22%23%22%20just%20causes%20it%20to%20default%20to%20the%20root%20site%20collection.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EA%20way%20to%20add%20a%20%22Header%22%20item%20through%20the%20modern%20experience%20%22Edit%20Links%22%20needs%20to%20be%20added.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-201666%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-201666%22%20slang%3D%22en-US%22%3EIt%20still%20works%20if%20you%20are%20using%20classic%20team%20sites.%20When%20managing%20the%20navigation%20(Site%20Settings%20%26gt%3B%20Navigation)%20for%20a%20parent%20item%20use%20%22add%20header%22%20(the%20file%20icon)%2C%20give%20it%20a%20name%20no%20link%20needed.%20For%20the%20child%20item%20then%20use%20%22add%20link%22%20and%20make%20sure%20these%20are%20indented%20under%20the%20header.%3CBR%20%2F%3EThe%20good%20thing%20about%20parent%20items%20with%20no%20links%20is%20that%20the%20whole%20menu%20expands%20if%20you%20select%20it.%20This%20does%20not%20happen%20when%20the%20item%20has%20a%20link%20attached%20to%20it%2C%20you%20have%20to%20select%20the%20arrow%20next%20to%20it%20for%20that%20to%20happen.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-201660%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-201660%22%20slang%3D%22en-US%22%3EA%20little%20late%20to%20the%20conversation%20here%2C%20but%20I%20was%20just%20wondering%20if%20any%20updates%20have%20been%20released%20on%20being%20able%20to%20set%20an%20item%20in%20left%20nav%20to%20be%20without%20a%20link%3F%20This%20is%20specifically%20for%20instances%20where%20you%20have%20a%20parent%20item%20that%20is%20purely%20descriptive%20and%20shouldn't%20link%20to%20anything%2C%20almost%20like%20a%20grouping%20and%20would%20only%20apply%20to%20first%20level%20items.%20Any%20feedback%20would%20be%20appreciated%20%3A)%3C%2Fimg%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-176044%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-176044%22%20slang%3D%22en-US%22%3E%3CP%3EJust%20wondering%20if%20you%20got%20any%20replies%20or%20fixes%20for%20this%20issue.%26nbsp%3B%20I'm%20having%20the%20same%20problem%20in%20my%20site%20collection%20and%20enabling%20publishing%20isn't%20fixing%20it.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-140530%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-140530%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%2F104527%22%20target%3D%22_blank%22%3E%40Beilul%20Brhane%3C%2FA%3E%20-%20not%20completely%20at%20this%20time%20(though%20I've%20heard%20of%20folks%20manipulating%20the%20page%20client-side%20after%20load).%20You%20can%20disable%20the%20quick%20launch%20in%20navigation%20elements%20setting%20(_layouts%2F15%2Fnavoptions.aspx)%20-%20but%20we%20still%20render%20the%20recycle%20bin%20outside%20of%20this%20setting%20so%20it%20will%20still%20display.%20We%20are%20looking%20to%20modify%20this%2C%20but%20no%20ETA%20at%20this%20time.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-139529%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-139529%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%2F5937%22%20target%3D%22_blank%22%3E%40Sean%20Squires%3C%2FA%3E%26nbsp%3Bis%20there%20any%20way%20were%20one%20can%20only%20remove%20the%20left%20navigation%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-139528%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-139528%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%2F5937%22%20target%3D%22_blank%22%3E%40Sean%20Squires%3C%2FA%3E%2C%20Is%20there%20a%20way%20can%20remove%20the%20left%20navigation%20in%20the%20modern%20experience%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-138552%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-138552%22%20slang%3D%22en-US%22%3EYes%2C%20I%20realized%20that%2C%20too...thanks%20for%20the%20feedback.%20By%20default%20right%20now%2C%20but%20we'll%20see%20if%20we%20can%20provide%20focus%20on%20selected%20items%20when%20navigating%20w%2Fin%20the%20site.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-136297%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-136297%22%20slang%3D%22en-US%22%3EGreat%20to%20see%20the%20quick%20launch%20collapsed%20by%20default!%3CBR%20%2F%3EHowever...%3CBR%20%2F%3EWhen%20I%20follow%20a%20link%2C%20say%20from%20a%20hero%20web%20part%20on%20the%20homepage%2C%20the%20page%20loads%20but%20the%20navigation%20does%20not%20change%20-%20it%20stays%20collapsed.%20Hence%20I%20am%20not%20clear%20where%20the%20page%20is%20located%20and%20what%20else%20it%20might%20refer%20to.%20Is%20this%20a%20bug%20or%20by%20default%3F%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-136008%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-136008%22%20slang%3D%22en-US%22%3EOMG.%20I%20logged%20in%20today%20and%20%3CTHIS%20might%3D%22%22%20be%3D%22%22%20the%3D%22%22%20proudes%3D%22%22%20moment%3D%22%22%20in%3D%22%22%20my%3D%22%22%20sharepoint%3D%22%22%20career%3D%22%22%3E%20It%20-was%20-%20fixed.%20I%20have%20never%20had%20this%20impact%20on%20SharePoint%20Before.%20I'm%20gonna%20call%20my%20mom.%3C%2FTHIS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-135479%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-135479%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%2F56928%22%20target%3D%22_blank%22%3E%40Pia%20Langenkrans%3C%2FA%3E%20%2F%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F2521%22%20target%3D%22_blank%22%3E%40Philine%20von%20Guretzky%3C%2FA%3E%20-%20thanks%20for%20the%20feedback.%20Yes%2C%20we're%20looking%20to%20amend%20the%20navigation%20to%20be%20default%20collapsed%20(and%20consistent%20w%2F%20the%20documents%20and%20pages%20libraries).%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-135375%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-135375%22%20slang%3D%22en-US%22%3Eha%2C%20and%20I%20thought%20you%20had%20some%20other%20trick%20up%20your%20sleeve%20%3A)%3C%2Fimg%3E%20Thanks%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-135372%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-135372%22%20slang%3D%22en-US%22%3E%3CP%3EIt's%20managed%20meta%20data%2C%20baby!%20What%20can't%20we%20do%20with%20that%3F%20Up%20to%20seven%20levels%2C%20allthough%20I%20think%20you%20are%20having%20issues%20if%20you%20need%20that%20many...%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-135338%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-135338%22%20slang%3D%22en-US%22%3E%3CP%3EWasn't%20aware%20you%20can%20have%20so%20many%20subcategories%2C%20how%20did%20you%20achieve%20that%3F%20I%20am%20only%20able%20to%20get%20one%20subcategory.%3CBR%20%2F%3E%3CBR%20%2F%3EAnd%20yes%20fully%20agree%2C%20as%20have%20many%20others%20here%2C%20default%20setting%20should%20be%20collapsed%20or%20it's%20state%20manageable.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-135289%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-135289%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%0A%3CP%3EI've%20reached%20the%20structure%20of%20my%20solution%20where%20I%20created%20a%20Classic%20team%20site%2C%20added%20publishing%20features%20and%20added%20metadata%20navigation%20on%20my%20left%20nav.%20Problem%20is%20that%20it's%20expanded%20by%20default.%20It's%20not%20so%20user%20friendly%20and%20now%20we%20only%20have%20about%2020%20pages%20but%20once%20the%20application%20is%20done%20it%20will%20be%20hundreds.The%20default%20setting%20should%20be%20collapsed.%3C%2FP%3E%0A%3CP%3EAnd%20trimming%20it%20down%20is%20no%20use%2C%20it's%20for%20a%20Customer%20in%20the%20public%20sector.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-135198%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-135198%22%20slang%3D%22en-US%22%3E%3CP%3ESuper%20helpful%20Roland%2C%20thanks.%26nbsp%3B%20I'm%20running%20this%20down%20with%20my%20team%20now.%26nbsp%3B%20Hoping%20to%20circle%20back%20after%20the%20new%20year%20at%20the%20latest).%20%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks!%3CBR%20%2F%3ENate%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-135148%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-135148%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F11843%22%20target%3D%22_blank%22%3E%40Nate%20Clinton%3C%2FA%3E%26nbsp%3Bsure%2C%20I%20have%20attached%20desktop%20versus%20SharePoint%20App.%20Neither%20the%20Quick%20Launch%26nbsp%3Bnor%20Top%20Bar%20show%20up.%20%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%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%2F25274iCB001D6A26487267%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22HP_Desktop.png%22%20title%3D%22HP_Desktop.png%22%20%2F%3E%3C%2FSPAN%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20562px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F25275i45753DA838B5FA73%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22HP_IOS.PNG%22%20title%3D%22HP_IOS.PNG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-135108%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-135108%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Roland...%20would%20you%20be%20able%20to%20provide%20a%20screenshot%20of%20what%20you%20are%20seeing%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks%3C%2FP%3E%0A%3CP%3ENate%20(from%20the%20SP%20Mobile%20team)%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-135027%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-135027%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20migrating%20a%20business%20unit%20to%20iPads%20and%20we%20need%20to%20step%20up%20our%20mobile%20game.%20Using%20the%20SharePoint%20App%2C%20I%20am%20only%20seeing%20the%20menu%20%22hamburger%22%20on%20Group-connected%20sites.%20For%20our%20classic%20sites%2C%20where%20we%20have%20implemented%20modern%20site%20pages%20to%20be%20mobile-friendly%2C%20we%20are%20not%20getting%20any%20menus%20showing%20on%20the%20device%2C%20making%20navigation%20non-existent.%20This%20is%20a%20particular%20issue%20with%20our%20Intranet%20Home%20Site%20which%20is%20a%20classic%20Publishing%20Infrastructure%20enabled%20site%20with%20the%20drop%20down%20menus.%3C%2FP%3E%0A%3CP%3EHow%20do%20I%20get%20menus%20to%20show%20up%20using%20the%20SharePoint%20App%20for%20these%20type%20of%20sites%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-115066%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-115066%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3EToday%20the%20top%20link%20bar%20(global%20navigation)%20is%20gone%20on%20modern%20experience%20page.%3C%2FP%3E%3CP%3EWe%20have%20a%20site%20collection%20with%26nbsp%3Ba%20lot%20of%20classic%20team%20sites.%20Publishing%20feature%20activated%20on%20this%20site%20collection%2C%20and%20a%20few%20subsites.%3C%2FP%3E%3CP%3ESome%20sites%20use%20classic%20page%2C%20and%20some%20sites%20use%20modern%20page%20-%26gt%3B%20with%20this%20one%2C%20the%20top%20link%20bar%20is%20gone.%3C%2FP%3E%3CP%3EI'm%20not%20the%20only%20one%20%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FSharePoint%2FAnybody-else-s-top-link-bar-in-Modern-experience-disappear%2Fm-p%2F114750%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FSharePoint%2FAnybody-else-s-top-link-bar-in-Modern-experience-disappear%2Fm-p%2F114750%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThere%20is%20a%20regression%20with%20the%20last%20update%20%3F%3C%2FP%3E%3CP%3EThanks%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-109428%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-109428%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F5937%22%20target%3D%22_blank%22%3E%40Sean%20Squires%3C%2FA%3E%2C%20The%20problem%20I'm%20having%20sounds%20similar%2C%20but%20not%20quite%20the%20same%20as%20anyone%20here.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20using%20Managed%20Metadata%20navigation.%20On%20%3CU%3Eclassic%3C%2FU%3E%20pages%2C%20both%20the%20level-1%20and%20level-2%20terms%20are%20working%20fine%3A%3C%2FP%3E%3CP%3ELevel-1%20term%3A%20%3CA%20href%3D%22http%3A%2F%2Fsiteurl.com%2FdocLibrary%26nbsp%3B%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fsiteurl.com%2FdocLibrary%26nbsp%3B%3C%2FA%3E%20(correct)%3C%2FP%3E%3CP%3ELevel-2%20term%3A%20%3CA%20href%3D%22http%3A%2F%2Fsiteurl.com%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fsiteurl.com%2F%3C%2FA%3E%3CU%3E%3CSTRONG%3EdocLibrary%2Fcategory1%3C%2FSTRONG%3E%3C%2FU%3E%26nbsp%3B%20(correct)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOn%20modern%20pages%2C%20my%20level-1%20term%20continues%20to%20work%20fine%2C%20but%20my%20level-2%20term%20become%20corrupt%20and%20duplicate%20the%20level-2%20term%20in%20place%20of%20the%20level-1%20term%2C%20which%20breaks%20the%20URL%20and%20results%20in%20a%20404%20page%20not%20found%20error%3A%3C%2FP%3E%3CP%3ELevel-1%20term%3A%20%3CA%20href%3D%22http%3A%2F%2Fsiteurl.com%2FdocLibrary%26nbsp%3B%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fsiteurl.com%2FdocLibrary%26nbsp%3B%3C%2FA%3E%20(correct)%3C%2FP%3E%3CP%3ELevel-2%20term%3A%20%3CA%20href%3D%22http%3A%2F%2Fsiteurl.com%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fsiteurl.com%2F%3C%2FA%3E%3CU%3E%3CSTRONG%3Ecategory1%3C%2FSTRONG%3E%2F%3C%2FU%3E%3CSTRONG%3E%3CU%3Ecategory1%3C%2FU%3E%26nbsp%3B%3C%2FSTRONG%3E%20(incorrect%20-%20404%20page%20not%20found)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%2C%20for%20reasons%20I%20can't%20explain%2C%20my%20level-1%20term%20is%20dropped%20and%20the%20Level-2%20term%20is%20duplicated%20on%20the%20Modern%20pages%2C%20but%20works%20fine%20on%20the%20classic%20pages.%20The%20fact%20that%20it%20works%20fine%20on%20classic%20pages%20but%20not%20on%20modern%20pages%20propted%20me%20to%20post%20it%20on%20this%20forum.%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-106330%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-106330%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F5937%22%20target%3D%22_blank%22%3E%40Sean%20Squires%3C%2FA%3E%2C%20I%20just%20noticed%20this%20discussion.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAre%20there%20any%20plans%20to%20make%20Managed%20Navigation%20work%20across%20multiple%20site%20collections%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-106326%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-106326%22%20slang%3D%22en-US%22%3E%3CP%3EWhat%20is%20planned%20for%20intelligent%2Fnot%20manual%20site%20navigation%20for%20modern%20pages%3F%20This%20doesn't%20feel%20very%20modern.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-101574%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-101574%22%20slang%3D%22en-US%22%3E%2B100%20for%20Left%20nav%20desperately%20need%20to%20have%20%22Collapsed%22%20as%20default%20option.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-101222%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-101222%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F5937%22%20target%3D%22_blank%22%3E%40Sean%20Squires%3C%2FA%3E%26nbsp%3BReally%20like%20the%20push%20for%20the%20modern%20and%20especially%20a%20Responsive%20experience%2C%20as%20that%20is%20absolutely%20essential%20in%20pushing%20SharePoint%20to%20a%20client%20now%20adays%2C%20the%20first%20thing%20a%20client%20asks%20is%20%22is%20it%20responsive%3F%22.%20So%20far%2C%20huge%20leaps%20have%20been%20made%20and%20its%20looking%20good!%3CBR%20%2F%3EBig%20issue%20however%20is%20the%20Top%20nav%20not%20being%20included.%26nbsp%3BAny%20idea%20on%20when%20we%20can%20expect%20to%20have%20the%20Top%20Navigation%20into%20the%20mobile%20experience%3F%20As%20previously%20mentioned%20it%20dissepears%20when%20the%20screen%20is%20640px%20or%20something%20like%20that.%3CBR%20%2F%3EAs%20of%20right%20now%2C%20its%20hard%20to%20recomend%20the%20client%20a%20navigation%20option%20that%20includ%20the%20Top%20nav%20at%20all%2C%20as%20we%20do%20not%20really%20know%20when%20it%20will%20be%20possible%20to%20use%20it%20in%20the%20mobile%20view.%20If%20we%20use%20the%20top%20nav%2C%20%26nbsp%3Bthe%20user%20cant%20navigate%20properly%20using%20the%20phone.%3CBR%20%2F%3E%3CBR%20%2F%3EThis%20leads%20us%20to%20use%20the%20Quick%20Luanch%20navigation%20entierely.%20But%20that%20hits%20on%20another%20problem.%20The%20navigation%20is%20not%20collapsed%20as%20default.%20This%20means%20that%20without%20a%20top%20navigation%20the%20left%20navigation%20becomes%20extreamly%20cluttered%20and%20large%2C%20and%20is%20expanded%20by%20default.%3CBR%20%2F%3E%3CBR%20%2F%3E3%20things%3A%3CBR%20%2F%3E1.%20Top%20nav%20need%20to%20be%20shown%20in%20the%20mobile%20experience%2C%20is%20this%20still%20the%20plan%3F%20And%20if%20so%20whats%20the%20ETA%3F%3C%2FP%3E%3CP%3E2.%20Left%20nav%20desperately%20need%20to%20have%20%22Collapsed%22%20as%20default%20option.%3C%2FP%3E%3CP%3E3.%20Aditionally%2C%20on%20nother%20note%2C%20the%26nbsp%3B%3CSPAN%3Ems-siteLogo-defaultLogo%20link%20needs%20to%20have%20the%20option%20to%20allways%20link%20to%20the%20top%20site%20collection%20landing%20page.%20Without%20the%20ability%26nbsp%3Bto%20inject%20JS%20this%20needs%20to%20be%20an%20option%2C%20as%20that%20is%20one%20of%20the%20main%20things%20i%20allways%20get%20requested%20to%20fix%20for%20our%20clients%20as%20developer.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CBR%20%2F%3ERegards%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-100417%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-100417%22%20slang%3D%22en-US%22%3EOf%20course%20-%20and%20yes%2C%20missed%20your%20note%20that%20you%20were%20looking%20to%20edit%20horizontal.%20In%20modern%20team%20we're%20moving%20to%20a%20left%2C%20vertical%20nav%20only%20-%20but%20will%20materialize%20the%20classic%20horizontal%20nav%20if%20you%20have%20subsites.%20You%20can%2C%20of%20course%2C%20continue%20to%20edit%20the%20toplink%20nav%20bar%20directly%2C%20but%20only%20through%20classic%20settings%2Fpage.%20Thanks.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-100341%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-100341%22%20slang%3D%22en-US%22%3E%3CP%3E%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F5937%22%20target%3D%22_blank%22%3E%40Sean%20Squires%3C%2FA%3E%2C%20thank%20you%20for%20the%20link.%20This%20bullet%20point%20addressed%20my%20concern%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CEM%3E%22In%20SharePoint%20Online%2C%20you%20can%20only%20customize%20the%20left-hand%20menu%20on%20a%20team%20site%20at%20this%20time%20unless%20you%20are%20in%20classic%20mode.%22%3C%2FEM%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-98416%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-98416%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%2F41150%22%20target%3D%22_blank%22%3E%40Peter%20Mcdermott%3C%2FA%3E%20-%20if%20you%20have%20sufficient%20permissions%20you%20should%20see%20an%20inline%20edit%20button%20that%20allows%20you%20to%20add%2C%20move%2C%20and%20group%20navigation%20links.%20From%20the%20pages%20library%20there's%20also%20an%20option%20in%20the%20context%20menu%20to%20add%20to%20the%20navigation.%20Take%20a%20look%20at%20this%20article%20for%20more%20details%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fsupport.office.com%2Fen-us%2Farticle%2FCustomize-the-navigation-on-your-SharePoint-site-3cd61ae7-a9ed-4e1e-bf6d-4655f0bf25ca%3Fui%3Den-US%26amp%3Brs%3Den-US%26amp%3Bad%3DUS%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.office.com%2Fen-us%2Farticle%2FCustomize-the-navigation-on-your-SharePoint-site-3cd61ae7-a9ed-4e1e-bf6d-4655f0bf25ca%3Fui%3Den-US%26amp%3Brs%3Den-US%26amp%3Bad%3DUS%3C%2FA%3E%20(let%20us%20know%20if%20you%20have%20other%20questions).%20Thanks!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-98414%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-98414%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%2F48415%22%20target%3D%22_blank%22%3E%40Adrienne%20Kidd%3C%2FA%3E%20-%20terribly%20sorry%20to%20have%20gone%20dark%20on%20you.%20I%20was%20out%20of%20town%20and%20thought%20an%20update%20was%20shared.%20The%20regression%20took%20a%20bit%20longer%20to%20isolate%20and%20fix%2C%20but%20I'm%20happy%20to%20report%20that%20a%20fix%20is%20in%20and%20should%20be%20rolling%20out%20this%20week%20(fully%20in%20by%20end%20of%20week).%20I'm%20looking%20into%20a%20related%20issue%20w%2F%20the%20browser%20status%20reporting%20the%20URL%20of%20the%20node%20w%2F%20focus%2C%20but%20the%20L2%20and%20L3%20links%20are%20correctly%20rendering.%20Thanks%20for%20your%20patience!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-93438%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-93438%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F5937%22%20target%3D%22_blank%22%3E%40Sean%20Squires%3C%2FA%3E%26nbsp%3B-%20I%20reallllly%20need%20an%20update%20on%20this.%26nbsp%3B%20Thanks.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-92516%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-92516%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%2F5937%22%20target%3D%22_blank%22%3E%40Sean%20Squires%3C%2FA%3E%26nbsp%3B-%20Any%20update%20yet%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-91009%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-91009%22%20slang%3D%22en-US%22%3E%3CP%3EHello!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EA%20little%20late%20to%20the%20party%20here%2C%20but%20trying%20to%20solve%20for%20navigation%20on%20a%20new%20Modern%20site.%20In%20the%20Classic%20sites%20it%20was%20very%20easy%20and%20straight-forward%20to%20create%20a%20horizontal%20navigation%20bar.%20This%20allowed%20users%20to%20select%20from%20over%2050%20wiki%20pages%20in%20a%20very%20organized%20fashion.%20However%2C%20unless%20I'm%20missing%20something%2C%20I%20can't%20determine%20how%20to%20create%20a%20horizontal%20navigation%20bar%20in%20the%20modern%20pages%26nbsp%3Benvironment%20without%20having%20to%20go%20through%20the%20Navigation%20menu%20in%20Site%20Settings.%20Is%20there%20not%20an%20easy%20%22Edit%20Links%22%20button%20that%20someone%20could%20use%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-90360%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-90360%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F48415%22%20target%3D%22_blank%22%3E%40Adrienne%20Kidd%3C%2FA%3E%20-%20very%20sorry%20about%20this%3B%20we%20validated%20this%20very%20scenario%20when%20we%20rolled%20the%20fix%20out%20earlier%20this%20month%20-%20but%20I'm%20now%20able%20to%20repro%2C%20too.%20I%20have%20an%20engineer%20investigating.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-89918%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-89918%22%20slang%3D%22en-US%22%3EI%20can%20confirm%2C%20that%20the%20second%20level%20does%20not%20work%20when%20there%20is%20a%20third.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-89896%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-89896%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F5937%22%20target%3D%22_blank%22%3E%40Sean%20Squires%3C%2FA%3E%26nbsp%3BThis%20is%20still%20not%20working.%26nbsp%3B%20When%20there%20is%20a%20third%20level%2C%20the%20second%20level%20stops%20working.%26nbsp%3B%20This%20is%20the%20only%20thing%20stopping%20us%20from%20moving%20to%20the%20new%20library%20experience%2C%20which%20we%20are%20desperate%20to%20do.%26nbsp%3B%26nbsp%3B%20Please%20can%20you%20help%3F%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-89886%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-89886%22%20slang%3D%22en-US%22%3E%3CP%3EWhat%20on%20earth%20is%20going%20on%3F%26nbsp%3B%20Our%20navigation%20is%20still%20all%20messed%20up.%26nbsp%3B%20When%20there%20is%20a%20third%20level%20flyout%2C%20it%20stops%20the%20second%20level%20fly-out%20from%20working.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20urgently%20need%20to%20upgrade%20to%20the%20modern%20library%20experience%2C%20and%20have%20been%20wanting%20to%20all%20year%2C%20but%20this%20failure%20to%20render%20the%20navigation%20is%20stopping%20us%20from%20doing%20so.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPlease%20can%20you%20provide%20an%20update%3F%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-86025%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-86025%22%20slang%3D%22en-US%22%3Edoes%20not%20work%20at%20my%20tenant%20yet%2C%20hoping%20it%20does%20soon%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-86024%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-86024%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F5937%22%20target%3D%22_blank%22%3E%40Sean%20Squires%3C%2FA%3E3rd%20level%20links%20now%20seem%20to%20work.%20Great%20news%2C%20thanks!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CBR%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-left%22%20style%3D%22width%3A%20203px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F17015i51B09F446A97B8AA%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20alt%3D%22Menu1.PNG%22%20title%3D%22Menu1.PNG%22%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-caption%22%20onclick%3D%22event.preventDefault()%3B%22%3EPage%3C%2FSPAN%3E%3C%2FSPAN%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-left%22%20style%3D%22width%3A%20194px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F17016iF10602F981266A7A%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20alt%3D%22Menu2.PNG%22%20title%3D%22Menu2.PNG%22%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-caption%22%20onclick%3D%22event.preventDefault()%3B%22%3ELibrary%3C%2FSPAN%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%3E%26nbsp%3B%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%3EJust%20flagging%20this%20again%2C%20the%20menu%20does%20however%20look%20different%20within%20the%20same%20site%20collection.%20On%20a%20page%20all%20menu%20items%20are%20fully%20visible%2C%20as%20soon%20as%20I%20am%20in%20a%20list%2Flibrary%20the%20menu%20items%20are%20cut%20off.%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-83765%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-83765%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F11696%22%20target%3D%22_blank%22%3E%40Glenn%20Goldberg%3C%2FA%3E%2C%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F32866%22%20target%3D%22_blank%22%3E%40Denis%20Tiri%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F645%22%20target%3D%22_blank%22%3E%40Scott%20Joyner%3C%2FA%3E%2C%20-%26nbsp%3BSorry%20I%20missed%20these%20comment%20last%20week%20-%20yes%2C%20we%20learned%20there%20was%20a%20regression%20that%20broke%20the%20rendering%20of%20the%20L3%20URL.%20A%20fix%20has%20already%20been%20patched%20and%20should%20be%20rolling%20to%20PROD.%20Apologies%20-%20thanks%20for%20your%20patience!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-83762%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-83762%22%20slang%3D%22en-US%22%3ESorry%20I%20missed%20this%20comment%20last%20week%20-%20yes%2C%20we%20learned%20there%20was%20a%20regression%20that%20broke%20the%20rendering%20of%20the%20L3%20URL.%20A%20fix%20has%20already%20been%20patched%20and%20should%20be%20rolling%20to%20PROD.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-83542%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-83542%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F2521%22%20target%3D%22_blank%22%3E%40Philine%20von%20Guretzky%3C%2FA%3E%2C%20I%20agree%20completely%20--%20menu%20item%20truncation%20and%20and%20the%20considerably%20slower%20interaction%20time%20with%20the%20dropdowns%20and%20flyouts%20make%20the%20current%20Managed%20navigation%20experience%20in%20Modern%20mode%20considerably%20less%20useful%20and%20pleasant%20than%20in%20Classic%20mode.%20If%20we%20can%20regain%20the%20ability%20to%20utilize%20CSS%20to%20customize%20the%20appearance%20of%20the%20dropdowns%2Fflyouts%2C%20we%20would%2C%20of%20course%2C%20have%20control%20over%20this.%20Short%20of%20that%2C%20at%20least%20eliminating%20truncation%20would%20be%20preferable.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOne%20of%20the%20main%20reasons%20to%20go%20to%20Managed%20navigation%20in%20large%20sites%20is%20the%20lightning%20fast%20display%20and%20interaction%20with%20the%20menus%20in%20the%20Global%20navigation.%20Since%20links%20to%20third%20levels%20don't%20yet%20work%2C%20I'm%20sure%20this%20is%20a%20work%20in%20progress.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-83523%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-83523%22%20slang%3D%22en-US%22%3E%3CP%3EPlease%20don't%20tructuate%20menu%20items!%3C%2FP%3E%3CP%3EI%20know%20Microsoft%20are%20a%20huge%20fan%20of%20the%20...%20but%20in%20a%20menu%20this%20really%20should%20not%20happen.%3C%2FP%3E%3CP%3EI%20currently%20see%20both%20options%2C%20so%20no%20trunctuation%20does%20seem%20possible!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWould%20it%20be%20possible%20to%20have%20the%20submenus%20fly%20out%20a%20little%20snappier%3F%3C%2FP%3E%3CP%3EI%20always%20see%20users%20click%20the%20headers%20since%26nbsp%3Bthe%20menus%26nbsp%3Bjust%20take%20that%20bit%20too%20long%20to%20appear.%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-left%22%20style%3D%22width%3A%20200px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F16625i1DC065B50D814914%2Fimage-size%2Fsmall%3Fv%3D1.0%26amp%3Bpx%3D200%22%20alt%3D%22menu4.PNG%22%20title%3D%22menu4.PNG%22%20%2F%3E%3C%2FSPAN%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-left%22%20style%3D%22width%3A%20200px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F16626i80976329D133D8DD%2Fimage-size%2Fsmall%3Fv%3D1.0%26amp%3Bpx%3D200%22%20alt%3D%22menu5.PNG%22%20title%3D%22menu5.PNG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-81596%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-81596%22%20slang%3D%22en-US%22%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESame%20here%2C%20in%20IE%20Level%203%20just%20takes%20us%20to%20Level%202%3C%2FP%3E%3CP%3Ein%20other%20browsers%20Level%203%20items%20are%20not%20clickable.%20there%20is%20no%20link%20underneath%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-80934%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-80934%22%20slang%3D%22en-US%22%3ESad%20to%20report%20we%20have%20the%20same%20experience.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-80898%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-80898%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20having%20a%20simlar%20issue.%26nbsp%3B%20Submenus%20are%20always%20directing%20users%20to%20the%20URL%20of%20the%20site%20above.%26nbsp%3B%20For%20example%20using%20the%20new%20Managed%20Metadata%20option%20with%20the%20menu%2C%20we%20may%20have%20Dept...HR...Benefits%2C%20but%20it%20take%20to%20the%20HR%20link%20for%20this%20and%20all%20other%20submenu%20items.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-80246%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-80246%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20grandchild%20links%20seem%20to%20show%20up%2C%20but%20when%20we%20try%20to%20use%20them%2C%20we%20are%20just%20taken%20to%20the%20'child'%20site.%26nbsp%3B%20We%20seem%20to%20have%20halfway%20there!%26nbsp%3B%20We%20desperately%20want%20to%20upgrade%20to%20the%20New%20Experience%20lists%20and%20libraries%2C%20but%20this%20navigation%20issue%20is%20SERIOUSLY%20holding%20us%20back.%26nbsp%3B%20Help!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-78601%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-78601%22%20slang%3D%22en-US%22%3EHi%20Adrienne%20-%20you%20beat%20my%20announcement!%20The%20fix%20to%20support%20L3%20links%20in%20managed%20nav%20horizontal%20orientation%20had%20to%20be%20made%20in%20two%20different%20code%20bases.%20It%20might%20have%20still%20been%20rolling%20through.%20I'll%20check%20a%20test%20tenant%2C%20but%20let%20me%20know%20if%20you%20don't%20see%20it%20next%20week.%20Thanks!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-77371%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-77371%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Sean%20-%20It%20appears%20that%20our%20'grandchild'%20links%20are%20rendering%20when%20in%20the%20view%20of%20the%20library%2C%20but%20NOT%20in%20the%20modern%20page.%26nbsp%3B%20When%20can%20we%20expect%20this%20functionality%20to%20appear%20consistently%20throughout%20the%20system%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-73400%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-73400%22%20slang%3D%22en-US%22%3EAbhimanyu%20-%20thanks%20for%20bump%20-%20yes%2C%20the%20controls%20team%20is%20looking%20at%20options%20to%20make%20the%20behavior%20more%20flexible.%20As%20it%20is%20used%20in%20the%20nav%20we%20are%20looking%20to%20correct%20the%20arbitrary%2C%20self-referencing%20link%20that%20gets%20assigned%20to%20a%20node%20acting%20as%20a%20%22header%22%20(no%20link)%20and%20get%20a%20fix%20out.%20Thanks.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-73398%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-73398%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%2F16848%22%20target%3D%22_blank%22%3E%40Charlie%20Lee%3C%2FA%3E%20-%20thanks%20for%20clarifying.%20We%20still%20have%20some%20work%20to%20do%20w%2F%20rendering%20horizontal%20nav%20in%20small%20viewports.%20We've%20logged%20the%20issue%20and%20will%20be%20working%20on%20a%20fix%20(for%20both%20team%20site%20w%2F%20managed%20nav%20-%20as%20you%20appear%20to%20have%20here%20-%20and%20our%20new%20communication%20site%20template%2C%20as%20it%20has%20a%20default%20horizontal%20nav).%20Thanks%20for%20reporting.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-73396%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-73396%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%2F1016%22%20target%3D%22_blank%22%3E%40Richard%20Sharp%3C%2FA%3E%20-%20thanks%20for%20the%20clarification.%20No%2C%20goal%20for%20pub%20provider%20support%20in%20modern%20control%20is%20to%20provide%20parity%20on%20key%20functionality%20to%20unblock%20folks%20from%20moving%20to%20modern.%20The%20support%20for%20level%203%20nodes%20is%20specific%20to%20horizontal%20managed%20navigation%20that%20we%20thought%20our%20previous%20fix%20addressed%2C%20so%20we're%20looking%20to%20address%20now%20(I'll%20keep%20thread%20apprised%20w%2F%20that%20status).%20The%20support%20for%20alt%20CSS%20is%20one%20we're%20also%20investigating%20further%2C%20as%20we%20need%20to%20see%20how%20this%20aligns%20w%2F%20the%20Fabric%20controls%20we%20are%20now%20using.%20I'm%20hoping%20that%20our%20Fabric%20improvements%20(design%20and%20interaction%20behavior)%20mitigate%20the%20need%20for%20alternate%20CSS%2C%20but%20acknowledge%20the%20feedback%20that%20we%20might%20need%20to%20provide%20affordances%20here.%20Thanks.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-72587%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-72587%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Sean%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGood%20request%20for%20clarification.%20Our%20(small)%20organization%20has%20all%20our%20files%20saved%20in%20a%20single%20document%20library.%20The%20primary%20way%20our%20staff%20navigates%20the%20document%20library%20is%20through%20tree-view%20control%20to%20filter%20the%20document%20library%20by%20nested%20metadata%20tags.%20(For%20us%2C%20this%20was%20the%20key%20to%20user%20adoption%2C%20allowing%20staff%20to%20use%20a%20UI%20that%20is%20similar%20to%20the%20one%20they%20were%20used%20to%20in%20their%20old%20file%20share%20with%20nested%20folders.%20Only%20instead%20with%20our%20SharePoint%20configuation%20they%20would%20be%20now%20using%20tags%20instead%20of%20folders.)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20re-reading%20this%20thread%2C%20our%20use%20case%20is%20indeed%20different%20from%20the%20primary%20one%20that%20this%20thread%20focuses%20on%3A%20we%20are%20not%20looking%20to%20have%20the%20top%20nav%20bar%20being%20used%20to%20navigate%20multiple%20sites%20(since%20we%20don't%20have%20multiple%20sites).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBut%20it%20is%20still%2C%20I%20think%2C%20relevent%20to%20the%20topic%20of%20managed%20metadata%20navigation.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20we%20are%20looking%20for%20is%20a%20way%20to%20%3CSPAN%3Ecreate%20dynamic%20metadata%20navigation%2C%20using%20the%20benefits%20of%20both%20Managed%20Metadata%20and%20Search.%20The%20result%20we%20want%20is%20a%20dynamic%20navigation%20that%20is%20built%26nbsp%3Bin%20through%20a%20taxonomy%20that%20shows%20the%20current%20search%20results%20filtered%20by%20the%20current%20node%20(with%20or%20without%20children%2C%20depending%20on%20the%20current%20configuration).%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EThis%20can%20be%20done%20through%20using%20Content%20Search%20Web%20Part%20as%20described%20here%3A%20%3CA%20href%3D%22https%3A%2F%2Fwww.itunity.com%2Farticle%2Fconfigure-managed-navigation-sharepoint-2013-step-step-94%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.itunity.com%2Farticle%2Fconfigure-managed-navigation-sharepoint-2013-step-step-94%3C%2FA%3E%20(that%20link%20also%20captures%20perfectly%20the%20navigation%20behavor%20we%20are%20looking%20for).%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHowever%2C%20we%20are%20an%20E1%20subscriber%20which%20only%20gives%20us%20access%20to%20SharePoint%20Online%201%20functionality%2C%20which%20does%20not%20include%20Content%20Search%20Web%20Part.%20There%20does%20not%20appear%20to%20be%20a%20way%20to%20do%20it%20through%20Content%20Query%20Web%20Part.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20we%20need%20to%20instead%20use%20this%20%22A%20No-Code%20Way%20to%20Hack%20SharePoint's%20URLs%20to%20Filter%20by%20Managed%20Metadata%20and%20Show%20Child%20Terms%22%20%3CA%20href%3D%22https%3A%2F%2Fwww.rightpoint.com%2F404%3Fitem%3D%252fblogs%252fviewpoint%252farchive%252f2015%252f01%252f08%252fa-no-code-way-to-hack-sharepoint-39-s-urls-to-show-child-managed-metadata-terms%26amp%3Buser%3Dextranet%255cAnonymous%26amp%3Bsite%3Dwebsite%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.rightpoint.com%2F404%3Fitem%3D%252fblogs%252fviewpoint%252farchive%252f2015%252f01%252f08%252fa-no-code-way-to-hack-sharepoint-39-s-urls-to-show-child-managed-metadata-terms%26amp%3Buser%3Dextranet%255cAnonymous%26amp%3Bsite%3Dwebsite%3C%2FA%3E%20which%20is%201)%20clumbsy%2C%20and%202)%20need%20to%20be%20done%20by%20hand%20every%20time%20there%20is%20a%20new%20term%20we%20want%20to%20give%20users%20a%20link%20to.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20ideas%20of%20how%20we%20might%20be%20able%20to%20achieve%20the%20desired%20navigation%20UI%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-71976%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-71976%22%20slang%3D%22en-US%22%3EThanks%20for%20reporting%2C%20Adrienne%20-%20as%20confirmed%20w%2F%20Scott%20and%20Richard%20we%20should%20be%20supporting%20three%20levels%20(Parent%20%26gt%3B%20Child%20%26gt%3B%20Grandchild)%20in%20horizontal%20managed%20navigation.%20We%20are%20actively%20investigating%20a%20fix%20and%20should%20have%20something%20out%20soon.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-71968%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-71968%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F54709%22%20target%3D%22_blank%22%3E%40Thaddeus%20Ferber%3C%2FA%3E%20-%20we%20are%20working%20on%20providing%20a%20modern%20metadata%20navigation%20experience%20for%20lists%2Flibraries%2C%20as%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F32817%22%20target%3D%22_blank%22%3E%40Miceile%20Barrett%3C%2FA%3E%20noted.%20Are%20you%20asking%20for%20the%20tree-view%20control%20for%20site%20nav%3F%20We%20aren't%20planning%20to%20bring%20that%20experience%20forward%20at%20this%20time%2C%20but%20I'd%20like%20to%20make%20sure%20I%20understand%20the%20ask%20and%20scenario%3B%20can%20you%20confirm%2Felaborate%3F%20Thanks.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-71964%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-71964%22%20slang%3D%22en-US%22%3EThanks%20Richard%20-%20yes%2C%20Scott%20and%20Adrienne%20reported%20same%20-%20we%20should%20be%20honoring%20three%20levels%20in%20horizontal%20managed%20nav.%20We%20are%20actively%20investigating%20a%20fix%20and%20should%20have%20something%20out%20soon.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-71050%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-71050%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20still%20are%20not%20seeing%20all%20our%20navigation%20rendered%20correctly%20when%20we%20move%20to%20the%20new%20UI.%26nbsp%3B%20We%20are%20using%20Managed%20Navigation.%26nbsp%3B%20We%20have%20the%20main%20level%20of%20sites%20listed%2C%20then%20subsites%2C%20then%20a%20third%20level%20of%20fly-out.%26nbsp%3B%20I%20was%20told%20this%20would%20still%20be%20supported%20in%20the%20new%20UI.%26nbsp%3B%20Please%20could%20someone%20confirm%20what%20the%20truth%20is%3F%3F%3F%26nbsp%3B%20We%20absolutely%20cannot%20move%20to%20the%20new%20UI%20without%20this.%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20989px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F14788i077EA2A5D1D6E993%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%222017-05-18%2010_47_40-Site%20Pages%20-%20All%20Pages%20-%20Internet%20Explorer.png%22%20title%3D%222017-05-18%2010_47_40-Site%20Pages%20-%20All%20Pages%20-%20Internet%20Explorer.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-70577%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-70577%22%20slang%3D%22en-US%22%3E%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F5937%22%20target%3D%22_blank%22%3E%40Sean%20Squires%3C%2FA%3E%20wrote%3A%3CBR%20%2F%3E%3CP%3EThanks%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F3377%22%20target%3D%22_blank%22%3E%40Abhimanyu%20Singh%3C%2FA%3E%20-%20yes%2C%20the%20intended%20design%20pattern%20of%20modern%20nav%20where%20nesting%20is%20used%20is%20for%20the%20parent%20header%20to%20have%20an%20expand%2Fcollapse%20target%20and%20a%20link%20target.%20Currently%2C%20if%20the%20parent%2Fheader%20doesn't%20have%20a%20link%20it%20gets%20treated%20like%20a%20self-referencing%20link%20(in%20this%20case%20to%20the%20root%20site%20collection).%26nbsp%3B%3CSTRONG%3ELet%20me%20discuss%20w%2F%20the%20team%20to%20see%20whether%20there%20are%20other%20options%3C%2FSTRONG%3E.%26nbsp%3B%3C%2FP%3E%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F5937%22%20target%3D%22_blank%22%3E%40Sean%20Squires%3C%2FA%3E%26nbsp%3Bwhat%20has%20been%20the%20outcome%20of%20your%20discussion%20with%20your%20team%20on%20this%3F%20This%20is%20a%20no-go%20for%20us.%20We%20carefully%20crafted%20the%20navigation%20for%20all%20our%20sites%2C%20and%20now%20suddenly%20the%20headers%20start%20pointing%20to%20the%20root.%20This%20is%20awful.%20Please%20make%20the%20headers%20with%20no%20links%2C%20behave%20like%20headers%20and%20nothing%20else.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOne%20way%20to%20solve%20this%20would%20be%20to%20NOT%20use%20those%20as%20self-referencing%20links%20at%20all.%20I%20mean%20do%20not%20use%20anchor%20element%20for%20such%20headers%20at%20all.%20Alternatively%2C%26nbsp%3Buse%20JavaScript%20to%20preventDefault%20on%20such%20headers.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPlease%20get%20this%20out%20already.%20It%20is%20ruining%20our%20experience.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-70575%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-70575%22%20slang%3D%22en-US%22%3E%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F5937%22%20target%3D%22_blank%22%3E%40Sean%20Squires%3C%2FA%3E%20wrote%3A%3CBR%20%2F%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F3377%22%20target%3D%22_blank%22%3E%40Abhimanyu%20Singh%3C%2FA%3E%20-%20this%20link%20is%20provided%20on%20modern%20pages%20to%20provide%20a%20quick%20way%20to%20get%20back%20to%20classic%20view%20mode.%20It%20is%20setting%20a%20session%20cookie%20-%20so%20you%20can%20close%20your%20browser%20session%20to%20revert%20back%20to%20modern%20(note%3A%20the%20team%20might%20be%20looking%20at%20making%20this%20more%20of%20a%20toggle%2C%20right%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F3771%22%20target%3D%22_blank%22%3E%40Lincoln%20DeMaris%3C%2FA%3E%3F%3C%2FP%3E%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%3CP%3EAny%20update%20on%20this%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F5937%22%20target%3D%22_blank%22%3E%40Sean%20Squires%3C%2FA%3E%26nbsp%3Band%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F3771%22%20target%3D%22_blank%22%3E%40Lincoln%20DeMaris%3C%2FA%3E%26nbsp%3B%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-69852%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-69852%22%20slang%3D%22en-US%22%3EHi%20Abhimanyu%2C%3CBR%20%2F%3E%3CBR%20%2F%3EAbout%20getting%20back%20to%20the%20modern%20view%2C%20this%20flag%20of%20current%20view%20is%20stored%20in%20a%20cookie.%20Even%20if%20you%20clear%20the%20cookies%20and%20refrersh%2C%20you%20will%20get%20back%20the%20modern%20view%20%3A)%3C%2Fimg%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fdigidottie.com%2F2017%2F02%2F14%2Fo365-sp-modern-to-classic-view%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdigidottie.com%2F2017%2F02%2F14%2Fo365-sp-modern-to-classic-view%2F%3C%2FA%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-69725%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-69725%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20is%20a%20great%20start%2C%20thanks!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECould%20you%20next%20also%20please%20bring%20back%20the%20tree%20interface%20for%20managed%20metadata%20navigation%20and%20filtering%20as%20described%20here%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fsharepoint.uservoice.com%2Fforums%2F329214-sites-and-collaboration%2Fsuggestions%2F19270162-bring-back-tree-interface-for-managed-metadata-nav%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%2F19270162-bring-back-tree-interface-for-managed-metadata-nav%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-68331%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-68331%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F5937%22%20target%3D%22_blank%22%3E%40Sean%20Squires%3C%2FA%3E%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20for%20your%20response%20and%20continued%20efforts%20to%20resolve%20these%20issues!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOne%20note%3A%20We%20also%20have%20Publishing%20sites%20using%20Structured%20navigation%20in%20global%2C%20with%20the%20same%20concept%20we%20use%20in%20our%20sites%20with%20Managed%20navigation.%20In%20looking%20at%20those%20sites%2C%20we%20see%20that%20Structured%20navigation%20also%20supports%20three%20levels%2C%20just%20the%20same%20as%20Managed%20Navigation.%20All%20that's%20required%20is%20that%20you%20check%20the%20box%20to%20Show%20Subsites%20in%20the%20navigation%20in%20the%20Level%202%20site.%20Then%20you%20see%20the%20flyouts%20just%20the%20same%20as%20you%20have%20in%20Managed%20navigation.%20The%20picture%20below%20is%20such%20a%20site%20(Classic%2C%20Publishing%2C%20Structured%20Global).%20It%20seems%20to%20be%20just%20the%20Publishing%20feature%20itself%20that%20enables%20the%20third%20level%2C%20which%20is%20what%20makes%20the%20feature%20so%20valuable!%20Thanks%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERichard%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20441px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F14328i203A465C65B6D1E0%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22PublishingStructuredGlobalThreeLevels.png%22%20title%3D%22PublishingStructuredGlobalThreeLevels.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-67639%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-67639%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20for%20the%20additional%20detail%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1016%22%20target%3D%22_blank%22%3E%40Richard%20Sharp%3C%2FA%3E%20(and%20sorry%20if%20I%20missed%20these%20previously).%20Yes%2C%20as%20we're%20effectively%20supporting%20the%20classic%20provider%20our%20goal%20is%20to%20have%20parity%20of%20behavior%20(which%2C%20incidentally%2C%20for%20structured%20is%20two-levels%20in%20global%20and%20current%2C%20but%20for%20managed%2C%20three-levels%20in%20global%20and%20two-levels%20for%20current)%20-%20so%20there%20appears%20to%20be%20a%20bug%20here%20(which%20others%20have%20since%20reported).%20We%20are%20investigating%20this%20now.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI've%20also%20noted%20the%20issue%20of%20your%20alternate%20CSS%20not%20being%20honored.%20We'll%20investigate%20this%20and%20get%20back%20to%20you%20via%20this%20thread.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks%20for%20reporting%20-%20I%20want%20to%20fulfill%20your%20goal%20and%20get%20you%20on%20the%20modern%20views!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-67637%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-67637%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%2F645%22%20target%3D%22_blank%22%3E%40Scott%20Joyner%3C%2FA%3E%20-%20the%20goal%20is%20to%20ensure%20functionality%20w%2F%20classic%20publishing%20provider%20(and%20that%20behavior)%26nbsp%3B%20-%20so%20for%20structured%20left%20and%20top%20that%20would%20be%20two-levels%20(parent-child)%2C%20but%20for%20managed%20top%20it%20looks%20like%20it's%20not%20rendering%20the%20third%20level%20(grandchild).%20We're%20investigating%20the%20issue%2C%20so%20thanks%20to%20you%20and%20Adrienne%20for%20reporting.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAs%20for%20long%20labels%2C%20yes%2C%20we%20should%20be%20truncating%20and%20providing%20full%20preview%20in%20the%20tooltip.%20We'll%20take%20another%20look%20at%20this%20one%20(thought%20it%20was%20previously%20fixed!).%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-67634%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-67634%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F48415%22%20target%3D%22_blank%22%3E%40Adrienne%20Kidd%3C%2FA%3E%20-%20apologies%2C%20I%20didn't%20see%20your%20inquiry%20last%20week.%20Yes%2C%20the%20new%20control%20does%20support%20flyout%2C%20but%20currently%20only%20two%20levels%20(parent%20and%20child)%20-%20which%20is%20parity%20for%20structured%20navigation%2C%20but%20not%20managed%20nav%20on%20global.%20I've%20opened%20a%20bug%20and%20we'll%20see%20if%20we%20can%20get%20this%20amended.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-67436%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-67436%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F11843%22%20target%3D%22_blank%22%3E%40Nate%20Clinton%3C%2FA%3E%26nbsp%3B-%20This%20is%20actually%20from%20Chrome%20on%20a%20desktop.%20%26nbsp%3BThis%20is%20not%20a%20device%20specific%20issue%2C%20its%20is%20specific%20to%20the%20screen%20resolution.%20%26nbsp%3BAny%20browser%20on%20any%20device%20which%20is%20trying%20to%20render%20the%20page%20on%20less%20than%20640px%20will%20not%20see%20the%20Top%20Navigation%20(highlighted%20below)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20640px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F14181iACFD60A14CBF03A0%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22global_nav_highlighted.png%22%20title%3D%22global_nav_highlighted.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHappy%20to%20have%20a%20call%20on%20this%20-%20please%20let%20me%20know%20how%20we%20would%20sort%20that%20out.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-66810%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-66810%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F5937%22%20target%3D%22_blank%22%3E%40Sean%20Squires%3C%2FA%3E%20-%20Thanks%20for%20the%20reply.%20As%20you'll%20see%20in%20the%20description%20and%20pictures%20in%20my%20post%20on%204-Apr-2017%2C%20the%20site%20I'm%20working%20on%20is%20a%20Classic%20SharePoint%20site%20with%20publishing%20turn%20on%20for%20the%20site%20collection%20and%20the%20top%20level%20site%2C%20using%20Managed%20navigation%20for%20global%20and%20Structured%20navigation%20for%20the%20Quick%20Launch.%20It%20is%20not%20a%20Modern%20site%2C%20but%20I%20did%20create%20a%20Modern%20page%20and%20I%20set%20the%20view%20for%20the%20document%20libraries%20to%20show%20the%20Modern%20view%20to%20see%20how%20the%20navigation%20would%20appear%20on%20those%20pages.%20On%20other%20pages%20the%20navigation%20appears%20as%20it%20always%20has.%20When%20I'm%20on%20a%20modern%20page%20or%20a%20document%20library%20with%20a%20modern%20view%2C%20the%20navigation%20loses%20the%20flyouts%20(labeled%20level%203%20in%20my%20screenshots)%20and%20does%20not%20follow%20the%20simple%20alternate%20CSS%20file%20I%20use%20simply%20to%20make%20each%20entry%20wider%2C%20put%20an%20outline%20around%20each%20entry%2C%20and%20add%20a%20highlight%20color%20when%20you%20mouse%20over%20an%20entry.%20The%20links%20(which%20omitted%20the%20%22%2Fsites%2Fsynctest%2F%22%20part%20of%20each%20link%20in%20my%20earlier%20description)%20are%20now%20correct%2C%20so%20that's%20an%20improvement!%20But%20the%20existing%20dropdowns%20have%20no%20outline%20or%20mouse-over%20highlight%20color%2C%20so%20they're%20very%20hard%20to%20see%2C%20and%20the%20flyout%20level%20is%20missing.%20So%20my%20question%20is%2C%20is%20there%20work%20still%20going%20on%20that%20will%20address%20these%20issues%2C%20or%20is%20the%20current%20state%20the%20intended%20end%20state%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMy%20goal%20is%20primarily%20to%20be%20able%20to%20turn%20on%20the%20modern%20views%20for%20document%20libraries%20and%20lists%20in%20existing%20Classic%20SharePoint%20sites%2C%20but%20I%20can't%20afford%20to%20lose%20the%20functionality%20of%20our%20current%20navigation.%20Thanks%20very%20much%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERichard%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-66801%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-66801%22%20slang%3D%22en-US%22%3EOk...%20so%20you%20are%20referring%20to%20the%20view%20in%20Safari%2Fetc.%20as%20well.%20In%20iOS%2C%20we%20should%20be%20displaying%20the%20nav%20natively.%20If%20you%20could%20check%20that%2C%20that'd%20be%20great.%20For%20Android%20we%20are%20doing%20that%20work%20soon.%20But%20that%20assumes%20I%20am%20referring%20to%20the%20right%20menu%20for%20you%20%3A)%3C%2Fimg%3E%20Might%20be%20better%20to%20chat%20on%20a%20call%20for%20this%20one%3F%20Thanks!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-66796%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-66796%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F11843%22%20target%3D%22_blank%22%3E%40Nate%20Clinton%3C%2FA%3E%26nbsp%3BIt%20occurs%20on%20any%20modern%20site.%20When%20the%20width%20drops%20below%20640px%20the%20whole%20global%20navigation%20is%20removed%20from%20the%20DOM.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESee%20attached.%20%26nbsp%3BI%20have%20removed%20site%20logo%20and%20name%20as%20it%20contained%20client%20specifics.%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20457px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F14082i7C2D35B4C33FF578%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22global_nav.png%22%20title%3D%22global_nav.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-66792%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-66792%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F16848%22%20target%3D%22_blank%22%3E%40Charlie%20Lee%3C%2FA%3E...%20we%20are%20looking%20into%20the%20device%20related%20issues%20now.%26nbsp%3B%20Quick%20question...%20are%20you%20only%20seeing%20this%20on%20Android%2C%20or%20iOS%20as%20well%3F%26nbsp%3B%20And%20it%20looks%20like%20the%20issue%20is%20that%20no%20nav%20appears%20at%20all%20in%20the%20mobile%20view%3F%26nbsp%3B%20If%20you%20have%20additional%20screenshots%2Fetc.%2C%20that'd%20be%20helpful.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks!%3CBR%20%2F%3ENate%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F31057%22%20target%3D%22_blank%22%3E%40Aneetha%20Jayaraman%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-66772%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-66772%22%20slang%3D%22en-US%22%3E%3CP%3EWill%20you%20be%20adding%20support%20for%20second%20level%20menu%20navigation%3F%20Currently%20it%20appears%20that%20you%20only%20have%20top%20levels%20displayed.%20Also%2C%20if%20the%20label%20is%20too%20long%20to%20display%20in%20the%20current%20width%2C%20can%20you%20add%20a%20rollover%20popup%20to%20show%20the%20full%20name%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-66658%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-66658%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F5937%22%20target%3D%22_blank%22%3E%40Sean%20Squires%3C%2FA%3E%2C%20the%20sooner%20we%20can%20get%20an%20idea%20of%20when%20this%20bug%20will%20be%20fixed%20the%20better%20as%20one%20of%20our%20customers%20is%20depending%20upon%20this.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-66526%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-66526%22%20slang%3D%22en-US%22%3E%3CP%3EStill%20waiting%20for%20a%20response%20to%20my%20question.%20%26nbsp%3B%3CSPAN%3EWe%20were%20told%20the%20new%20UI%20would%20support%20the%20flyouts%20in%20the%20managed%20navigation.%20%26nbsp%3BWe%20are%20still%20unable%20to%20move%20to%20the%20new%20UI%20because%20although%20we%20see%20one%20level%20of%20subsites%2C%20we%20do%20not%20see%20the%20next%20level%20as%20flyouts%2C%20which%20we%20rely%20on%20in%20our%20existing%20navigation.%20%26nbsp%3BPlease%20confirm.%20%26nbsp%3BThanks!%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-66509%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-66509%22%20slang%3D%22en-US%22%3E%3CP%3EThank%20you!%26nbsp%3B%20I%20can%20now%20fully%20support%20rolling%20out%20modern%20lists%20to%20our%20entire%20user%20base.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGreat%20job!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAaron%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-65835%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-65835%22%20slang%3D%22en-US%22%3ECharlie%20-%20known%20limitation%2C%20but%20let%20me%20or%20Nate%20get%20back%20to%20thread%20w%2F%20more%20detail.%20Thanks.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-65834%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-65834%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%2F1016%22%20target%3D%22_blank%22%3E%40Richard%20Sharp%3C%2FA%3E%20-%20apologies%20if%20I%20missed%20an%20earlier%20comment%20-%20this%20work%20was%20to%20support%20structured%2Fmanaged%20nav%20on%20modern%20pages%20in%20classic%20team%20sites.%20Enabling%20the%20publishing%20feature%20in%20a%20modern%20team%20site%20is%20not%20a%20supported%20state%20as%20it%20causes%20other%20issues%20-%20most%20pertinently%2C%20edits%20to%20settings%20cannot%20be%20persisted%20(please%20see%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fmsdn.microsoft.com%2Fen-us%2Fpnp_articles%2Fmodern-experience-customizations-customize-sites%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fmsdn.microsoft.com%2Fen-us%2Fpnp_articles%2Fmodern-experience-customizations-customize-sites%3C%2FA%3E%20for%20more%20details).%20Thanks%2C%20Sean%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-65833%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-65833%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F50984%22%20target%3D%22_blank%22%3E%40Bernd%20Diel%3C%2FA%3E%20-%20that%20is%20the%20plan%2C%20to%20ensure%20parity%20of%20settings%20across%20devices.%20Adding%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F11843%22%20target%3D%22_blank%22%3E%40Nate%20Clinton%3C%2FA%3E%20for%20notice%2Fcomment%20(I'll%20also%20follow-up%20on%20this%20one).%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-65667%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-65667%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F50984%22%20target%3D%22_blank%22%3E%40Bernd%20Diel%3C%2FA%3E%26nbsp%3BWe%20are%20also%20seeing%20this%20and%20its%20a%20massive%20problem%20for%20us.%20%26nbsp%3BHow%20can%20we%20rely%20on%20a%20Global%20Navigation%20that%20is%20not%20present%20on%20all%20devices%20(or%20resolutions)%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F5937%22%20target%3D%22_blank%22%3E%40Sean%20Squires%3C%2FA%3E%26nbsp%3BIs%20this%20a%20bug%2C%20a%20known%20limitation%2C%20or%20by%20design%3F%20%26nbsp%3BWhat%20is%20the%20recommendation%20for%20shared%20global%20navigation%20across%20site%20collections%20which%20works%20on%20all%20devices%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-64778%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-64778%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20were%20told%20the%20new%20UI%20would%20support%20the%20flyouts%20in%20the%20managed%20navigation.%20%26nbsp%3BWe%20are%20still%20unable%20to%20move%20to%20the%20new%20UI%20because%20although%20we%20see%20one%20level%20of%20subsites%2C%20we%20do%20not%20see%20the%20next%20level%20as%20flyouts%2C%20which%20we%20rely%20on%20in%20our%20existing%20navigation.%20%26nbsp%3BPlease%20confirm.%20%26nbsp%3BThanks!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-64730%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-64730%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F5937%22%20target%3D%22_blank%22%3E%40Sean%20Squires%3C%2FA%3E%20-%20As%20far%20as%20I%20can%20see%2C%20neither%20structured%20nor%20managed%20navigation%20work%20in%20modern%20sites%20when%20the%20Publishing%20site%20collection%20feature%20is%20turned%20on.%20Is%20your%20group%20continuing%20work%20in%20this%20area%20to%20resolve%20these%20issues%2C%20or%20is%20this%20now%20considered%20the%20end%20state%3F%20Thanks%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERichard%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-62395%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-62395%22%20slang%3D%22en-US%22%3EGreat%20Job%20!%3CBR%20%2F%3EBut%20what%20about%20the%20mobile%20view.%20When%20I%20open%20the%20modern%20UI%20Site%20with%20the%20activated%20global%20Metadata%20Navigation%20on%20my%20phone%2C%20the%20global%20Navigation%20disappears%20%3A(%3C%2Fimg%3E%20I%20hoped%20there%20would%20be%20an%20Integration%20with%20the%20hamburger%20menu%20or%20something%20like%20this.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-59919%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-59919%22%20slang%3D%22en-US%22%3E%3CP%3EYes%2C%20I'm%20still%20seeing%20the%20issue.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-59700%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-59700%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F5937%22%20target%3D%22_blank%22%3E%40Sean%20Squires%3C%2FA%3E%26nbsp%3BPerhaps%20it's%20just%20me%2C%20but%20I%20still%20see%20the%20same%20problems%20with%20Global%20navigation%20(Publishing%20turned%20on%2C%20using%20Managed%20Navigation%20(term%20set%20under%20the%20Site%20Collection%20tree)%2C%20with%20a%20simple%20custom%20CSS%20to%20outline%20the%20drop-down%20boxes%20and%20shade%20them%20light%20blue%20on%20hover-over)%20that%20I've%20seen%20in%20the%20past%20when%20viewed%20from%20a%20Modern%20Document%20Library.%20It%20works%20fine%20when%20viewed%20from%20a%20classic%20page.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EViewed%20from%20classic%20(home%20page%20of%20%22Sync%20Client%20Test%20Site%22%20site%20collection)%3A%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-left%22%20style%3D%22width%3A%20592px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F12791i04F082E861D3E79A%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Classic.png%22%20title%3D%22Classic.png%22%20%2F%3E%3C%2FSPAN%3E%26nbsp%3B%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%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESeen%20from%20a%20Modern%20Document%20Library%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-left%22%20style%3D%22width%3A%20383px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F12792i65FA82FF9EA1DF07%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Modern.png%22%20title%3D%22Modern.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%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20the%20Modern%20view%2C%20there%20are%20no%20Level%203%20flyouts%2C%20no%20observation%20of%20the%20custom%20CSS%2C%20and%20all%20the%20underlying%20links%20are%20wrong%3A%20they%20all%20omit%20the%20%22%2Fsites%2Fsynctest%2F%22%20portion%20of%20the%20URL%20(i.e.%2C%20the%20portion%20that%20specifies%20the%20site%20collection%20home).%20The%20only%20link%20that%20works%20is%20the%20default%20icon%20that%20takes%20you%20to%20the%20Home%20of%20the%20site.%20In%20the%20classic%20view%2C%20all%20the%20links%20work%20as%20expected.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20I%20look%20at%20%2Fsites%2Fsynctest%2F_layouts%2F15%2Ftopnav.aspx%2C%20there%20is%20only%20one%20link%20there%2C%20%22Home%22%2C%20and%20it%20links%20to%20%22%2Fsites%2Fsynctest%22.%20Surely%20we're%20not%20supposed%20to%20have%20to%20edit%20that%20page%20on%20every%20site%20we've%20ever%20created%20to%20rebuild%20our%20navigation%3F%20Here's%20what%20my%20term%20store%20entry%20looks%20like%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-left%22%20style%3D%22width%3A%20303px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F12793iB829A0ADBBFCCD23%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22TermStore2.png%22%20title%3D%22TermStore2.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%3E%26nbsp%3B%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%26nbsp%3B%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%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20ideas%3F%20Thanks!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERichard%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-59674%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-59674%22%20slang%3D%22en-US%22%3EPooya%20-%20flight%20rollout%20didn't%20complete%20until%20probably%20early%20afternoon%20yesterday.%20Can%20you%20confirm%20you%20are%20still%20seeing%20the%20issue%3F%20Thanks.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-59670%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-59670%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%2F3377%22%20target%3D%22_blank%22%3E%40Abhimanyu%20Singh%3C%2FA%3E%20-%20this%20link%20is%20provided%20on%20modern%20pages%20to%20provide%20a%20quick%20way%20to%20get%20back%20to%20classic%20view%20mode.%20It%20is%20setting%20a%20session%20cookie%20-%20so%20you%20can%20close%20your%20browser%20session%20to%20revert%20back%20to%20modern%20(note%3A%20the%20team%20might%20be%20looking%20at%20making%20this%20more%20of%20a%20toggle%2C%20right%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F3771%22%20target%3D%22_blank%22%3E%40Lincoln%20DeMaris%3C%2FA%3E%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-59668%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-59668%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F3377%22%20target%3D%22_blank%22%3E%40Abhimanyu%20Singh%3C%2FA%3E%20-%20yes%2C%20the%20intended%20design%20pattern%20of%20modern%20nav%20where%20nesting%20is%20used%20is%20for%20the%20parent%20header%20to%20have%20an%20expand%2Fcollapse%20target%20and%20a%20link%20target.%20Currently%2C%20if%20the%20parent%2Fheader%20doesn't%20have%20a%20link%20it%20gets%20treated%20like%20a%20self-referencing%20link%20(in%20this%20case%20to%20the%20root%20site%20collection).%26nbsp%3BLet%20me%20discuss%20w%2F%20the%20team%20to%20see%20whether%20there%20are%20other%20options.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-59664%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-59664%22%20slang%3D%22en-US%22%3EThanks%20for%20reporting.%20The%20feature%20crew%20has%20been%20notified%20and%20is%20investigating%20(appears%20to%20be%20an%20issue%20specifically%20w%2F%20Edge%20browser).%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-59290%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-59290%22%20slang%3D%22en-US%22%3E%3CP%3EIssue%20is%20still%20there.%20The%20submenu%20in%20the%20structural%20navigation%20opens%20the%20Site%20above%20while%20the%20config%20is%20correct%20at%26nbsp%3B%2F_layouts%2F15%2Fquiklnch.aspx%20and%26nbsp%3B%2F_layouts%2F15AreaNavigationSettings.aspx%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-59182%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-59182%22%20slang%3D%22en-US%22%3E%3CP%3EAnd%20while%20you%20are%20at%20it%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F5937%22%20target%3D%22_blank%22%3E%40Sean%20Squires%3C%2FA%3E%2C%20could%20you%20also%20please%20help%20me%20with%20a%20conundrum%20am%20facing%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThere%20is%20a%20%22%3CEM%3E%3CSTRONG%3EReturn%20to%20classic%20SharePoint%3C%2FSTRONG%3E%3C%2FEM%3E%22%20link%20at%20the%20bottom%20of%20the%20current%20navigation%20(%3CEM%3Eleft-pane%3C%2FEM%3E).%20When%20I%20click%20it%2C%20I%20am%20taken%20to%20the%20classic%20mode.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3EQuestion%3C%2FSTRONG%3E%20----%20How%20do%20I%20%3CEM%3E%3CSTRONG%3Eget%20back%20to%20modern-mode%3C%2FSTRONG%3E%3C%2FEM%3E%20from%20the%20classic-mode%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-59172%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-59172%22%20slang%3D%22en-US%22%3E%3CP%3EThank%20you%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F5937%22%20target%3D%22_blank%22%3E%40Sean%20Squires%3C%2FA%3E.%20I%20can%20see%20that%20the%20navigation%20elements%20are%20now%20fixed.%20This%20resolves%20by%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FSharePoint%2FStructured-Navigation-Publishing-not-supported-on-quot-Modern%2Fm-p%2F49174%2Fhighlight%2Ftrue%23M4715%22%20target%3D%22_blank%22%3Eearlier%20problem%20of%20inconsistent%20navigation%3C%2FA%3E%20between%20classic%20and%20modern.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHowever%2C%20now%20another%20problem%20remains%20(%3CEM%3EI%20haven't%20done%20a%20comprehensive%20testing%20yet%3C%2FEM%3E%3A(%3C%2Fimg%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20headers%20in%20our%20current%20navigation%20(left-pane)%2C%20and%20these%20headers%20do%20not%20have%20links.%20While%20this%20works%20correctly%20as%20intended%20in%20the%20classic-mode%2C%20the%20modern-mode%20adds%20a%20link%20to%20the%20root%20site-collection%20for%20these%20link-less%20(%3CEM%3EI%20don't%20know%20what%20you%20call%20those%3C%2FEM%3E)%20headers.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThese%20comparative%20screenshots%20show%20you%20what%20I%20am%20talking%20about%3A%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20208px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F12731i038B756984ED0C2E%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22modern-nav-02.png%22%20title%3D%22modern-nav-02.png%22%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-caption%22%20onclick%3D%22event.preventDefault()%3B%22%3EModern-Mode%20(headers%20are%20linked)%3C%2FSPAN%3E%3C%2FSPAN%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-left%22%20style%3D%22width%3A%20208px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F12732i2EA49359BE2E22E4%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22modern-nav-01.png%22%20title%3D%22modern-nav-01.png%22%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-caption%22%20onclick%3D%22event.preventDefault()%3B%22%3EClassic-Mode%20(headers%20remain%20unlinked)%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-58844%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-58844%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%40Deleted%20-%20no%2C%20this%20fix%20is%20specific%20to%20ensuring%20support%20for%20modern%20pages%20in%20classic%20team%20sites%20only.%20We%20do%20not%20recommend%20enabling%20classic%20publishing%20infrastructure%20service%20feature%20on%20a%20modern%2C%20group-connected%20team%20site%20(see%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fmsdn.microsoft.com%2Fen-us%2Fpnp_articles%2Fmodern-experience-customizations-customize-sites%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fmsdn.microsoft.com%2Fen-us%2Fpnp_articles%2Fmodern-experience-customizations-customize-sites%3C%2FA%3E)%3B%20it%20is%20technically%20possible%20to%20do%2C%20but%20an%20unsupported%20configuration%20at%20this%20time.%20Hope%20that%20helps!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-58837%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-58837%22%20slang%3D%22en-US%22%3EYes%2C%20let%20me%20know%20if%20you%20still%20have%20issues%20after%20next%20Monday.%20Thanks!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-58597%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-58597%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ejust%20to%20get%20a%20definitiv%20answer%2C%20activating%20SharePoint%20Server%20Publishing%20Infrastructure%20is%20now%20supported%20again%20by%20Microsoft%26nbsp%3Bfor%20SharePoint%20Online%20Teamsites%20(both%20classic%20and%20modern%20and%20classic%20with%20modern%20pages)%20to%20get%20Managed%20Navigation%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20is%20important%20information%20for%20us.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EKind%20regards%2C%3C%2FP%3E%3CP%3EAndy%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-58553%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-58553%22%20slang%3D%22en-US%22%3E%3CP%3EGreat%20to%20see%20this%20in%20my%20tenancy%20this%20morning%20-%20thanks%20team%20for%20resolving!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-58387%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-58387%22%20slang%3D%22en-US%22%3ENot%20sure%20if%20this%20is%20still%20rolling%20out%2C%20but%20my%20first%20release%20account%20doesn't%20correctly%20display%20the%20structural%20global%20navigation%20in%20a%20sub%20site.%20It's%20missing%20the%20root%20site%20%22Home%22%20link%20in%20the%20child%20sites.%3CBR%20%2F%3E%3CBR%20%2F%3EIn%20classic%20I%20get%20(when%20visiting%20subsite%3A%20Child%201)%3A%3CBR%20%2F%3EHome%20(%2Fsites%2Fsitea)%3CBR%20%2F%3EChild%201%20(%2Fsites%2Fsitea%2Fchild1)%3CBR%20%2F%3EChild%202%20(%2Fsites%2Fsitea%2Fchild2)%3CBR%20%2F%3E%3CBR%20%2F%3EIn%20modern%20I%20get%20(when%20visiting%20subsite%3A%20Child%201)%3A%3CBR%20%2F%3EChild%201%20(%2Fsites%2Fsitea%2Fchild1)%3CBR%20%2F%3EChild%202%20(%2Fsites%2Fsitea%2Fchild2)%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-58380%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-58380%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20borders%20around%20the%20colun%20headers%20as%20well.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-58265%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-58265%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20structural%20navigation%20is%20now%20broken%20for%20me.%20It%20worked%20for%20a%20couple%20of%20days%20and%20now%20the%20submenu%20in%20the%20structural%20navigation%20opens%20the%20Site%20above%20the%20Site%20I%20have%20set.%20Editing%20at%20%22quicklinks.aspx%22%20or%20%22AreaNavigationSettings.aspx%22%20doesn't%20help.%20The%20links%20are%20correct%20and%20it%20still%20opens%20the%20Site%20above.%20Adding%20new%20items%20also%20results%20in%20the%20same%20behavior.%20The%20order%20for%20both%20the%20structural%20and%20global%20navigation%20was%20also%20randomized%20on%20it's%20own%20today.%20Also%20tried%20adding%20a%20sub%20menu%20in%20the%20global%20nav%20and%20the%20items%20all%20open%20blank%20pages.%20Don't%20even%20want%20to%20fix%20the%20global%20nav%20anymore.%20Would%20be%20nice%20if%20something%20as%20basic%20as%20navigation%20would%20simply%20work.%20Regret%20having%20adviced%20the%20customer%20to%20make%20use%20of%20the%20modern%20pages.%20It's%20kind%20of%20hard%20to%20explain%20to%20a%20customer%20that%20you%20had%20to%20spend%20more%20than%20a%20day%20to%20fix%20something%20as%20basic%20as%20the%20navigation.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eedit-%20just%20noticed%20that%20you%20mentioned%20that%20the%20fix%20should%20be%20deployed%20by%20the%20end%20of%20this%20week%20in%20the%20other%20post.%20Have%20advised%20the%20customer%20to%20wait%20and%20create%20a%20ticket%20if%20it's%20still%20not%20working%20after%20Friday.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-58047%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-58047%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F5937%22%20target%3D%22_blank%22%3E%40Sean%20Squires%3C%2FA%3E%26nbsp%3BLooks%20like%20it%20is%20working%20as%20expected%20today!!%20%26nbsp%3Bit%20was%20with%20structured%20navigation%20by%20the%20way%2C%20thanks%20looks%20great.%20%26nbsp%3BMight%20be%20able%20to%20roll%20this%20out%20to%20our%20production%20tenant%20soon%20after%20the%20fix%20is%20rolled%20to%20all%20non-first%20release%20tenants.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-57594%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-57594%22%20slang%3D%22en-US%22%3EThanks%20Kiran%20-%20no%2C%20that%20configuration%20is%20not%20in%20this%20fix.%20We%20are%20still%20evaluating%20design%20options%20to%20support%20that%20in%20the%20new%20control%3B%20current%20behavior%20will%20be%20to%20open%20site%20links%20in%20same%20tab%20and%20related%20workload%20links%20(mailbox%2C%20calendar%2C%20planner)%20in%20a%20new%20tab.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-57593%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-57593%22%20slang%3D%22en-US%22%3EFR%20roll%20went%20out%20today%20-%20if%20you're%20still%20seeing%20the%20issue%20tomorrow%2C%20let%20me%20know%20and%20we%20can%20troubleshoot%20(is%20this%20w%2F%20structured%20or%20managed%20nav%3F)%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-57590%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-57590%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F60%22%20target%3D%22_blank%22%3E%40Juan%20Carlos%20Gonz%C3%A1lez%20Mart%C3%ADn%3C%2FA%3E!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-57589%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-57589%22%20slang%3D%22en-US%22%3ENoted!%20We're%20actually%20already%20working%20to%20implement%20better%20overflow%20logic%20-%20consistent%20w%2F%20other%20column%20header%20behaviors.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-57588%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-57588%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F226%22%20target%3D%22_blank%22%3E%40John%20Wynne%3C%2FA%3E%26nbsp%3BHi%20John%2C%20no%20this%20fix%20is%20specific%20to%20navigation%20-%20but%20that%20doesn't%20look%20right.%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F3771%22%20target%3D%22_blank%22%3E%40Lincoln%20DeMaris%3C%2FA%3E%26nbsp%3B-%20have%20you%20seen%20or%20heard%20other%20reports%20of%20this%20issue%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-57542%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-57542%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F5937%22%20target%3D%22_blank%22%3E%40Sean%20Squires%3C%2FA%3E%26nbsp%3BShould%20this%20be%20in%20all%20first%20release%20tenants%20yet%3F%20%26nbsp%3BI%20have%20a%20developer%20tenant%20that%20I%20am%20not%20seeing%20those%20changes%20in%20yet.%20%26nbsp%3BI%20am%20still%20seeing%20the%20hidden%20%22page%20not%20found%22%20page%20in%20both%20the%20global%20and%20quick%20launch%20navigation.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-57442%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-57442%22%20slang%3D%22en-US%22%3E%3CP%3EGreat%20job%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F5937%22%20target%3D%22_blank%22%3E%40Sean%20Squires%3C%2FA%3E%26nbsp%3Band%20team%20for%20monitoring%20the%20forum.%3C%2FP%3E%3CP%3EDoes%20the%20fix%20include%20ability%20to%20control%20the%20behaviour%20of%20opening%20in%20new%20tab%20vs%20same%20tab%3F%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-57431%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-57431%22%20slang%3D%22en-US%22%3EDespite%20this%20minor%20issues%20%3A-)%2C%20congratulations%20to%20the%20team%20for%20adding%20support%20to%20structural%20navigation%20in%20modern%20team%20sites!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-57424%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-57424%22%20slang%3D%22en-US%22%3E%3CP%3EIs%20it%20possible%20to%20finetune%20the%20width%26nbsp%3Bto%20better%20support%20non-English%20longer%20words...%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20363px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F12474i2DF591015ABD1F81%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20alt%3D%22menu.png%22%20title%3D%22menu.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-57394%22%20slang%3D%22en-US%22%3ERe%3A%20UPDATE%3A%20Support%20for%20Structured%2FManaged%20Navigation%20enabled%20on%20Modern%20Pages%20in%20Classic%20Team%20Sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-57394%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Sean%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20seeing%20a%20new%20grid%20on%20document%20libraries%20today%20in%20FR.%20Is%20this%20part%20of%20this%20update%3F%20It's%20rendering%20like%20this%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%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%2F12469i32605B7617E3185C%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22docgrid.PNG%22%20title%3D%22docgrid.PNG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3C%2FLINGO-BODY%3E

@Sean Squires wrote:

Hi @Abhimanyu Singh - this link is provided on modern pages to provide a quick way to get back to classic view mode. It is setting a session cookie - so you can close your browser session to revert back to modern (note: the team might be looking at making this more of a toggle, right @Lincoln DeMaris?


Any update on this @Sean Squires and @Lincoln DeMaris ?


@Sean Squires wrote:

Thanks @Abhimanyu Singh - yes, the intended design pattern of modern nav where nesting is used is for the parent header to have an expand/collapse target and a link target. Currently, if the parent/header doesn't have a link it gets treated like a self-referencing link (in this case to the root site collection). Let me discuss w/ the team to see whether there are other options


@Sean Squires what has been the outcome of your discussion with your team on this? This is a no-go for us. We carefully crafted the navigation for all our sites, and now suddenly the headers start pointing to the root. This is awful. Please make the headers with no links, behave like headers and nothing else.

 

One way to solve this would be to NOT use those as self-referencing links at all. I mean do not use anchor element for such headers at all. Alternatively, use JavaScript to preventDefault on such headers. 

 

Please get this out already. It is ruining our experience.

We still are not seeing all our navigation rendered correctly when we move to the new UI.  We are using Managed Navigation.  We have the main level of sites listed, then subsites, then a third level of fly-out.  I was told this would still be supported in the new UI.  Please could someone confirm what the truth is???  We absolutely cannot move to the new UI without this.2017-05-18 10_47_40-Site Pages - All Pages - Internet Explorer.png

Thanks Richard - yes, Scott and Adrienne reported same - we should be honoring three levels in horizontal managed nav. We are actively investigating a fix and should have something out soon.

@Thaddeus Ferber - we are working on providing a modern metadata navigation experience for lists/libraries, as @Miceile Barrett noted. Are you asking for the tree-view control for site nav? We aren't planning to bring that experience forward at this time, but I'd like to make sure I understand the ask and scenario; can you confirm/elaborate? Thanks.

Thanks for reporting, Adrienne - as confirmed w/ Scott and Richard we should be supporting three levels (Parent > Child > Grandchild) in horizontal managed navigation. We are actively investigating a fix and should have something out soon.

Hi Sean,

 

Good request for clarification. Our (small) organization has all our files saved in a single document library. The primary way our staff navigates the document library is through tree-view control to filter the document library by nested metadata tags. (For us, this was the key to user adoption, allowing staff to use a UI that is similar to the one they were used to in their old file share with nested folders. Only instead with our SharePoint configuation they would be now using tags instead of folders.)

 

In re-reading this thread, our use case is indeed different from the primary one that this thread focuses on: we are not looking to have the top nav bar being used to navigate multiple sites (since we don't have multiple sites).

 

But it is still, I think, relevent to the topic of managed metadata navigation.

 

What we are looking for is a way to create dynamic metadata navigation, using the benefits of both Managed Metadata and Search. The result we want is a dynamic navigation that is built in through a taxonomy that shows the current search results filtered by the current node (with or without children, depending on the current configuration).

 

This can be done through using Content Search Web Part as described here: https://www.itunity.com/article/configure-managed-navigation-sharepoint-2013-step-step-94 (that link also captures perfectly the navigation behavor we are looking for).

 

However, we are an E1 subscriber which only gives us access to SharePoint Online 1 functionality, which does not include Content Search Web Part. There does not appear to be a way to do it through Content Query Web Part.

 

So we need to instead use this "A No-Code Way to Hack SharePoint's URLs to Filter by Managed Metadata and Show Child Terms" https://www.rightpoint.com/404?item=%2fblogs%2fviewpoint%2farchive%2f2015%2f01%2f08%2fa-no-code-way-... which is 1) clumbsy, and 2) need to be done by hand every time there is a new term we want to give users a link to.

 

Any ideas of how we might be able to achieve the desired navigation UI?

Hi @Richard Sharp - thanks for the clarification. No, goal for pub provider support in modern control is to provide parity on key functionality to unblock folks from moving to modern. The support for level 3 nodes is specific to horizontal managed navigation that we thought our previous fix addressed, so we're looking to address now (I'll keep thread apprised w/ that status). The support for alt CSS is one we're also investigating further, as we need to see how this aligns w/ the Fabric controls we are now using. I'm hoping that our Fabric improvements (design and interaction behavior) mitigate the need for alternate CSS, but acknowledge the feedback that we might need to provide affordances here. Thanks. 

Hi @Charlie Lee - thanks for clarifying. We still have some work to do w/ rendering horizontal nav in small viewports. We've logged the issue and will be working on a fix (for both team site w/ managed nav - as you appear to have here - and our new communication site template, as it has a default horizontal nav). Thanks for reporting.

Abhimanyu - thanks for bump - yes, the controls team is looking at options to make the behavior more flexible. As it is used in the nav we are looking to correct the arbitrary, self-referencing link that gets assigned to a node acting as a "header" (no link) and get a fix out. Thanks.

Hi Sean - It appears that our 'grandchild' links are rendering when in the view of the library, but NOT in the modern page.  When can we expect this functionality to appear consistently throughout the system?

Hi Adrienne - you beat my announcement! The fix to support L3 links in managed nav horizontal orientation had to be made in two different code bases. It might have still been rolling through. I'll check a test tenant, but let me know if you don't see it next week. Thanks!

The grandchild links seem to show up, but when we try to use them, we are just taken to the 'child' site.  We seem to have halfway there!  We desperately want to upgrade to the New Experience lists and libraries, but this navigation issue is SERIOUSLY holding us back.  Help!

We are having a simlar issue.  Submenus are always directing users to the URL of the site above.  For example using the new Managed Metadata option with the menu, we may have Dept...HR...Benefits, but it take to the HR link for this and all other submenu items.

 

Same here, in IE Level 3 just takes us to Level 2

in other browsers Level 3 items are not clickable. there is no link underneath

 

Please don't tructuate menu items!

I know Microsoft are a huge fan of the ... but in a menu this really should not happen.

I currently see both options, so no trunctuation does seem possible!

 

Would it be possible to have the submenus fly out a little snappier?

I always see users click the headers since the menus just take that bit too long to appear.

 

 

menu4.PNGmenu5.PNG

@Philine von Guretzky, I agree completely -- menu item truncation and and the considerably slower interaction time with the dropdowns and flyouts make the current Managed navigation experience in Modern mode considerably less useful and pleasant than in Classic mode. If we can regain the ability to utilize CSS to customize the appearance of the dropdowns/flyouts, we would, of course, have control over this. Short of that, at least eliminating truncation would be preferable.

 

One of the main reasons to go to Managed navigation in large sites is the lightning fast display and interaction with the menus in the Global navigation. Since links to third levels don't yet work, I'm sure this is a work in progress.

 

Sorry I missed this comment last week - yes, we learned there was a regression that broke the rendering of the L3 URL. A fix has already been patched and should be rolling to PROD.

@Glenn Goldberg@Denis Tiri @Scott Joyner, - Sorry I missed these comment last week - yes, we learned there was a regression that broke the rendering of the L3 URL. A fix has already been patched and should be rolling to PROD. Apologies - thanks for your patience!

@Sean Squires3rd level links now seem to work. Great news, thanks!

 


Menu1.PNGPageMenu2.PNGLibrary

 

 

 

 

 

 

 

Just flagging this again, the menu does however look different within the same site collection. On a page all menu items are fully visible, as soon as I am in a list/library the menu items are cut off.

 

 

does not work at my tenant yet, hoping it does soon

What on earth is going on?  Our navigation is still all messed up.  When there is a third level flyout, it stops the second level fly-out from working.

 

We urgently need to upgrade to the modern library experience, and have been wanting to all year, but this failure to render the navigation is stopping us from doing so. 

 

Please can you provide an update??

@Sean Squires This is still not working.  When there is a third level, the second level stops working.  This is the only thing stopping us from moving to the new library experience, which we are desperate to do.   Please can you help??

I can confirm, that the second level does not work when there is a third.

@Adrienne Kidd - very sorry about this; we validated this very scenario when we rolled the fix out earlier this month - but I'm now able to repro, too. I have an engineer investigating.

Hello!

 

A little late to the party here, but trying to solve for navigation on a new Modern site. In the Classic sites it was very easy and straight-forward to create a horizontal navigation bar. This allowed users to select from over 50 wiki pages in a very organized fashion. However, unless I'm missing something, I can't determine how to create a horizontal navigation bar in the modern pages environment without having to go through the Navigation menu in Site Settings. Is there not an easy "Edit Links" button that someone could use?

Hi @Adrienne Kidd - terribly sorry to have gone dark on you. I was out of town and thought an update was shared. The regression took a bit longer to isolate and fix, but I'm happy to report that a fix is in and should be rolling out this week (fully in by end of week). I'm looking into a related issue w/ the browser status reporting the URL of the node w/ focus, but the L2 and L3 links are correctly rendering. Thanks for your patience!

Hi @Peter Mcdermott - if you have sufficient permissions you should see an inline edit button that allows you to add, move, and group navigation links. From the pages library there's also an option in the context menu to add to the navigation. Take a look at this article for more details: https://support.office.com/en-us/article/Customize-the-navigation-on-your-SharePoint-site-3cd61ae7-a... (let us know if you have other questions). Thanks!


@Sean Squires, thank you for the link. This bullet point addressed my concern:

 

"In SharePoint Online, you can only customize the left-hand menu on a team site at this time unless you are in classic mode."

Of course - and yes, missed your note that you were looking to edit horizontal. In modern team we're moving to a left, vertical nav only - but will materialize the classic horizontal nav if you have subsites. You can, of course, continue to edit the toplink nav bar directly, but only through classic settings/page. Thanks.

@Sean Squires Really like the push for the modern and especially a Responsive experience, as that is absolutely essential in pushing SharePoint to a client now adays, the first thing a client asks is "is it responsive?". So far, huge leaps have been made and its looking good!
Big issue however is the Top nav not being included. Any idea on when we can expect to have the Top Navigation into the mobile experience? As previously mentioned it dissepears when the screen is 640px or something like that.
As of right now, its hard to recomend the client a navigation option that includ the Top nav at all, as we do not really know when it will be possible to use it in the mobile view. If we use the top nav,  the user cant navigate properly using the phone.

This leads us to use the Quick Luanch navigation entierely. But that hits on another problem. The navigation is not collapsed as default. This means that without a top navigation the left navigation becomes extreamly cluttered and large, and is expanded by default.

3 things:
1. Top nav need to be shown in the mobile experience, is this still the plan? And if so whats the ETA?

2. Left nav desperately need to have "Collapsed" as default option.

3. Aditionally, on nother note, the ms-siteLogo-defaultLogo link needs to have the option to allways link to the top site collection landing page. Without the ability to inject JS this needs to be an option, as that is one of the main things i allways get requested to fix for our clients as developer.


Regards

 

+100 for Left nav desperately need to have "Collapsed" as default option.

What is planned for intelligent/not manual site navigation for modern pages? This doesn't feel very modern.

@Sean Squires, I just noticed this discussion. 

 

Are there any plans to make Managed Navigation work across multiple site collections?

@Sean Squires, The problem I'm having sounds similar, but not quite the same as anyone here.

 

I'm using Managed Metadata navigation. On classic pages, both the level-1 and level-2 terms are working fine:

Level-1 term: http://siteurl.com/docLibrary  (correct)

Level-2 term: http://siteurl.com/docLibrary/category1  (correct)

 

On modern pages, my level-1 term continues to work fine, but my level-2 term become corrupt and duplicate the level-2 term in place of the level-1 term, which breaks the URL and results in a 404 page not found error:

Level-1 term: http://siteurl.com/docLibrary  (correct)

Level-2 term: http://siteurl.com/category1/category1  (incorrect - 404 page not found)

 

So, for reasons I can't explain, my level-1 term is dropped and the Level-2 term is duplicated on the Modern pages, but works fine on the classic pages. The fact that it works fine on classic pages but not on modern pages propted me to post it on this forum.

 

Thanks!

Hi,

Today the top link bar (global navigation) is gone on modern experience page.

We have a site collection with a lot of classic team sites. Publishing feature activated on this site collection, and a few subsites.

Some sites use classic page, and some sites use modern page -> with this one, the top link bar is gone.

I'm not the only one : https://techcommunity.microsoft.com/t5/SharePoint/Anybody-else-s-top-link-bar-in-Modern-experience-d...

 

There is a regression with the last update ?

Thanks

 

 

We are migrating a business unit to iPads and we need to step up our mobile game. Using the SharePoint App, I am only seeing the menu "hamburger" on Group-connected sites. For our classic sites, where we have implemented modern site pages to be mobile-friendly, we are not getting any menus showing on the device, making navigation non-existent. This is a particular issue with our Intranet Home Site which is a classic Publishing Infrastructure enabled site with the drop down menus.

How do I get menus to show up using the SharePoint App for these type of sites?

 

Hi Roland... would you be able to provide a screenshot of what you are seeing?

 

Thanks

Nate (from the SP Mobile team)

@Nate Clinton sure, I have attached desktop versus SharePoint App. Neither the Quick Launch nor Top Bar show up.  

 

 

HP_Desktop.pngHP_IOS.PNG

Super helpful Roland, thanks.  I'm running this down with my team now.  Hoping to circle back after the new year at the latest).  

 

Thanks!
Nate

Hi,

I've reached the structure of my solution where I created a Classic team site, added publishing features and added metadata navigation on my left nav. Problem is that it's expanded by default. It's not so user friendly and now we only have about 20 pages but once the application is done it will be hundreds.The default setting should be collapsed.

And trimming it down is no use, it's for a Customer in the public sector.

 

 

Wasn't aware you can have so many subcategories, how did you achieve that? I am only able to get one subcategory.

And yes fully agree, as have many others here, default setting should be collapsed or it's state manageable.

It's managed meta data, baby! What can't we do with that? Up to seven levels, allthough I think you are having issues if you need that many...

ha, and I thought you had some other trick up your sleeve :) Thanks

Hi @Deleted / @Philine von Guretzky - thanks for the feedback. Yes, we're looking to amend the navigation to be default collapsed (and consistent w/ the documents and pages libraries). 

OMG. I logged in today and <this might be the proudes moment in my SharePoint career> It -was - fixed. I have never had this impact on SharePoint Before. I'm gonna call my mom.
Great to see the quick launch collapsed by default!
However...
When I follow a link, say from a hero web part on the homepage, the page loads but the navigation does not change - it stays collapsed. Hence I am not clear where the page is located and what else it might refer to. Is this a bug or by default?
Related Conversations
Tabs and Dark Mode
cjc2112 in Discussions on
46 Replies
Extentions Synchronization
Deleted in Discussions on
3 Replies
Stable version of Edge insider browser
HotCakeX in Discussions on
35 Replies
flashing a white screen while open new tab
Deleted in Discussions on
14 Replies
How to Prevent Teams from Auto-Launch
chenrylee in Microsoft Teams on
30 Replies
Security Community Webinars
Valon_Kolica in Security, Privacy & Compliance on
13 Replies