搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

Updated to Firefox 73 and now £ symbol displays as Ł on our Database

  • 3 回覆
  • 2 有這個問題
  • 2 次檢視
  • 最近回覆由 Tom Jelfs

more options

Firefox updated to version 73 the other day and now my php/mysql database system that I built displays Ł symbol inplace of the £ symbol. This is an old Database that sits on an in house PC and we connect via a browser over LAN.

Anyone else getting this problem? Tested other sites and it works on places like Amazon, Ebay etc

It displays fine using Chrome.

Firefox updated to version 73 the other day and now my php/mysql database system that I built displays Ł symbol inplace of the £ symbol. This is an old Database that sits on an in house PC and we connect via a browser over LAN. Anyone else getting this problem? Tested other sites and it works on places like Amazon, Ebay etc It displays fine using Chrome.

所有回覆 (3)

more options

Did you check what font is used ?

It is possible that Firefox uses a font that doesn't have this glyph.

You can right-click and select "Inspect Element" to open the builtin Inspector with this element selected.

You can check in the Rules tab in the right panel in the Inspector what font-family is used for selected text. You can check in the Font tab in the right panel in the Inspector what font is actually used because Firefox might be using a different font than specified by the website.

more options

The font used is Arial.

more options

cor-el said

Did you check what font is used ? It is possible that Firefox uses a font that doesn't have this glyph. You can right-click and select "Inspect Element" to open the builtin Inspector with this element selected. You can check in the Rules tab in the right panel in the Inspector what font-family is used for selected text. You can check in the Font tab in the right panel in the Inspector what font is actually used because Firefox might be using a different font than specified by the website.

Font is Arial. Any ideas? Is it likely my website/database is the cause? As I say Chrome does not have a problem with it.