1485282 - Opening about:blank from urlbar does not change content area if a specific addon is installed

Status: RESOLVED DUPLICATE of bug 1465388

(Developer Engagement :: Outreach Request, defect)

Description

[Alice0775 White]

Steps To Reproduce:
1. Start browser with new profile
2. Open about:preferences#home
   and set "Blank Page" for New tabs
3. Install addon https://addons.mozilla.org/en-US/firefox/addon/gesturefy/?src=search

4. Open any webpage
   e.g, https://www.mozilla.org/en-US/firefox/nightly/firstrun/
5. Type about:blank in urlbar and hit Enter key

Actual Results:
Content area remains as previous site

Expected Results:
Content area should be blank

Comment 1

[Alice0775 White]

the problem happens since Firefox55.

Comment 2

[Alice0775 White]

STR:
1. Start browser with new profile
2. Install addon https://addons.mozilla.org/en-US/firefox/addon/gesturefy/?src=search
   Install latest version which is working with the relevant Firefox version.
3. Open any webpage
   e.g, https://www.mozilla.org/en-US/firefox/nightly/firstrun/
4. Type about:blank in urlbar and hit Enter key


Regression Window:
https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=8726e36dafe1c875d86b33b5885f6b9e6d1a5a12&tochange=1b3359583493bf0506c4fe1c81573b8a123413ec


Regressed by: Bug 1322235, Bug 1368102, Bug 1368152


Note: The problem happen regardless of WebExtensions or Legacy Addon.

Comment 3

[Alice0775 White]

Via local build,
Last Good: 417fd0cf65a8
First Bad: 32a3b7c39207

Regressed by : 	32a3b7c39207	Kris Maglione — Bug 1368102: Part 5 - Move static content script matching into C++. r=mixedpuppy,zombie


:kmag,
Your patch seems to cause the problem, can you please look into this?

Comment 4

[Alice0775 White]

Attachment: modified maxVersion so that it will be able to install on Nightly55

Comment 5

[Alice0775 White]

Attachment: avoid signature check and disable autoupdate

Comment 6

[Alice0775 White]

:kmag, I can not understand why you deleted the blocking bug without any explanation.

Anyway, I can reproduce the problem with WebExtensions version on Nightly63.0a1 (and Firefox55.0 with the attached modified one).
And I got same regression window and same culprit changesets.

Comment 7

[David Durst [:ddurst]]

(In reply to Alice0775 White from comment #6)
> :kmag, I can not understand why you deleted the blocking bug without any
> explanation.

In c2, three bugs were identified in the regression window; in removing the other two in , are you saying that you have narrowed it to only be 1368102?

If the blocking is removed, it's because this is not directly tied to that bug. If you're confident on that range, we can investigate starting there, but won't block until something is confirmed.

Comment 8

[Alice0775 White]

I narrowed down the range, See comment#3.

Comment 9

[Alice0775 White]

It seems that only one add-on is affected.
So, It is a waste time to investigate bug.

Comment 10

[David Durst [:ddurst]]

Well, if this only manifests with one extension, then we could reach out to Gesturefy.