Closed Bug 1557383 Opened 5 years ago Closed 5 years ago

Reftest 404149-1.xul fails when loaded with system privilege

Categories

(Core :: Layout: Text and Fonts, defect)

defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1557371

People

(Reporter: bdahl, Unassigned)

References

Details

Over in bug 1557371, where I start loading all XUL pages with chrome privilege this test start perma-failing. Bug 602469 also suggests this tests may not actually be testing what it should be anymore.

Do you have a Try run with the test failure that we can take a look at?

Flags: needinfo?(bdahl)

Thanks. Here's a "prettified" log from that run (with all the bonus links/buttons/etc):
https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=250265060&repo=try

Reftest-analyzer:
https://hg.mozilla.org/mozilla-central/raw-file/tip/layout/tools/reftest/reftest-analyzer.xhtml#logurl=https://queue.taskcluster.net/v1/task/SadZ0tmmRGy5rSa5AA96yA/runs/0/artifacts/public/logs/live_backing.log&only_show_unexpected=1

Just for the record, in case that log expires: it looks like the testcase renders a "فا" character with a sort of "]" shape around it, whereas the reference case only shows the right edge of the "]" shape (at a more-to-the-left position). Or something like that.

I don't know what the correct rendering actually is, nor am I sure whether the testcase or the reference case (or both) is the one whose rendering is changed by the chrome-privilege change here.

The priority flag is not set for this bug.
:dholbert, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(dholbert)

Right now, it sounds like this is just due to a packaging mistake in bug 1557371 (needing to get the fonts packaged), as suggested in the phabricator comment that dbaron pointed to.

This should probably just be addressed in bug 1557371 itself, so I'll just dupe this back over to that bug.

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