Closed Bug 420095 Opened 17 years ago Closed 4 years ago

Larry (Identity UI) should identify (chrome) error pages as such and not as an unverified site

Categories

(Firefox :: Site Identity, enhancement)

Product:
Firefox
Component:
Site Identity
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: bram, Unassigned)

References

Details

(Whiteboard: [tor 34370])

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b4pre) Gecko/2008022704 Minefield/3.0b4pre Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b4pre) Gecko/2008022704 Minefield/3.0b4pre When getting an (network) error page like "Failed to Connect" clicking the favicon makes Larry gives inaccurate information. Reproducible: Always Steps to Reproduce: 1. Visit a URL (e.g. http://localhost:8765 or some other port nothing is listening to) that would cause an error page to appear. 2. Click the favicon in the location bar Actual Results: The error page tells me I've "Failed to Connect". Larry says: "You are connected to an unverified site Your connection to this website is not encrypted". Expected Results: Larry should say something like: "You are not connected to a site. Your seeing an error page generated by Firefox." It would also be a way to detect spoofed error pages.
Version: unspecified → Trunk
This would also let us say something smarter when malware pages are displayed too.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Same applies to about:blank, about:config, about:mozilla and the like. Jo Hermans mentioned that about:credits is an exception, though, as it uses external data.
Fixed with Bug 750106, or is there something left to do?
The specific steps to reproduce still show this bug: Even when Firefox is unable to connect at all it's telling me that my connection is not encrypted.
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INACTIVE

Reopening. This issue was recently reported by a Tor Browser user. See: https://trac.torproject.org/projects/tor/ticket/34370

Status: RESOLVED → REOPENED
Resolution: INACTIVE → ---
Whiteboard: [tor 34370]
Component: Address Bar → Site Identity

This bug has mostly been fixed as suggested in comment 4. Re. the specific steps to reproduce, showing that connection is not encrypted is the intended behavior here since the premise is that the user will associate the information with the site that couldn't be reached rather than the error page content that's actually shown (which e.g. a Firefox developer might know is loaded from a bundled chrome:// resource).

Maybe we can replace the content to specifically say that the connection could not be made, but this UI has been discussed so much over the last several years that I doubt we will update this again now. If we do, we can do it in a new bug with fresh context and user story.

Status: REOPENED → RESOLVED
Closed: 7 years ago → 4 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.