<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Scroll bar immersive section Portal vs AGOL in Classic Esri Story Maps Questions</title>
    <link>https://community.esri.com/t5/classic-esri-story-maps-questions/scroll-bar-immersive-section-portal-vs-agol/m-p/755993#M8525</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for clearing that up Owen.&amp;nbsp;&lt;BR /&gt;Thought it might be something like that!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 06 Mar 2019 16:19:00 GMT</pubDate>
    <dc:creator>JustinGleeson1</dc:creator>
    <dc:date>2019-03-06T16:19:00Z</dc:date>
    <item>
      <title>Scroll bar immersive section Portal vs AGOL</title>
      <link>https://community.esri.com/t5/classic-esri-story-maps-questions/scroll-bar-immersive-section-portal-vs-agol/m-p/755991#M8523</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm rebuilding a Cascade Storymap in Portal from scratch which was originally developed in AGOL. We have quite a bit of&amp;nbsp;text and graphics in the immersive section text boxes. This works well in AGOL, the text box will size itself based on the amount of content. In Portal the the box will not resize and scroll bar appears instead. An internal scroll bar in a cascade Storymap does not work.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Am I missing something here or are there fundamental differences between the Portal and AGOL Storymap builders?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any assistance would be greatly appreciated&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG alt="" class="image-1 jive-image j-img-original" src="https://community.esri.com/legacyfs/online/438630_AGOL_PortalCompare-01.png" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 04 Mar 2019 17:23:11 GMT</pubDate>
      <guid>https://community.esri.com/t5/classic-esri-story-maps-questions/scroll-bar-immersive-section-portal-vs-agol/m-p/755991#M8523</guid>
      <dc:creator>JustinGleeson1</dc:creator>
      <dc:date>2019-03-04T17:23:11Z</dc:date>
    </item>
    <item>
      <title>Re: Scroll bar immersive section Portal vs AGOL</title>
      <link>https://community.esri.com/t5/classic-esri-story-maps-questions/scroll-bar-immersive-section-portal-vs-agol/m-p/755992#M8524</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Justin -- The improvement to the way Cascade panels handle longer chunks of content was &lt;A href="https://www.esri.com/arcgis-blog/products/story-maps/sharing-collaboration/tall-panels-in-story-map-cascade/"&gt;added to ArcGIS Online in June 2018&lt;/A&gt;, so that will be available in ArcGIS Enterprise 10.7.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 05 Mar 2019 15:52:32 GMT</pubDate>
      <guid>https://community.esri.com/t5/classic-esri-story-maps-questions/scroll-bar-immersive-section-portal-vs-agol/m-p/755992#M8524</guid>
      <dc:creator>OwenGeo</dc:creator>
      <dc:date>2019-03-05T15:52:32Z</dc:date>
    </item>
    <item>
      <title>Re: Scroll bar immersive section Portal vs AGOL</title>
      <link>https://community.esri.com/t5/classic-esri-story-maps-questions/scroll-bar-immersive-section-portal-vs-agol/m-p/755993#M8525</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for clearing that up Owen.&amp;nbsp;&lt;BR /&gt;Thought it might be something like that!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 06 Mar 2019 16:19:00 GMT</pubDate>
      <guid>https://community.esri.com/t5/classic-esri-story-maps-questions/scroll-bar-immersive-section-portal-vs-agol/m-p/755993#M8525</guid>
      <dc:creator>JustinGleeson1</dc:creator>
      <dc:date>2019-03-06T16:19:00Z</dc:date>
    </item>
  </channel>
</rss>

