Graphical glitch when viewing Network map on Safari
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- frontend
Research direction
Start by reproducing the issue in Safari on the Network page and comparing the map with a working browser. Find the Network map rendering entry point and inspect how device names and diagram lines are positioned. Done means the map and labels display correctly in Safari and the reported iOS/WebKit cases.
Written by the indexing model from the issue text.
Description
Is there an existing issue for this?
- I have searched the existing open and closed issues and I checked the docs https://jokob-sk.github.io/NetAlertX/
The issue occurs in the following browsers. Select at least 2.
- Firefox
- Chrome
- Edge
- Safari (unsupported) - PRs welcome
- N/A - This is an issue with the backend
Current Behavior
Hi,
By the title of Safari's checkbox ("Safari (unsupported) - PRs welcome") when creating this issue, I can understand that this may probably be a known issue, and perhaps, will not be addressed in the long term, but I'll report it anyways.
When going into the "Network" section, when the network map is displayed, using Safari (in this case on macOS) causes that map to be drawn incorrectly, as shown in my screenshot, all the names seem to be going to the top left corner. All the spaces where the names for each device should be displayed are blank.
Some of the details have been omitted for privacy and security reasons.
This also happens on iPhone and iPad, on iPhone (iOS) it looks even worse, since it draws the diagram lines inverted, the names remain the same... All of them displayed at the top left corner of the space where the diagram is displayed. And since Chrome for iOS/iPadOS seems to still be using WebKit, the same happens on Chrome when using any of those OSs.
Screenshot for Safari on iOS (iPhone 16):
Screenshot for Chrome on iOS (WebKit) (iPhone 16):
Again, for both pictures, some of the details have been omitted for privacy and security reasons.
As said previously, I don't have much hopes of this getting fixed anytime soon as for the "unsupported" flag in Safari's checkbox, but still wanted to report this in hopes that this gets addressed in the future and ends up working fine on Safari... For the absolute rest of the functions of NetAlertX, everything seems to be working perfectly fine so far... I've been able to configure every detail of my network from Safari and everything works flawlessly... It's just that Network diagram that is not working for me.
In case this also helps in any way (I doubt it) I'm using NetAlertX on a Docker Container in my UGREEN NAS.
Thanks in advance.
Expected Behavior
When going into the "Network" section, when the network map is displayed, using Safari (in this case on macOS, but also happens in iPadOS and iOS) the map should be displayed correctly. All the names for each device and diagram lines correctly arranged.
Sorry again for the grey blocks in the screenshot above, but I wanted to hide the names for all my devices for privacy and security reasons. I hope you all understand.
Steps To Reproduce
- Setup NetAlertX normally (in my case, using Docker Compose) and configure all (if possible) of your network details for devices to be shown in the network diagram.
- Open Safari on any device... A Mac, an iPhone, an iPad, heck, even an iPod Touch if you would like, the sky is the limit, and obviously go to your NetAlertX local IP address.
- In NetAlertX, go to "Network" in order to admire your network diagram.
- Enjoy.
app.conf
docker-compose.yml
services:
netalertx:
image: jokobsk/netalertx:latest
container_name: netalertx
volumes:
- ./config:/app/config
- ./db:/app/db
environment:
- TZ=Europe/Madrid
network_mode: host
restart: unless-stopped
What installation are you running?
Production (netalertx)
app.log
No response
Debug enabled
- I have read and followed the steps in the wiki link above and provided the required debug logs and the log section covers the time when the issue occurs.
- Dominant language
- Python
- Stars
- 7.2k
- Forks
- 456
- Avg merge
- 17h 59m
- Merged PRs (30d)
- 26
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from netalertx/NetAlertX
-
bug 🐛
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
netalertx/NetAlertX#1856 · 1 comment · 7 reactions ·
Maintainers usually reply within 1 day
-
[Bug] MCP SSE endpoint event omits the /server prefix, so clients behind the built-in nginx proxy get a 404 on /mcp/messagesPossibly taken @frdmn claimed this 2 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Docker 🐋
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
bug 🐛 next release/in dev image 🚀 Waiting for reply⏳
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
netalertx/NetAlertX#1851 · 2 comments ·
Maintainers usually reply within 1 day
-
[Bug] Internet-Check returns 0.0.0.0 when IPv6 is enabled and OpenDNS lookup failsPossibly taken @pujitha24 claimed this 6 days ago. Openbug 🐛 next release/in dev image 🚀 Waiting for reply⏳
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
netalertx/NetAlertX#1845 · 2 comments ·
Maintainers usually reply within 1 day
All issues in netalertx/NetAlertX
Similar issues
-
style: article/section 📝 system: cloud.rc ☁️ system: security 🔐
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
uabrc/uabrc.github.io#1262 ·
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
NCAR/miles-credit#526 ·
-
documentation
Difficulty 1/5 1-3 hours Newbie friendliness 76/100
conda/conda-lock#957 ·
Maintainers usually reply within 1 day
-
Type: Bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
aws-samples/sample-per-model-bedrock#464 ·
Maintainers usually reply within 1 day