1270407 - Security Error: Content at about:home may not load or link to about:rights.

Status: RESOLVED WORKSFORME

(Firefox :: Menus, defect)

Description

[Liu Xing]

Attachment: aboutlicense.png

about:license and about:rights can not click on Firefox Developer Edition.

Comment 1

[Hector Zhao [:hectorz]]

Error message in console: "Security Error: Content at moz-nullprincipal:{uuid} may not load or link to about:license."

Comment 2

[Liu Xing]

It is in the about menu.

Comment 3

[Liu Xing]

(In reply to Hector Zhao [:hectorz] from comment #1)
> Error message in console: "Security Error: Content at
> moz-nullprincipal:{uuid} may not load or link to about:license."

How can I see the error message in console?

Comment 4

[Elvin Lee [:ellee] (no longer with Mozilla)]

Confirming this in Dev Edition 48 on both Windows and Mac OS X.

Liu Xing, console can be accessed by Ctrl+SHift+J

Comment 5

[Kamil Jozwiak [:kjozwiak]]

I've ran into the same issue today while using the latest version of m-c on OSX:
* fx50.0a1, buildID: 20160608030219, changeset: f8ad071a6e14

STR:

* install a new instance of m-c/or create a brand new profile
* when m-c is opened, you'll have two tabs opened:
** https://www.mozilla.org/en-US/firefox/nightly/firstrun/
** about:home
* switch into the about:home tab
* click on the "Know your rights…" link

You'll notice that about:rights doesn't open and you'll receive the "Security Error: Content at about:home may not load or link to about:rights." error message in the browser console.

Regression Range:
=================

5:51.53 INFO: Last good revision: ae7413abfa4d3954a6a4ce7c1613a7100f367f9a
5:51.53 INFO: First bad revision: 973dfa15822126c39ea2d98d34ac16643b040243
5:51.53 INFO: Pushlog:
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=ae7413abfa4d3954a6a4ce7c1613a7100f367f9a&tochange=973dfa15822126c39ea2d98d34ac16643b040243

Comment 6

[Liu Xing]

It is OK on Firefox Developer Edition now.
>"version": "49.0a2",
>"buildID": "20160616004032"

Comment 7

[Kamil Jozwiak [:kjozwiak]]

I can still reproduce the case I reported in comment # 5. Created bug # 1280649 to address that test case.