web-bugs
web-bugs copied to clipboard
webcompat
radiolippe.de - design is broken
URL: http://radiolippe.de
Browser / Version: Since Firefox 50 Operating System: Android Tested Another Browser: Yes Chrome
Problem type: Design is broken Description: Items are misaligned Steps to Reproduce: First element on page is not scaled correctly. Other Android browers (plural!) show the page as it is supposed to look.
View the screenshot
Browser Configuration
- None
From webcompat.com with ❤️
@wehkah We appreciate your report. I was not able to reproduce the issue. The page loads as expected, with no issues encountered:
Tested with:
Browser / Version: Firefox Release 100.3.0 (2015881499-🦎100.0.2-20220519220738 )/ Firefox Nightly 102.0a1 (2015881995-🦎102.0a1-20220522094633🦎 Operating System: Samsung A51 (Android 11) -1080 × 2400 pixels 20:9 aspect ratio (~405 ppi density) Operating System: Google Pixel 3 (Android 12) -1080 x 2160 pixels, 18:9 ratio (~443 ppi density)
Suggestion: Try clearing cache/data/cookies, disabling add-ons and Ad-blocker (if available) and extensions or use a clean profile, and check again? If there are any changes made to the default settings of the browser (e.g. in about: config) please revert to the default settings and try again. Also, have the required cookies been accepted for this page?
[qa_21/2022]
I have three Android devices running here: an old Samsung phone running LOS 14.1, a slightly more modern Samsung tablet running LOS 16, and my Pixel 4 running LOS 19. They all behave the same: Firefox renders the page totally misaligned, as shown in the screen shot, but opening the same page in a different browser the page is displayed correctly.
On each device I also created a second user and installed Firefox again, without any add on, but the result didn't change.
On each device there's a different second browser, one is called Dolphin, I think, one is simply called "Browser" (doesn't reveal any more information), and one is called "Via". They all render the page correctly.
To be honest: this buggy behaviour has been annoying me for years now, and if you don't get to see it, then it has to be a very old and long lived bug in LineageOS. But is that possible? Can a bug in the OS affect just one specific browser?
Suggestion: Try clearing cache/data/cookies, disabling add-ons and Ad-blocker (if available) and extensions or use a clean profile, and check again?
Been there, done that!
(e.g. in about: config)
That URL does not work in FF on Android any more!
@wehkah The about:config: works in all android devices:
Possibly the extra space added in my comment messes with the URL. Sorry about that. Could you please check and see if the defaults settings of the browser have been altered?
I have a feeling that this might be device-dependent. But before that, may I ask what version of Firefox are you running at the moment?
[inv_21/2022]
The
about:config: works in all android devices:
Sorry to contradict, but it does not! If you search the internet for the terms
android firefox "about:config"
you will find many complains from users who are missing this possibility to change settings. When I try that URL, I see only a blank page. And yes: I took care of the extra space and I deactivated all addons before!
In your comment above you say that you're using "Firefox Nightly". You can not compare your settings with the rest of all the users. I've found articles on the internet stating that this special URL is only available in those nightly version. I can't testify this statements, because I'm only using packages that are installable via Google Play Store. I don't install any packages directly from third sources.
I have a feeling that this might be device-dependent
That is not the case, see my second comment.
@wehkah In your report, it says from Firefox 50 upwards. As some users are using older versions of Firefox, when situations like these arrises (we are not given a version on which the issue occurs), we test the issue on the latest build of Firefox Nightly. This is our guideline. For this project, we perform testing on Firefox Nightly's latest version. I can confirm that about:config does not work on the latest build of Firefox Release, at it is a known issue that this works only on the Beta versions and Nightly version.
I was referring that this might be device depend based on the display of the devices. If I could have that information, that would be awesome, as some rendering is affected by the size of the screen of the devices, pixels and DPi (since you are able to reproduce it on more than one device, there might be a link there) - so as seen in my previous comment about the display info of my devices. For me, the rendering is correct on both the Release version and the Nightly version, on multiple devices
[inv_21/2022]
In your report, it says from Firefox 50 upwards.
I meant: ever since around that version. I can not remember the exact date and FF version, but I also can not remember any FF version I ever used on Android that did render this (and some other pages) correctly.
As some users are using older versions of Firefox,
Like I said: I am using FF 100 now, the latest one available on Google Play Store.
I was referring that this might be device depend based on the display of the devices.
Again: this faulty rendering happens on all of my devices, see my second article in this thread. It would be a very, very strange coincident, if a resolution dependent mistake is causing this. Two of my devices are by the same manufacturer, but that is the only thing those three devices have in common, concerning the hardware. The other thing all 3 have in common is the OS: they all run on LineageOS, different versions, of course, due to they age. See my statement here.
It would be nice if someone else running LOS on their device could comment on this issue. If this faulty rendering does not happen on your device, it can only lead to three conclusions, I think:
- The nightly and the release version of FF behave differently.
- There's been a bug LOS since (at least) version 14, that only effects FF regardless of its version, but no other browser.
- The owner of the misaligned site knows me and my devices and hates me enough to deliver faulty pages to me only!
Actually, I don't know on which possibility I should bet my money...
One more information I can provide: after the page has been loaded (misaligned), I can squeeze it, so it fits the screen and everything is readable. But, of cause, after every change to another sub-page I have to do this again. And this behaviour is also common on all of my devices.
@denschub Anyone on our team that might have a similar device running LOS?
[inv_21/2022]
I've also checked on all my devices, but could not reproduce.
Tested with: Browser / Version: Firefox Nightly 103.0a1 (🦎 103.0a1-20220531065724) Operating System: Google Pixel 5 (Android 12) - 1080 x 2340 pixels, 19.5:9 ratio (~432 ppi density), Samsung Galaxy S8 (Android 9) - 1440 x 2960 pixels, 18.5:9 ratio (~570 ppi density), Samsung Galaxy S6 (Android 7.0) - 1440 x 2560 pixels (~577 ppi pixel density)
[inv_22/2022]
No one running LOS has tested this page yet?
In the meantime, I installed Android in a VirtualBox (the x86 Version), downloaded the same FF version from PlayStore and the page is loading correctly there.
One more interesting fact: "radiolippe" is part of the private/commercial radio group "radio nrw". If you go to radionrw.de/nrw-lokalradios/sendegebiet.html and click on the map, and visit the associated local radio stations, you can see that not all of those pages load misaligned. Only those stations that use the big logo saying "radio" and the local station's name beneath it, misbehave.
Could this be a clue?
Supplement:
On a Chromebook, with FF installed from PlayStore (thus: same Android Version), the page is also rendered correctly!
@wehkah We are still trying to replicate the environment in which the issue has occurred, but because a custom ROM build is needed for our devices in order to have this OS, this might present an issue, since our devices are company-owned.
[inv_23/2022]
@wehkah We are still unable to replicate the test environment, due to the OS used.
[inv_33/2022]
This works fine for me in all current Firefox release trains on LineageOS 19.1. This probably isn't related to the operating system, but rather something device-specific. Unfortunately, WebCompat isn't the right place to investigate that, we lack a broad range of devices and knowledge about possible edge-cases.
Can you please report this in Firefox for Android's bugtracker at https://github.com/mozilla-mobile/fenix/issues/new/choose, explicitly mention that WebCompat people sent you? They can help digging into that, and maybe figure out why it's breaking in your specific case!
