<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Fidelity.com login page does not show username and password field"
href="https://bugs.webkit.org/show_bug.cgi?id=151782#c8">Comment # 8</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Fidelity.com login page does not show username and password field"
href="https://bugs.webkit.org/show_bug.cgi?id=151782">bug 151782</a>
from <span class="vcard"><a class="email" href="mailto:dbates@webkit.org" title="Daniel Bates <dbates@webkit.org>"> <span class="fn">Daniel Bates</span></a>
</span></b>
<pre>Looking at <<a href="https://login.fidelity.com/ftgw/pages/js/common/device_print.js">https://login.fidelity.com/ftgw/pages/js/common/device_print.js</a>>, Fidelity.com is using the navigator.plugins data as a way to fingerprint a device, which is a behavior that we do not want to support and mitigated in the patch for <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - Hide all plugin names except Flash, Java, and QuickTime"
href="show_bug.cgi?id=149014">bug #149014</a>.
As aforementioned in the second paragraph of <a href="show_bug.cgi?id=151782#c3">comment #3</a>, Fidelity.com has a JavaScript error in their code such that when navigator.plugins.length == 0 a ReferenceError is thrown and this affects the display of a username and password field. Fidelity.com should update their code to address this issue.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>