How can Issue 664177 be closed if we're still merging issues?
Reported by
mike.lit...@weather.com,
Jan 19 2017
|
||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:50.0) Gecko/20100101 Firefox/50.0 Steps to reproduce the problem: If everyone is still experiencing this after 10 weeks, how can the ticket be closed? What is the expected behavior? Chromium to work always. What went wrong? Issue 664177 has been closed incorrectly. Did this work before? Yes 43 Chrome version: <Copy from: 'about:version'> Channel: n/a OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Shockwave Flash 23.0 r0 Please let us know if this issue will be legitimately resolved.
,
Jan 20 2017
Marking this as WontFix - Issue 664177 was correctly closed, the 'issue' is that it requires an update for non-Chrome-branded browsers (e.g. if you are using Android WebView, Chromium provided by a distro, a Chromium-derived browser that enabled Certificate Transparency enforcement, etc). Updating to 55 or later, as captured in that bug, resolves it for those non-Chrome browsers. For Chrome-branded browsers, the issue was resolved via experimental configuration ("Finch")
,
Jan 20 2017
Ah, Thanks! I didn't see that in the notes. It seemed like 55 was being reported as having the issue. |
||
►
Sign in to add a comment |
||
Comment 1 by kavvaru@chromium.org
, Jan 20 2017