-
Notifications
You must be signed in to change notification settings - Fork 711
Cannot get rid of trash can circle #809
Comments
@squarewave I’ve been able to dismiss the erase button simply by scrolling down the page. What do you think about this non-permanent dismissal versus getting rid of it entirely? |
@squarewave Is this a page that doesn't scroll (#810) or is the button not hiding when scrolling? |
@brampitoyo, personally (but I know I'm just one user), the fact that it goes away on scroll is nice, but not quite enough. The circle is the browser reminding me that it exists, which no other browser really does. Though it's not egregious, it does feel a bit like it's stealing attention away from the content that I'm viewing. That being said I understand that there's a trade-off here - the erase button does successfully make it clear and obvious how this browser I am using is different from, say, Chrome, so I think it makes sense to have the button exist by default. But I think heavy users might eventually tire from seeing it everywhere once the novelty wears off, even if it goes away once they scroll down. |
Adding the 'needs triage' label back because the I don't think this is in our V2 list, the bug/issue isn't completely clear ATM, and there's still some discussion going on |
see #1312 |
This is no longer an issue. The pink trashcan has been moved in the toolbar. |
Not sure if this is where I should be throwing this, but hopefully someone can direct me where to go if this isn't a good place. It's kind of annoying that I can't get rid of the purple trash can circle in the bottom right. It would be nice if I could move that feature to an option in the menu, maybe under "Open with...". I'm trying to use Focus as my default browser, but it can be a bit irritating seeing the trash can everywhere.
Also, my impulse as a user is to try a long press on the button to give me an option to get rid of it, but doing this just ends up activating the button and deleting my history. Don't have any thoughts on what should be done about that, just thought I'd provide the anecdote.
The text was updated successfully, but these errors were encountered: