<?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 The aggressive auto-refresh on New Tab recommendations makes absolutely no sense. in Firefox Labs</title>
    <link>https://connect.mozilla.org/t5/firefox-labs/the-aggressive-auto-refresh-on-new-tab-recommendations-makes/m-p/145079#M5392</link>
    <description>&lt;DIV class=""&gt;I am writing to express my profound confusion regarding the design logic behind the Firefox New Tab page.&lt;/DIV&gt;&lt;DIV class=""&gt;Currently, every single time a new tab is opened, the recommended articles feed aggressively refreshes, instantly wiping out whatever was displayed a second prior. I am constantly finding myself in a situation where I spot an interesting headline, open a new tab to click it, and watch it vanish forever because the browser apparently assumes I have the memory of a goldfish.&lt;BR /&gt;&lt;BR /&gt;&lt;/DIV&gt;&lt;DIV class=""&gt;Did anyone at Mozilla stop to consider the basic user workflow before pushing this live? A feed that refreshes so rapidly that users cannot even click the content being recommended is fundamentally broken. It feels like the Pocket development team prioritized desperate engagement metrics over basic human intuition, creating a system that aggressively hides the very content it is supposed to be promoting. It completely defeats the purpose of having recommendations in the first place, serving only to frustrate your users.&lt;BR /&gt;&lt;BR /&gt;I can't figure out which design team is more incompetent... Mozilla's or Pocket's.&amp;nbsp; You both seem pretty inept with this type of stuff.&amp;nbsp; Does anyone even use these products on your payroll?&amp;nbsp; Anyone competent?&lt;/DIV&gt;&lt;DIV class=""&gt;&lt;BR /&gt;Please implement a state-saving mechanism, a "back" button for rotated stories, or at the very least, stop forcing a hard refresh on every single instance of a new tab. As it stands, this feels less like a thoughtful feature and more like a poorly tested oversight.&lt;BR /&gt;&lt;BR /&gt;Disrespectfully yours,&lt;BR /&gt;&lt;BR /&gt;Someone who actually uses your products.&lt;/DIV&gt;</description>
    <pubDate>Tue, 27 Oct 2026 21:50:19 GMT</pubDate>
    <dc:creator>no_excuses</dc:creator>
    <dc:date>2026-10-27T21:50:19Z</dc:date>
    <item>
      <title>The aggressive auto-refresh on New Tab recommendations makes absolutely no sense.</title>
      <link>https://connect.mozilla.org/t5/firefox-labs/the-aggressive-auto-refresh-on-new-tab-recommendations-makes/m-p/145079#M5392</link>
      <description>&lt;DIV class=""&gt;I am writing to express my profound confusion regarding the design logic behind the Firefox New Tab page.&lt;/DIV&gt;&lt;DIV class=""&gt;Currently, every single time a new tab is opened, the recommended articles feed aggressively refreshes, instantly wiping out whatever was displayed a second prior. I am constantly finding myself in a situation where I spot an interesting headline, open a new tab to click it, and watch it vanish forever because the browser apparently assumes I have the memory of a goldfish.&lt;BR /&gt;&lt;BR /&gt;&lt;/DIV&gt;&lt;DIV class=""&gt;Did anyone at Mozilla stop to consider the basic user workflow before pushing this live? A feed that refreshes so rapidly that users cannot even click the content being recommended is fundamentally broken. It feels like the Pocket development team prioritized desperate engagement metrics over basic human intuition, creating a system that aggressively hides the very content it is supposed to be promoting. It completely defeats the purpose of having recommendations in the first place, serving only to frustrate your users.&lt;BR /&gt;&lt;BR /&gt;I can't figure out which design team is more incompetent... Mozilla's or Pocket's.&amp;nbsp; You both seem pretty inept with this type of stuff.&amp;nbsp; Does anyone even use these products on your payroll?&amp;nbsp; Anyone competent?&lt;/DIV&gt;&lt;DIV class=""&gt;&lt;BR /&gt;Please implement a state-saving mechanism, a "back" button for rotated stories, or at the very least, stop forcing a hard refresh on every single instance of a new tab. As it stands, this feels less like a thoughtful feature and more like a poorly tested oversight.&lt;BR /&gt;&lt;BR /&gt;Disrespectfully yours,&lt;BR /&gt;&lt;BR /&gt;Someone who actually uses your products.&lt;/DIV&gt;</description>
      <pubDate>Tue, 27 Oct 2026 21:50:19 GMT</pubDate>
      <guid>https://connect.mozilla.org/t5/firefox-labs/the-aggressive-auto-refresh-on-new-tab-recommendations-makes/m-p/145079#M5392</guid>
      <dc:creator>no_excuses</dc:creator>
      <dc:date>2026-10-27T21:50:19Z</dc:date>
    </item>
    <item>
      <title>Re: The aggressive auto-refresh on New Tab recommendations makes absolutely no sense.</title>
      <link>https://connect.mozilla.org/t5/firefox-labs/the-aggressive-auto-refresh-on-new-tab-recommendations-makes/m-p/145207#M5393</link>
      <description>&lt;P&gt;I agree, though you could just leave the New Tab page open until you've middle-clicked on all the articles you want, and be sure to click the "..." and then "Dismiss" on ones you've read.&lt;/P&gt;&lt;P&gt;Though for some sites, I find at-least half lead to paywalled articles anyway, so I've just turned the newsfeed off as it often just seems a waste of my time.&lt;/P&gt;</description>
      <pubDate>Wed, 28 Oct 2026 16:38:10 GMT</pubDate>
      <guid>https://connect.mozilla.org/t5/firefox-labs/the-aggressive-auto-refresh-on-new-tab-recommendations-makes/m-p/145207#M5393</guid>
      <dc:creator>dftf</dc:creator>
      <dc:date>2026-10-28T16:38:10Z</dc:date>
    </item>
  </channel>
</rss>

