<?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: Ancestry with Firefox vs Chrome in Discussions</title>
    <link>https://connect.mozilla.org/t5/discussions/ancestry-with-firefox-vs-chrome/m-p/77809#M29683</link>
    <description>&lt;P&gt;Thank you for reaching out!&lt;/P&gt;
&lt;P&gt;This sounds like a web compatibility bug. Can you please file a report on&amp;nbsp;&lt;A href="https://webcompat.com/" target="_blank"&gt;https://webcompat.com/&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;We are regularly triaging reports coming through this site.&lt;/P&gt;
&lt;P&gt;Thank you!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 12 Nov 2024 09:11:05 GMT</pubDate>
    <dc:creator>Honza</dc:creator>
    <dc:date>2024-11-12T09:11:05Z</dc:date>
    <item>
      <title>Ancestry with Firefox vs Chrome</title>
      <link>https://connect.mozilla.org/t5/discussions/ancestry-with-firefox-vs-chrome/m-p/77628#M29635</link>
      <description>&lt;P&gt;I do not like using the Chrome browser but have been forced to do so while on the Ancestry site. Maybe there is a fix for this I am unaware, consistently Ancestry run by Firefox will say the site is having technical difficulties and asked to be refreshed. Chrome running Ancestry does not have this issue.&lt;/P&gt;</description>
      <pubDate>Sun, 10 Nov 2024 17:43:09 GMT</pubDate>
      <guid>https://connect.mozilla.org/t5/discussions/ancestry-with-firefox-vs-chrome/m-p/77628#M29635</guid>
      <dc:creator>dms2024</dc:creator>
      <dc:date>2024-11-10T17:43:09Z</dc:date>
    </item>
    <item>
      <title>Re: Ancestry with Firefox vs Chrome</title>
      <link>https://connect.mozilla.org/t5/discussions/ancestry-with-firefox-vs-chrome/m-p/77656#M29636</link>
      <description>&lt;P&gt;I'm a newbie here, so feel free to ignore this, but I had similar problems with the Ancestry site. Clearing cookies and the cache helped stopped that a lot (but not completely). I clear them when closing anyway.&lt;/P&gt;</description>
      <pubDate>Sun, 10 Nov 2024 19:30:47 GMT</pubDate>
      <guid>https://connect.mozilla.org/t5/discussions/ancestry-with-firefox-vs-chrome/m-p/77656#M29636</guid>
      <dc:creator>horsedata</dc:creator>
      <dc:date>2024-11-10T19:30:47Z</dc:date>
    </item>
    <item>
      <title>Re: Ancestry with Firefox vs Chrome</title>
      <link>https://connect.mozilla.org/t5/discussions/ancestry-with-firefox-vs-chrome/m-p/77809#M29683</link>
      <description>&lt;P&gt;Thank you for reaching out!&lt;/P&gt;
&lt;P&gt;This sounds like a web compatibility bug. Can you please file a report on&amp;nbsp;&lt;A href="https://webcompat.com/" target="_blank"&gt;https://webcompat.com/&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;We are regularly triaging reports coming through this site.&lt;/P&gt;
&lt;P&gt;Thank you!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Nov 2024 09:11:05 GMT</pubDate>
      <guid>https://connect.mozilla.org/t5/discussions/ancestry-with-firefox-vs-chrome/m-p/77809#M29683</guid>
      <dc:creator>Honza</dc:creator>
      <dc:date>2024-11-12T09:11:05Z</dc:date>
    </item>
  </channel>
</rss>

