https://redmine.stoutner.com/https://redmine.stoutner.com/favicon.ico?16699090422018-07-04T04:23:17ZStoutner - RedminePrivacy Browser Android - Feature #299: Remove favicon from URL barhttps://redmine.stoutner.com/issues/299?journal_id=7302018-07-04T04:23:17ZSoren Stoutnersoren@stoutner.com
<ul><li><strong>Assignee</strong> set to <i>Soren Stoutner</i></li><li><strong>Priority</strong> changed from <i>2</i> to <i>3.x</i></li></ul><p>1. Privacy Browser does not use a lock to indicate HTTPS connections, so this concern does not apply.</p>
<p>2. Reclaiming precious space in the UI is a valid consideration. However, the favicon does not just display the icon, but tapping on it also displays the SSL certificate information. If it were removed from the interface, that functionality would have to be moved somewhere else, probably somewhere in the options menu.</p>
<p>My general impression is that I am not included to make any changes in this regard right now for the following reasons:</p>
<p>a. I like the way it looks to have the favorite icon displayed. It is something I miss from some other browsers.</p>
<p>b. If I did implement a change, it would be an optional display option, so the user could decide if they wanted the favicon to be displayed to the left of the URL bar or if they wanted it to be hidden and an option menu item used to access the SSL certificate information. This is doable, but having multiple interfaces is more complex than might be readily apparent, and increases the time in the future that must be spent on regression testing to make sure that some aspect of this multi-interface design doesn't break when some other seemingly unrelated feature is added.</p>
<p>As such, I am unlikely make this change unless there are a large number of users who are in favor of having it. I will leave this feature request open. If you would like to see this happen, please add a comment below. If there are enough comments from enough people I will revisit the idea.</p> Privacy Browser Android - Feature #299: Remove favicon from URL barhttps://redmine.stoutner.com/issues/299?journal_id=8842018-11-03T22:13:59ZSoren Stoutnersoren@stoutner.com
<ul></ul><p>It is quite possible that with the addition of tabbed browsing in the 3.x series, the favicon might move to the tabbed interface, which would resolve the issue with space in the URL bar. <a class="external" href="https://redmine.stoutner.com/issues/22">https://redmine.stoutner.com/issues/22</a> After tabbed browsing is implemented I will revisit this issue if anything additional needs to be done.</p> Privacy Browser Android - Feature #299: Remove favicon from URL barhttps://redmine.stoutner.com/issues/299?journal_id=11252019-04-27T19:07:52ZSoren Stoutnersoren@stoutner.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Closed</i></li></ul><p>Tabbed browsing did indeed move the favorite icon to the tab interface, so it is now no longer on the URL bar.</p> Privacy Browser Android - Feature #299: Remove favicon from URL barhttps://redmine.stoutner.com/issues/299?journal_id=37602024-01-09T01:57:24Zask low
<ul></ul><p>Removing favicon from URL bar or tabs ? I'm confused by this ticket description.<br />As far as I read from the previous comments and blogs of soren, removing the favicon from tab visibility does not prevent sites from grabbing it in the first place. Am I right ?</p>
<a name="PS"></a>
<h3 >PS<a href="#PS" class="wiki-anchor">¶</a></h3>
<p>Btw I always thought that disabling Images shouldn't render favicons because they're images too. But they still do.</p> Privacy Browser Android - Feature #299: Remove favicon from URL barhttps://redmine.stoutner.com/issues/299?journal_id=37612024-01-09T17:33:41ZSoren Stoutnersoren@stoutner.com
<ul></ul><p>Some browsers do not display the protocol part of the URL (HTTP or HTTPS), but only display a lock icon if the URL is encrypted. On some of these browsers, this lock icon was displayed next to the favorite icon. Some malicious websites that were not encrypted started using an identical lock icon as their favorite icon in an effort to confuse users.</p>
<p>As explained above, none of this affects Privacy Browser, so this feature request was closed without action.</p>