Closed Bug 1789361 Opened 2 years ago Closed 2 years ago

Glam can't export to JSON after bug 1771423

Categories

(Core :: DOM: File, defect)

Product:
Core
Component:
DOM: File
Type:
defect

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1786128
Tracking Flags:
Tracking Status
firefox-esr91 --- unaffected
firefox-esr102 --- unaffected
firefox104 --- unaffected
firefox105 --- unaffected
firefox106 --- affected

People

(Reporter: valentin, Unassigned)

References

(Regression)

Details

(Keywords: regression)

Yesterday I noticed that Glam's Export to JSON doesn't work anymore:
https://github.com/mozilla/glam/issues/2122

After doing a mozregression I narrowed it down to this range:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=a6e4268924e20f94b4e1e96ed1eb61d1909f8cfd&tochange=c1d1be434427b1d709c490a02a1e8ac0899aba14

Considering this works in other browsers, this seems like a regression.

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

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

For more information, please visit auto_nag documentation.

status-firefox104: --- → unaffected
status-firefox105: --- → unaffected
status-firefox106: --- → affected
status-firefox-esr102: --- → unaffected
status-firefox-esr91: --- → unaffected
Flags: needinfo?(drobertson)

Thanks for the bug report. This looks to be a duplicate of bug 1786128.

Considering this works in other browsers, this seems like a regression.

Definitely a regression :) Working through a fix in D155439, and I think the patch has been backed out of the beta channel.

Flags: needinfo?(drobertson)
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.