Closed Bug 1944309 Opened 1 year ago Closed 6 months ago

www.royalmail.com - Tracking item does not work in Private Browsing Mode

Categories

(Web Compatibility :: Site Reports, defect, P2)

ARM
Android

Tracking

(Webcompat Priority:P2, Webcompat Score:6, firefox134 affected, firefox135 affected, firefox136 affected)

RESOLVED WORKSFORME
Webcompat Priority P2
Webcompat Score 6
Tracking Status
firefox134 --- affected
firefox135 --- affected
firefox136 --- affected

People

(Reporter: rbucata, Unassigned)

References

()

Details

(Keywords: webcompat:needs-diagnosis, webcompat:site-report, Whiteboard: [webcompat-source:web-bugs])

User Story

user-impact-score:240
platform:android
impact:workflow-broken
configuration:general
affects:some
branch:release
diagnosis-team:webcompat

Environment:
Operating system: Android 11
Firefox version: Firefox Mobile 134.0

Preconditions:
Valid tracking number

Steps to reproduce:

  1. Navigate to:
  2. Insert the tracking number into the input field
  3. Tap on the "Track your delivery" button and observe

Expected Behavior:
The tracking status is returned

Actual Behavior:
Nothing happens

Notes:

  • Reproducible regardless of the status of ETP
  • Reproducible on the latest build of Firefox Nightly and Release
  • Not reproducible with Normal Browsing Mode

Created from https://github.com/webcompat/web-bugs/issues/147133

Component: Site Reports → Privacy: Site Reports
Summary: www.royalmail.com - site is not usable → www.royalmail.com - Tracking item does not work in Private Browsing Mode

Since nightly and release are affected, beta will likely be affected too.
For more information, please visit BugBot documentation.

I see a failing captcha in the devtools when clicking on the button for the first time:

https://api-web.royalmail.com/mailpieces/v3/{{removed: tracking number}}/events

{
  "httpCode": "401",
  "httpMessage": "Unauthorized",
  "moreInformation": "captcha validation failed",
  "errors": [
    {
      "errorCode": "E0015",
      "errorDescription": "Access denied",
      "errorCause": "Invalid or expired captcha token",
      "errorResolution": "Please request for a new captcha token"
    }
  ]
}

The second time seems to consistently succeed. It doesn't seem to be related to blocking resources, but I couldn't figure out another root cause.

Severity: -- → S2
Priority: -- → P3

For me this doesn't even work in normal mode with ETP off. I keep seeing NS_ERROR_NET_INTERRUPTED when trying to talk to the api-web.royalmail.com host.

Moving to Site reports based on comment #3 and resetting triage.

Severity: S2 → --
Component: Privacy: Site Reports → Site Reports
Priority: P3 → --
User Story: (updated)
Webcompat Score: --- → 1
Severity: -- → S4
User Story: (updated)
Webcompat Priority: --- → P2
Webcompat Score: 1 → 6
Priority: -- → P2

(In reply to Raul Bucata from comment #0)

  1. Insert the tracking number into the input field
  2. Tap on the "Track your delivery" button and observe

Looks like we need a tracking number in order to test this.

The tracking number from the screenshot on the GitHub issue is TQ632570345GB but unfortunately that tracking number doesn't seem to work at all in Chrome or Firefox at this point.

Does anyone have a tracking number that can be used to reproduce a Firefox-specific issue at this point?

Oh, huh - the tracking number wasn't getting me a useful page on Firefox or Chrome on desktop, but it does work properly in Firefox-on-Android - I get to a page that says "Delivered" along with other tracking info.

It works for me in normal mode as well as private browsing mode as well. I tested Firefox release 144 as well as Nightly 146 on my Pixel 10 Pro XL (using Private Browsing mode in both, visiting https://www.royalmail.com/track-your-item and pasting in TQ632570345GB as the tracking number)

So whatever the bug was here, it seems to have been fixed.

Status: NEW → RESOLVED
Closed: 6 months ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.