Closed
Bug 1277937
Opened 9 years ago
Closed 9 years ago
https has an underline instead of a strikethrough when mixed active content is loaded
Categories
(Firefox :: General, defect, P1)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox46 | --- | unaffected |
| firefox47 | --- | unaffected |
| firefox48 | + | verified |
| firefox49 | --- | verified |
| firefox-esr45 | --- | unaffected |
| firefox50 | --- | verified |
People
(Reporter: tanvi, Assigned: xidorn)
References
Details
(Keywords: regression, Whiteboard: [fxprivacy])
Attachments
(2 files)
|
13.20 KB,
image/png
|
Details | |
|
58 bytes,
text/x-review-board-request
|
jfkthame
:
review+
lizzard
:
approval-mozilla-aurora+
lizzard
:
approval-mozilla-beta+
|
Details |
STR:
1) Go to https://people.mozilla.org/~tvyas/mixedcontent.html
2) Open the control center, go to the submenu.
3) Click Disable Protection
4) observe the url bar. It should show an crossed out grey lock and a crossed out https, like the fourth picture in the second column here:
https://ffp4g1ylyit3jdyti1hqcvtb-wpengine.netdna-ssl.com/security/files/2015/10/combo-graph21.png. It actually looks like a crossed out lock with an *underlined https*.
Why did the https switch from being struck through to underlined? What release did this issue occur in? Sometime between 46 and 49. In 46 it looks good, in 49 it does not.
+++ This bug was initially created as a clone of Bug #1253771 +++
(In reply to Tanvi Vyas - behind on reviews [:tanvi] from comment #21)
> (In reply to Johann Hofmann [:johannh] from comment #18)
> > (In reply to agrigas from comment #17)
> > > Also the https shouldnt have a line under it...
> >
> > When I visit a site like https://mixed-script.badssl.com/ and turn off
> > protection then it has that line on my Aurora/DevEdition and Nightly, but
> > not on stable Firefox. Is that a bug? We should really fix it then.
>
> That seems like a bad regression! We do not want to underline https when
> protection is disabled! It is supposed to be struck through. On Firefox 46
> release, I see a struck through https in the url bar when we disable
> protection. But on Nightly, I see an underlined https in the url bar. That
> is no good!
>
> https://people.mozilla.com/~tvyas/mixedcontent.html
Comment 1•9 years ago
|
||
Found the following regression:
9:56.49 INFO: Last good revision: b79f70a20d4a380715f1fc79a986aac6703d993a
9:56.49 INFO: First bad revision: e4d32bd5e11e3612f91cea4fc8fd799019304351
9:56.49 INFO: Pushlog:
https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=b79f70a20d4a380715f1fc79a986aac6703d993a&tochange=e4d32bd5e11e3612f91cea4fc8fd799019304351
9:57.76 INFO: Looks like the following bug has the changes which introduced the regression:
https://bugzilla.mozilla.org/show_bug.cgi?id=1258636
Xidorn, would you mind taking a look whenever you have some time? Thanks!
Flags: needinfo?(bugzilla)
| Assignee | ||
Comment 2•9 years ago
|
||
Could someone tell me what style does it use to display that line? I had a look via the browser toolbox inspector, but couldn't find anything useful.
Comment 3•9 years ago
|
||
See my attached image
Comment 4•9 years ago
|
||
Oh, were you referring to the code that draws that line? You can find it here: https://dxr.mozilla.org/mozilla-central/source/browser/base/content/urlbarBindings.xml#216
| Assignee | ||
Comment 5•9 years ago
|
||
Yes, I mean the code. Thanks for the information.
| Assignee | ||
Comment 6•9 years ago
|
||
Taking this. Will submit patch soon, waiting for local build.
Assignee: nobody → bugzilla
status-firefox46:
--- → unaffected
status-firefox47:
--- → unaffected
status-firefox48:
--- → affected
status-firefox49:
--- → affected
status-firefox-esr45:
--- → unaffected
tracking-firefox48:
--- → ?
Flags: needinfo?(bugzilla)
Version: 47 Branch → 48 Branch
| Assignee | ||
Comment 7•9 years ago
|
||
Review commit: https://reviewboard.mozilla.org/r/57770/diff/#index_header
See other reviews: https://reviewboard.mozilla.org/r/57770/
Attachment #8760041 -
Flags: review?(jfkthame)
| Reporter | ||
Comment 8•9 years ago
|
||
When do we show the struck through https? Are there any cases other than when mixed active content has loaded?
Updated•9 years ago
|
Attachment #8760041 -
Flags: review?(jfkthame)
Comment 9•9 years ago
|
||
Comment on attachment 8760041 [details]
Bug 1277937 - Fix SELECTION_URLSTRIKEOUT.
https://reviewboard.mozilla.org/r/57770/#review54632
::: layout/generic/nsTextFrame.cpp:5616
(Diff revision 1)
> - offset = metrics.strikeoutOffset + 0.5;
> - aDecoration = NS_STYLE_TEXT_DECORATION_LINE_LINE_THROUGH;
> + params.offset = metrics.strikeoutOffset + 0.5;
> + params.decoration = NS_STYLE_TEXT_DECORATION_LINE_LINE_THROUGH;
It looks like this fail to account for aDecorationOffsetDir in the resulting params.offset, doesn't it?
| Assignee | ||
Comment 10•9 years ago
|
||
Comment on attachment 8760041 [details]
Bug 1277937 - Fix SELECTION_URLSTRIKEOUT.
Review request updated; see interdiff: https://reviewboard.mozilla.org/r/57770/diff/1-2/
Attachment #8760041 -
Flags: review?(jfkthame)
Updated•9 years ago
|
Attachment #8760041 -
Flags: review?(jfkthame) → review+
Comment 11•9 years ago
|
||
Comment on attachment 8760041 [details]
Bug 1277937 - Fix SELECTION_URLSTRIKEOUT.
https://reviewboard.mozilla.org/r/57770/#review54636
Looks better, thanks. Could we have reftests for this, too? We could at least verify that text-decoration: none / underline / overline / line-through all render differently.
| Assignee | ||
Comment 12•9 years ago
|
||
That wouldn't catch this regression either.
I guess it might be good to open another bug and have a mochitest to check behavior of decoration lines.
Updated•9 years ago
|
Whiteboard: [fxprivacy][triage]
| Assignee | ||
Updated•9 years ago
|
Keywords: checkin-needed
Comment 13•9 years ago
|
||
Pushed by mozilla@noorenberghe.ca:
https://hg.mozilla.org/integration/fx-team/rev/2666d8ddb8ef
Fix SELECTION_URLSTRIKEOUT. r=jfkthame
Keywords: checkin-needed
Comment 14•9 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 9 years ago
status-firefox50:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 50
Updated•9 years ago
|
Blocks: 1258636
Keywords: regression
Comment 15•9 years ago
|
||
We will probably need QA verification for this. Florin, could you take a look? It's a bit urgent, since this regression is already in Beta. STR see first comment.
Flags: qe-verify+
Flags: needinfo?(florin.mezei)
Comment 16•9 years ago
|
||
Comment on attachment 8760041 [details]
Bug 1277937 - Fix SELECTION_URLSTRIKEOUT.
Approval Request Comment
[Feature/regressing bug #]: Bug 1258636
[User impact if declined]: Pretty serious Security UI regression, all stroke through https signs for insecure pages will instead be underlined.
[Describe test coverage new/current, TreeHerder]: See comments, this is a visual regression that would not be easy to catch by a machine but can easily be verified by QA. We're waiting on QA right now.
[Risks and why]: The change is really small, seems to be just correcting an oversight from Bug 1258636. If anything were wrong, we might introduce another visual regression.
[String/UUID change made/needed]: none
Attachment #8760041 -
Flags: approval-mozilla-beta?
Attachment #8760041 -
Flags: approval-mozilla-aurora?
Updated•9 years ago
|
Flags: needinfo?(florin.mezei)
QA Contact: paul.silaghi
Comment 17•9 years ago
|
||
Verified fixed FX 50.0a1 (2016-06-08) Win 7, Ubuntu 16.04, OS X 10.11.
Fyi, bug 1186892 is related to this and it's still reproducible on Windows.
Comment 18•9 years ago
|
||
Comment on attachment 8760041 [details]
Bug 1277937 - Fix SELECTION_URLSTRIKEOUT.
Regression from 48, please uplift to aurora and beta.
Attachment #8760041 -
Flags: approval-mozilla-beta?
Attachment #8760041 -
Flags: approval-mozilla-beta+
Attachment #8760041 -
Flags: approval-mozilla-aurora?
Attachment #8760041 -
Flags: approval-mozilla-aurora+
Comment 19•9 years ago
|
||
| bugherder uplift | ||
Comment 20•9 years ago
|
||
| bugherder uplift | ||
Updated•9 years ago
|
Iteration: --- → 50.1
Backed out from beta because it apparently made some android reftests near permafail:
https://hg.mozilla.org/releases/mozilla-beta/rev/b449af6b8741
https://treeherder.mozilla.org/#/jobs?repo=mozilla-beta&bugfiler&fromchange=331c922bff8152bc967e9065a97566f9f712e434&filter-tier=1&selectedJob=1190227&filter-searchStr=6c23eb02ba6973e0b2514fcc333c02202c2e5f59
Flags: needinfo?(bugzilla)
| Assignee | ||
Comment 22•9 years ago
|
||
It has been clear that permafail isn't this patch's fault, and it has been re-land on beta by philor:
https://hg.mozilla.org/releases/mozilla-beta/rev/f751465bac6a
Flags: needinfo?(bugzilla)
Updated•9 years ago
|
Comment 23•9 years ago
|
||
Verified fixed FX 49.0a2 (2016-06-23), 48b3 Win 7.
Updated•9 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•