Opened 4 years ago
Last modified 21 months ago
#2623 new defect
Unexpected behaviour when opening a new Private Tab from History
| Reported by: | passbrains | Assignee: | rjeschke |
|---|---|---|---|
| Priority: | Unknown | Milestone: | |
| Module: | Adblock-Browser-for-Android | Keywords: | |
| Cc: | Blocked By: | ||
| Blocking: | Platform: | Adblock Browser for Android | |
| Ready: | no | Confidential: | no |
| Tester: | Unknown | Verified working: | no |
| Review URL(s): | |||
Description (last modified by fhd)
Adapted from https://www.passbrains.com/dashboard/view-ticket.php?ticket_no=ADR-14
Environment
Samsung + Galaxy S 4 + Android 4.4.2
How to reproduce
- Open Adblock Browser - Homepage will be opened
- Browse for some pages
- Then go to the Adblock homepage
- Tap on History tab
- Tap on Clear Browsing History and confirm to delete
- Now tap on New Private Tab link from the message in the History tab
- Observe navigation
NOTE : I have tested the latest build(1.0.0.20150520125137) which was given under Test URL's.
Observed behaviour
Tap on New Private Tab from the History page, Settings options opened and no private tab opened
Expected behaviour
Tap on New Private Tab from the History page, a new private tab should be opened
Attachments (1)
Change History (4)
Changed 4 years ago by passbrains
comment:1 Changed 4 years ago by fhd
- Component changed from Unknown to Adblock-Browser-for-Android
- Description modified (diff)
- Owner set to rjeschke
- Summary changed from Galaxy S4 to Unexpected behaviour when opening a new Private Tab from History
comment:2 Changed 4 years ago by philll
- Platform changed from Android to Adblock Browser for Android
See #2673
comment:3 Changed 21 months ago by diegocarloslima
- Tester set to Unknown
I don't think that a upstream bug will solve that, since this is the intended behaviour of Firefox. Tested in the latest Firefox release (55.0) and it still behaves like this. If we want to change this behaviour, we'll need to change that ourselves.
Note: See
TracTickets for help on using
tickets.
This appears to be as intended, works the same way in Firefox for Android. We should look for an upstream bug. If there is none, we can think about submitting one ourselves.