Closed Bug 1897995 Opened 6 months ago Closed 4 months ago

on https://in.investing.com/charts/live-charts, the charts appear to be completely blank

Categories

(Core :: Layout: Tables, defect)

defect

Tracking

()

VERIFIED FIXED
130 Branch
Tracking Status
firefox-esr115 --- unaffected
firefox-esr128 --- disabled
firefox126 --- disabled
firefox127 --- disabled
firefox128 --- disabled
firefox129 --- disabled
firefox130 --- verified

People

(Reporter: alice0775, Unassigned)

References

(Blocks 1 open bug, Regression)

Details

(Keywords: regression)

This is clone of Bug 1897395 comment#2

STR:
1 Open https://in.investing.com/charts/live-charts (no need logged in)

AR:
the charts appear to be completely blank

Regression window:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=14d68154a5bee022c96b908cfcf492dcb4f7f085&tochange=7cdb37e233eb8ff913e8aa2214f90659a7e261c3

NOTE,
However, I cannot reproduce the issue on Firefox126.0 and 127.0b4.
So, this seems to be nightly build only issue. Setting layout.tables.scrollable-cells to false fixes the issue on Nightly128.0a1.

:emilio, since you are the author of the regressor, bug 1880550, could you take a look? Also, could you set the severity field?

For more information, please visit BugBot documentation.

Flags: needinfo?(emilio)
Depends on: 1883699
Flags: needinfo?(emilio)

(In reply to Alice0775 White from comment #0)

So, this seems to be nightly build only issue. Setting layout.tables.scrollable-cells to false fixes the issue on Nightly128.0a1.

Just for release-management purposes: note that the relevant pref here, layout.tables.scrollable-cells, is default-false on release/beta for now (as of bug 1877719), until we make a decision to change that.

So: even though this is a regression on Nightly, we don't need to worry about this regression riding the trains to release.

The severity field is not set for this bug.
:jfkthame, could you have a look please?

For more information, please visit BugBot documentation.

Flags: needinfo?(jfkthame)

Severity is tricky here; if this were on the way to release, it'd be clearly s2, but given that we have this behind a pref, let's say s3.

In any case, we'll need to fix this before the pref rides the trains.

Severity: -- → S3
Flags: needinfo?(jfkthame)

Set release status flags based on info from the regressing bug 1880550

Is there a bug this should be blocking, related to the pref riding the trains?

Flags: needinfo?(dholbert)

(In reply to Liz Henry (:lizzard) (relman/hg->git project) from comment #6)

Is there a bug this should be blocking, related to the pref riding the trains?

There is now; I've just filed bug 1904159 to cover this.

Flags: needinfo?(dholbert)

(In reply to Daniel Holbert [:dholbert] from comment #4)

Severity is tricky here; if this were on the way to release, it'd be clearly s2, but given that we have this behind a pref, let's say s3.

In any case, we'll need to fix this before the pref rides the trains.

Update: we turned off the pref for Nightly as well (bug 1877719 comment 20 - 22), so this now doesn't reproduce on any of our release channels by default, and I think we can consider this bug FIXED by that change (just as we considered the similar YouTube issue in bug 1877719 to be fixed by that change).

I'll add a note on the relevant bugs tracking the pref-reenabling to be sure we don't regress this at that point.

Status: NEW → RESOLVED
Closed: 4 months ago
Resolution: --- → FIXED
Target Milestone: --- → 130 Branch
Depends on: 1877719
No longer depends on: 1883699
See Also: → 1883699
Flags: qe-verify+

I was able to reproduce the issue on an affected Firefox Nightly build from 2024-05-21 on Windows 11, while following the steps described in Comment 0.
Verified as fixed using Firefox 130.0b5 and also the latest 131.0a1 Nightly, on Windows 11, MacOS 14.4 and Ubuntu 22.04. The chart from https://in.investing.com/charts/live-charts is no longer blank and the layout.tables.scrollable-cells pref is set to false by default.

Status: RESOLVED → VERIFIED
Flags: qe-verify+
You need to log in before you can comment on or make changes to this bug.