Paladin Reporter
	Description • 9 years ago

[1.Description]:
[Flame][v2.2&3.0][App/Datastore Permissions]The cert error page can't appear again when you visit the same website for the second time.
Attachments: logcat_flame_0611.txt and  no_cert_error_page.3gp
Occurrence time: 06:11

[2.Testing Steps]: 
1. Open the browser app. 
2. Tap on the URL and type:
https://cav.receita.fazenda.gov.br/eCAC/Aplicacao.aspx 
3. Add a temporary exception. (Tap visit it)
4. Close the browser through the card viewer. 
5. Open the browser app. 
6. Tap on the URL and type:
https://cav.receita.fazenda.gov.br/eCAC/Aplicacao.aspx 


[3.Expected Result]: 
6.A cert error page should appear.

[4.Actual Result]: 
6.The cert error page  will not appear.

[5.Reproduction build]: 
Device:Flame 2.2 [Affected]
Build ID               20150325162500
Gaia Revision          2d42a7c1d99472780e3aeb2e16d7cb0a4adbd222
Gaia Date              2015-03-25 20:46:52
Gecko Revision         https://hg.mozilla.org/releases/mozilla-b2g37_v2_2/rev/ebb742bfe1a4
Gecko Version          37.0
Device Name            flame
Firmware(Release)      4.4.2
Firmware(Incremental)  eng.cltbld.20150325.200218
Firmware Date          Wed Mar 25 20:02:30 EDT 2015
Bootloader             L1TC000118D0

Device:Flame 3.0 [Affected]
Build ID               20150325160204
Gaia Revision          508b8d48fb5ecf08bf0e5b4fef42bc48b770e7f2
Gaia Date              2015-03-25 16:54:53
Gecko Revision         https://hg.mozilla.org/mozilla-central/rev/f40ee067d081
Gecko Version          39.0a1
Device Name            flame
Firmware(Release)      4.4.2
Firmware(Incremental)  eng.cltbld.20150325.191758
Firmware Date          Wed Mar 25 19:18:07 EDT 2015
Bootloader             L1TC000118D0


[6.Reproduction Frequency]: 
Always Recurrence,5/5

[7.TCID]: 
6914

	Gregor Wagner [:gwagner]
	Comment 2 • 9 years ago

How about 2.1?

	Pi Wei Cheng [:piwei] (inactive)
	Comment 3 • 9 years ago

This issue reproduces on Flame 2.1. Tap on "Visit site" button, close browser and re-visit the site doesn't prompt user for certification error. Even if I go to Settings and clear browser history and cookies it still doesn't prompt me again.

Device: Flame 2.1
BuildID: 20150326001202
Gaia: 6f39e4e876152de1dcdcc0e7656197f22f105e4b
Gecko: e00ae73d67a2
Gonk: b83fc73de7b64594cd74b33e498bf08332b5d87b
Version: 34.0 (2.1) 
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

	Gregor Wagner [:gwagner]
	Comment 4 • 9 years ago

Its not a regression. Paul, what do you think, how serious is this?

	Paul Theriault [:pauljt] (no longer reading bugmail)
	Comment 5 • 9 years ago

(In reply to Gregor Wagner [:gwagner] from comment #4)
> Its not a regression. Paul, what do you think, how serious is this?

Are you sure this is a regression? When you add an exception, you are adding the exception for this browsing session. Closing the "browser" app closes the tab that the browser is running, but it doesn't "close the browser" in the sense of stop b2g. So when you "reopen" the browser app, the exception is still there. (until b2g is restarted, for example if you restart your phone).

This has been raised before (by myself, and also others - I'll find the dupes). I completely agree with original post - closing the browser app should clear the exceptions. But afaik this isn't a regression - I don't think we ever supported this.

	Paul Theriault [:pauljt] (no longer reading bugmail)
	Comment 6 • 9 years ago

(In reply to Gregor Wagner [:gwagner] from comment #4)
> Its not a regression. Paul, what do you think, how serious is this?

I should learn to read? :) And yes its a dupe of 858730

To answer your actual question, I don't think this should block, but this *is* important (though I've never managed to convince anyone enough that this gets prioritized on our roadmap). My team is planning to take this in Q2 though if no-one gets to it sooner.