Working with FF 124 on Archlinux
Web Development
Welcome to the web development community! This is a place to post, discuss, get help about, etc. anything related to web development
What is web development?
Web development is the process of creating websites or web applications
Rules/Guidelines
- Follow the programming.dev site rules
- Keep content related to web development
- If what you're posting relates to one of the related communities, crosspost it into there to help them grow
- If youre posting an article older than two years put the year it was made in brackets after the title
Related Communities
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
Wormhole
Some webdev blogs
Not sure what to post in here? Want some web development related things to read?
Heres a couple blogs that have web development related content
- https://frontendfoc.us/ - [RSS]
- https://wesbos.com/blog
- https://davidwalsh.name/ - [RSS]
- https://www.nngroup.com/articles/
- https://sia.codes/posts/ - [RSS]
- https://www.smashingmagazine.com/ - [RSS]
- https://www.bennadel.com/ - [RSS]
- https://web.dev/ - [RSS]
Working with FF 124 on Android.
as i have already mentioned,This issue doesn't occur with any mobile device Browsers.
Ah, I just tested once I read that section. Why read further was my thinking. Now I have not tested it on PC... Sorry
no problem
FF124, Windows; What I see is grey and a loading icon.
Have you opened the Browser Console?
downloadable font: Glyph bbox was incorrect
While one would not expect that to cause such issues, depending on if you're using a SPA or what kind of bootstrapping you use, or a Firefox consequential issue, it may. What happens if you skip web fonts?
I can open the browser console, and I can context menu inspect elements, and it selects them in the inspector. So it seems like the DOM is being rendered and laid out, to an interactable level.
When I open CTRL+SHIFT+M it looks very funky and broken. No border, nothing rendered; only the resize handle, which remains usable. Using different Window to compare, there should be a border and border shadow. This makes me come back to the font issue, and makes me wonder if trying to render a faulty font brings Firefox into a broken render state.
FWIW, it's working with FF 123 on Kubuntu as well.