Bug 1583479 Comment 6 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

I found the culprit! It was a change in the blocklist, done by the other peer tester. I do not understand why this behaves as such, but this was certainly the cause.

* Initially, I have added the string "pc=U510" and the bug would reproduce (the Bing homepage would be set even if it would already be blocklisted by the "pc=U510" string), but it would get blocked and reverted to default after the first restart.
* Then, the "bing" string (that is contained in the domain of the homepage link) was added to the homepage blocklist as well and after this, the Bing homepage would not be set at all when installing the extension. 
* I had to also try it when only the "bing" string is added to the blocklist and it gives the same result as when both the "pc=U510" and "bing" strings are added together: the bug does not reproduce.

In conclusion, it appears that if the "bing" string is added to the blocklist, it behaves differently than when the "pc=U510" string is added.
The bug is still valid, but there might be another issue being uncovered by this revelation. 

Mark, what do you think?
I found the culprit! It was a change in the blocklist, done by the other peer tester. I do not understand why this behaves as such, but this was certainly the cause.

* Initially, I have added the string "pc=U510" and the bug would reproduce (the Bing homepage would be set even if it would already be blocklisted by the "PC=U510" string), but it would get blocked and reverted to default after the first restart.
* Then, the "bing" string (that is contained in the domain of the homepage link) was added to the homepage blocklist as well and after this, the Bing homepage would not be set at all when installing the extension. 
* I had to also try it when only the "bing" string is added to the blocklist and it gives the same result as when both the "pc=U510" and "bing" strings are added together: the bug does not reproduce.

In conclusion, it appears that if the "bing" string is added to the blocklist, it behaves differently than when the "pc=U510" string is added.
The bug is still valid, but there might be another issue being uncovered by this revelation. 

Mark, what do you think?
I found the culprit! It was a change in the blocklist, done by the other peer tester. I do not understand why this behaves as such, but this was certainly the cause.

* Initially, I have added the string "pc=U510" and the bug would reproduce (the Bing homepage would be set even if it would already be blocklisted by the "PC=U510" string), but it would get blocked and reverted to default after the first restart.
* Then, the "bing" string (that is contained in the domain of the homepage link) was added to the homepage blocklist as well and after this, the Bing homepage would not be set at all when installing the extension. 
* I had to also try it when only the "bing" string is added to the blocklist and it gives the same result as when both the "PC=U510" and "bing" strings are added together: the bug does not reproduce.

In conclusion, it appears that if the "bing" string is added to the blocklist, it behaves differently than when the "PC=U510" string is added.
The bug is still valid, but there might be another issue being uncovered by this revelation. 

Mark, what do you think?
I found the culprit! It was a change in the blocklist, done by the other peer tester. I do not understand why this behaves as such, but this was certainly the cause.

* Initially, I have added the string "PC=U510" and the bug would reproduce (the Bing homepage would be set even if it would already be blocklisted by the "PC=U510" string), but it would get blocked and reverted to default after the first restart.
* Then, the "bing" string (that is contained in the domain of the homepage link) was added to the homepage blocklist as well and after this, the Bing homepage would not be set at all when installing the extension. 
* I had to also try it when only the "bing" string is added to the blocklist and it gives the same result as when both the "PC=U510" and "bing" strings are added together: the bug does not reproduce.

In conclusion, it appears that if the "bing" string is added to the blocklist, it behaves differently than when the "PC=U510" string is added.
The bug is still valid, but there might be another issue being uncovered by this revelation. 

Mark, what do you think?

Back to Bug 1583479 Comment 6