Bugzilla

Thanks. That's odd/interesting that it's reproducing in a device-specific way.

For what it's worth, I tested every Oppo phone model that BrowserStack has available for me to test (A78, A96, Reno 8T 5G, Reno 6, Reno 3 Pro), and I wasn't able to reproduce this on any of them. (Tested using Firefox-that-BrowserStack-has-installed which is v127.0.2; and I tested with ETP at both standard and off.)

Looking at the screenshots of the broken rendering: it looks like ad container element (the element with a gray-background and a black bottom and top border) is ending up too short, and the ad is then overflowing onto the content that follows it.

I don't immediately see how that would happen except via a site bug where they're occasionally adding a different set of CSS classes or styles to that element or something. Locally for me, that element looks like this:
```html
<div class="pp_ad-fullwidth pp_ad-mob">
```
and those classes give it these styles -- note the explicit `height: 304px` in particular:
```css
element {
}
.pp_ad-fullwidth.pp_ad-mob {
[ ...]
  height: 304px;
  width: 100%;
  border-top-width: 1px;
  border-bottom-width: 1px;
  padding-bottom: 12px;
```

If I locally add `max-height:10px` to that element (or similar), then I can end up with a rendering that's similar to the broken screenshots that Raul's posted. So I wonder if there's some condition where the site is inadvertently doing something along those lines.

Raul: since I can't repro locally on any of the phones I've tested (including the Oppo ones I've got access to), I've got two last ideas for how to reason a little bit about what might be going wrong:
(1) could you attach a screencast showing a broken pageload in its entirety?  It'd be helpful to be able to see how this^ container element appears as the page loads.

(2) If it's not too much trouble, it'd be great to capture a performance profile with the bad pageload, which might have some clues.  You can do that by [tapping the about-firefox-logo to enable debug menu](https://firefox-source-docs.mozilla.org/mobile/android/fenix/Secret-settings-debug-menu-instructions.html) and then scroll to the very bottom of settings and tap "start profiler", and accept the default Firefox profiler-settings-preset.  Then, trigger a bad pageload (or a few), and then return to Firefox settings and tap "Stop profiler" (at the very bottom), and then tap "Upload Profile", and then paste the profile URL (which ends up in your clipboard) here.  Thanks!

Thanks. That's odd/interesting that it's reproducing in a device-specific way.

For what it's worth, I tested every Oppo phone model that BrowserStack has available for me to test (A78, A96, Reno 8T 5G, Reno 6, Reno 3 Pro), and I wasn't able to reproduce this on any of them. (Tested using Firefox-that-BrowserStack-has-installed which is v127.0.2; and I tested with ETP at both standard and off.)

Looking at the screenshots of the broken rendering in e.g. comment 3: it looks like ad container element (the element with a gray-background and a black bottom and top border) is ending up too short, and the ad is then overflowing onto the content that follows it.

I don't immediately see how that would happen except via a site bug where they're occasionally adding a different set of CSS classes or styles to that element or something. Locally for me, that element looks like this:
```html
<div class="pp_ad-fullwidth pp_ad-mob">
```
...and those classes give it these styles -- note the explicit `height: 304px` in particular which should make this element plenty tall for the sorts of ads that I'm seeing there:
```css
element {
}
.pp_ad-fullwidth.pp_ad-mob {
[ ...]
  height: 304px;
  width: 100%;
  border-top-width: 1px;
  border-bottom-width: 1px;
  padding-bottom: 12px;
```

If I locally add `max-height:10px` to that element (or similar), then I can end up with a rendering that's similar to the broken screenshots that Raul's posted. So I wonder if there's some condition where the site is inadvertently doing something along those lines.

Raul: since I can't repro locally on any of the phones I've tested (including the Oppo ones I've got access to), I've got two last ideas for how to reason a little bit about what might be going wrong:
(1) could you attach a screencast showing a broken pageload in its entirety?  It'd be helpful to be able to see how this^ container element appears as the page loads.

(2) If it's not too much trouble, it'd be great to capture a performance profile with the bad pageload, which might have some clues.  You can do that by [tapping the about-firefox-logo to enable debug menu](https://firefox-source-docs.mozilla.org/mobile/android/fenix/Secret-settings-debug-menu-instructions.html) and then scroll to the very bottom of settings and tap "start profiler", and accept the default Firefox profiler-settings-preset.  Then, trigger a bad pageload (or a few), and then return to Firefox settings and tap "Stop profiler" (at the very bottom), and then tap "Upload Profile", and then paste the profile URL (which ends up in your clipboard) here.  Thanks!