UPS package tracking no longer working in TFF
I noticed yesterday that the UPS package tracking page no longer works in TFF FPR14 for G4 7450 on a Mac running Leopard. I'm visiting this type of URL with a tracking number inserted at the end of the string:
https://www.ups.com/track?loc=en_US&tracknum=
This lands me on the tracking page with a spinning progress wheel, but I never get a result. TFF remains responsive, but the wheel just keeps spinning. I tried disabling TFF's basic adblock yesterday and this morning I backed off to FPR10 and also tried using various user agents, all with no change in behavior. I assume UPS changed something on their end. I have no add-ons enabled. My alternative for now is to use Leopard WebKit for UPS package tracking.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Chris (chtrusch... on 08 Jun, 2019 07:37 AM
I can comfirm the problem, also that it works on LWK. It's another instance of issue 533 ('TypeError: this is undefined'), see
https://github.com/classilla/tenfourfox/issues/533
2 Posted by rardin on 08 Jun, 2019 02:18 PM
Thanks for confirming the issue, Chris. Issue 533 strikes again. I'm a Citi customer, so I'm already familiar with it, but didn't assume immediately that the UPS tracking issue was related.
3 Posted by guest on 25 Aug, 2019 01:13 PM
@rardin - is the missing menu on Citi.com also related ?
4 Posted by rardin on 25 Aug, 2019 06:26 PM
Yes, but the Citi issue may have been resolved by a change on the Citi end. I'd be interested to hear another Citi customer confirm that I'm not imagining this.
Support Staff 5 Posted by Cameron Kaiser on 25 Aug, 2019 09:43 PM
Yes, they're the same underlying issue.
6 Posted by ml on 17 Aug, 2020 11:16 PM
with regards to UPS tracking, looks like is still unresolved in 2020...
Support Staff 7 Posted by Cameron Kaiser on 18 Aug, 2020 12:37 AM
Feel free to submit a patch if you have a solution to it. Meanwhile, I'm a solitary developer, and multiple megabytes of changes landed in the test range which may or may not have anything to do with the front end parser issue responsible here.