Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Lolu chungechunge lwabekwa kunqolobane. Uyacelwa ubuze umbuzo omusha uma udinga usizo.

Why does Firefox erroneously truncate my HTML?

  • 3 uphendule
  • 1 inale nkinga
  • 12 views
  • Igcine ukuphendulwa ngu cor-el

more options

I'm trying to add and provide access to specific in-page anchors. I first added a link to the destination page (see "Here is the code I entered first:" below). Then I added the specific anchor (#Vespoli_Single). When I save the HTML, the page portion of the href ("/Classified")disappeared and only the #Vespoli_Single remained. I assumed it was the fault of the editor, but...

To try to diagnose the problem, I did the following:
(1) Cleared the browser cache on my PC and tried again. Same problem.
(2) Used Firefox on a MacAir. Same problem.
(3) Used Safari on a MacAir. NO problem!
(4) Used IE on my PC. NO problem!

That makes Firefox look like the problem.

Here is the code I entered first (and saved my work):

<p>For sale: <a href="/Classified_Ads">Vespoli Single $2000</a></p>

Then I added the specific anchor name and saved my work:

<p>For sale: <a href="/Classified_Ads#Vespoli_Single">Vespoli Single $2000</a></p>

After saving, the result was:

<p>For sale: <a href="#Vespoli_Single">Vespoli Single $2000</a></p>

Note that the page reference disappeared and only the specific anchor remained

Does anyone have *any* idea what's happening? This is a new problem, as I've successfully used specific anchors in href statements in the past.

I'm trying to add and provide access to specific in-page anchors. I first added a link to the destination page (see "Here is the code I entered first:" below). Then I added the specific anchor (#Vespoli_Single). When I save the HTML, the page portion of the href ("/Classified")disappeared and only the #Vespoli_Single remained. I assumed it was the fault of the editor, but... To try to diagnose the problem, I did the following:<br /> (1) Cleared the browser cache on my PC and tried again. Same problem.<br /> (2) Used Firefox on a MacAir. Same problem.<br /> (3) Used Safari on a MacAir. NO problem!<br /> (4) Used IE on my PC. NO problem! That makes Firefox look like the problem. Here is the code I entered first (and saved my work): <pre><nowiki><p>For sale: <a href="/Classified_Ads">Vespoli Single $2000</a></p></nowiki></pre> Then I added the specific anchor name and saved my work: <pre><nowiki><p>For sale: <a href="/Classified_Ads#Vespoli_Single">Vespoli Single $2000</a></p></nowiki></pre> After saving, the result was: <pre><nowiki><p>For sale: <a href="#Vespoli_Single">Vespoli Single $2000</a></p></nowiki></pre> Note that the page reference disappeared and only the specific anchor remained Does anyone have *any* idea what's happening? This is a new problem, as I've successfully used specific anchors in href statements in the past.

Okulungisiwe ngu cor-el

Isisombululo esikhethiwe

Yes, that should normally be sufficient.
A reload and bypass the cache also sends a specific header that a cached version shouldn't be used.
If the new code is uploaded correctly and it works in other browsers then the old page may still be cached somewhere if Firefox is still displaying this previous copy.

Funda le mpendulo ngokuhambisana nalesi sihloko 👍 0

All Replies (3)

more options

Firefox or another server may still have an older version of the page in the cache.

Reload web page(s) and bypass the cache to refresh possibly outdated or corrupted files.

  • Hold down the Shift key and left-click the Reload button
  • Press "Ctrl + F5" or press "Ctrl + Shift + R" (Windows,Linux)
  • Press "Command + Shift + R" (Mac)
more options

Note that the first correction I tried was to clear the cache. Wouldn't that eliminate any older version of the page?

more options

Isisombululo Esikhethiwe

Yes, that should normally be sufficient.
A reload and bypass the cache also sends a specific header that a cached version shouldn't be used.
If the new code is uploaded correctly and it works in other browsers then the old page may still be cached somewhere if Firefox is still displaying this previous copy.