3 ms·
The only studies are from a decade ago using the IE7 UI: Then: https://paypal.com Identified by Thawte Compared to now: PayPal Inc [US] |
by nailer 10y ago
The only studies are from a decade ago using the IE7 UI:
Then:
https://paypal.com Identified by Thawte
Compared to now:
PayPal Inc [US] | https://paypal.com
I'd love to either be able to do this ourselves or for the browsers to test the effectiveness of their own UIs.
- koolba 10y ago> I'd love to either be able to do this ourselves or for the browsers to test the effectiveness of their own UIs. That'd be pretty cool. A flag you could set (probably in head > meta) that instructs the browser to use a default padlock instead of a fancy EV name for display HTTPS info. That'd obviate the need to have two separate HTTPS endpoints for your app too. Combined with User-Agent verification you could infer what % of clients respect the flag and what % impact (if any) it has on their conversion habits. Course I doubt browser vendors would be up for adding something like this. Would probably be a pain as the rendering code would be separate from the display of the overall chrome.
- deleted 10y ago[deleted]