Closed
Bug 1432399
Opened 7 years ago
Closed 7 years ago
Affordance of history navigation backward/forward
Categories
(Core :: Widget: Cocoa, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 860493
People
(Reporter: domoritz, Unassigned)
Details
(Keywords: ux-affordance)
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:58.0) Gecko/20100101 Firefox/58.0
Build ID: 20180118215408
Steps to reproduce:
Use my touch pad to go back to the previous page.
Actual results:
It takes a few seconds and then the old page is loaded. I don't have a visual indicator.
Expected results:
Chrome and Safari and visual indicators. Firefox needs this as well to give users feedback.
Reporter | ||
Updated•7 years ago
|
OS: Unspecified → All
Hardware: Unspecified → All
Reporter | ||
Comment 1•7 years ago
|
||
Related: 860493
Reporter | ||
Updated•7 years ago
|
Keywords: ux-affordance
Reporter | ||
Updated•7 years ago
|
Summary: Indicate history backward/forward → Affordance of history navigation backward/forward
Component: Untriaged → Widget: Cocoa
OS: All → Mac OS X
Product: Firefox → Core
Hardware: All → x86
Comment 2•7 years ago
|
||
(In reply to Dominik Moritz from comment #1)
> Related: 860493
We don't need additional bugs to track the same feature.
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Comment 3•7 years ago
|
||
I added a separate issue to track a slightly different feature. The original issue was about overscroll as far as I understand. Here, I am suggesting a simple indicator. I was hoping that it would not be blocked by some compositor changes as the original issue hasn't been solved for 5 years.
Comment 4•7 years ago
|
||
(In reply to Dominik Moritz from comment #3)
> I added a separate issue to track a slightly different feature. The original
> issue was about overscroll as far as I understand. Here, I am suggesting a
> simple indicator. I was hoping that it would not be blocked by some
> compositor changes as the original issue hasn't been solved for 5 years.
Understood. The fact that the bug hasn't been solved in 5 years doesn't mean that we haven't been thinking/working on it. I will get back to this shortly and will explore exactly what you suggested: use a visual indicator for back/forward swipes. However, I will also revisit the current state of things to make sure that using snapshots still constitutes a significant amount of work. Should we need a separate bug for visual indicators I will reopen this bug to track the work.
Reporter | ||
Comment 5•7 years ago
|
||
(In reply to Stephen A Pohl [:spohl] from comment #4)
> Understood. The fact that the bug hasn't been solved in 5 years doesn't mean
> that we haven't been thinking/working on it. I will get back to this shortly
> and will explore exactly what you suggested: use a visual indicator for
> back/forward swipes. However, I will also revisit the current state of
> things to make sure that using snapshots still constitutes a significant
> amount of work. Should we need a separate bug for visual indicators I will
> reopen this bug to track the work.
Thank you for the clarification. I understand that you need to prioritize a lot of features and that there are complicated dependencies. Thank you for the hard work and I am happy to give feedback on any prototypes.
You need to log in
before you can comment on or make changes to this bug.
Description
•