🌐 Website Issue | Font icons not displaying properly when using NoScript #1763
Labels
No Label
🔍🤖 Search Engines
approved
dependencies
duplicate
feedback wanted
high priority
I2P
iOS
low priority
OS
Self-contained networks
Social media
stale
streaming
todo
Tor
WIP
wontfix
XMPP
[m]
₿ cryptocurrency
ℹ️ help wanted
↔️ file sharing
⚙️ web extensions
✨ enhancement
❌ software removal
💬 discussion
🤖 Android
🐛 bug
💢 conflicting
📝 correction
🆘 critical
📧 email
🔒 file encryption
📁 file storage
🦊 Firefox
💻 hardware
🌐 hosting
🏠 housekeeping
🔐 password managers
🧰 productivity tools
🔎 research required
🌐 Social News Aggregators
🆕 software suggestion
👥 team chat
🔒 VPN
🌐 website issue
🚫 Windows
👁️ browsers
🖊️ digital notebooks
🗄️ DNS
🗨️ instant messaging (im)
🇦🇶 translations
No Milestone
No Assignees
1 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: privacyguides/privacytools.io#1763
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description
One way this could be solved is by introducing a class to problematic font icons called
hideicon
, setting their style to"display:none"
and then using JavaScriptdocument.getElementsByClassName("hideicon").stlyle.display = ";
to revert the display property to the CSS default value.This mostly solves the issues with the navigation bar (excluding home button) but other sections like the "Spread the word and help your friends" at the bottom of the page will have to be tweaked differently as the icons are the only thing there. Perhaps a similar approach as above but instead of just hiding the icon, a fallback logo image would be shown in the opposite way that was described above.
Screenshots
It works okay for me, are you using No Script?
This does seem to be caused by NoScript exclusively and not TB Safest, weird. I thought that Safest implies NoScript being enabled.
We are not currently interested in fixing this issue. If you have browser-side extensions that break compatibility with the websites you visit, those are use-cases that we can not prepare for. Your alternative solution would break icons for all users with Javascript disabled, which is not ideal.