740282 - Lock in lower right-hand corner is red and broken inapproprately

Status: UNCONFIRMED

(SeaMonkey :: General, defect)

Description

[Christine]

User Agent: Mozilla/5.0 (Windows NT 5.1; rv:11.0) Gecko/20120312 Firefox/11.0 SeaMonkey/2.8
Build ID: 20120312220748

Steps to reproduce:

I created an HTML document that I emailed to various email addresses. The document includes various images stored on a webserver using http: (NOT https:).


Actual results:

When viewing the email document in gmail, the "lock" in the lower right-hand corner shows red and broken. I assume this is because the images I am using are NOT referenced as https:. The problem is that the lock STAYS red and broken for all subsequent emails viewed in gmail, including those that are only text (no image references of any kind). Logging out and logging back into gmail seems to resolve the problem.


Expected results:

While I could make arguments either way for the initial "red broken lock", clearly it STAYING red and broken for all subsequent emails is an error. If the currently displayed email does not violate the https: protocol, then the lock should go to its normal pale yellow background and be "not broken". This is similar to https://bugzilla.mozilla.org/show_bug.cgi?id=383369

Comment 1

[therube]

> While I could make arguments either way for the initial "red broken lock",
> clearly it STAYING red and broken for all subsequent emails is an error.

AFAICT it is working as expected.

I don't think either are at error.  SeaMonkey is notifying you correctly.
(I would expect any other browsers to do likewise.)

At some point, there is non-secured content, hence the broken lock.
And it is not that the next message you are viewing is text only, it is not that the particular message is non-secured, it is that Gmail is displaying (elsewhere) non-secured content.

---

When (which is rare) I visit http://www.gmail.com/ my selected viewing mode is "Gmail in basic HTML".

By default (can be changed by pref, or by session), Gmail does not display images.
So you open a message, no images display, lock should be secure.

If I click, "Display images below", images display, coming over http:, so no longer secure, so broken lock displays.

If I then click the Inbox, at that point, no unsecured content is coming through, the lock is locked, yellow.

Now I view a textual message, that is still secured, locked.

I view another message with images, images unsecured, lock is broken.

Back to Sent Mail, all content secure, lock is locked, yellow.

Again, this is with "Gmail in basic HTML".

---

Now what I've described above /is/ different from you would see if you were not using "Gmail in basic HTML".  Maybe they call it "standard" or something like that?  (Standard requires JavaScript, Basic does not.)

When you initially load Standard, all is secure.  If you view a message, with unsecured images, the lock is broken.  At that point, all further actions display a broken lock.  Open a text message, still broken.  You will also see "Ads" displayed.  Those ads are unsecured.  While viewing that text message, click the "In new window" button (above the Reply box).  You will see that the new window opens, with only the message itself, no ads or whatnot, & the lock does show it is secure.

In addition to ads or other unsecured content they may be displaying, could be their particular programing method (Ajax or whatever) that contributes to the persistent broken lock?

Comment 2

[Philip Chee]

If you view the email in gmail and then view another one, does gmail remove the old email or just hide it from view? I suspect that Google optimizes the gmail code so as not to discard the previous N viewed messages in case you want to go back to it.

Comment 3

[Tony Mechelynck [:tonymec]]

(In reply to Philip Chee from comment #2)
> If you view the email in gmail and then view another one, does gmail remove
> the old email or just hide it from view? I suspect that Google optimizes the
> gmail code so as not to discard the previous N viewed messages in case you
> want to go back to it.

Seems removed, but I'm not sure: the Gmail source HTML is really hard to read

Comment 4

[Philip Chee]

That's because Google uses Java to write Gmail then uses a Java-to-JavaScript compiler to produce the final HTML/CSS/JS.