Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

vpp.itunes.apple.com - site is not usable #13944

Closed
webcompat-bot opened this issue Nov 30, 2017 · 5 comments
Closed

vpp.itunes.apple.com - site is not usable #13944

webcompat-bot opened this issue Nov 30, 2017 · 5 comments

Comments

@webcompat-bot
Copy link

URL: https://vpp.itunes.apple.com/store?term=firefox&mediaType=All

Browser / Version: Firefox 59.0
Operating System: Linux
Tested Another Browser: Yes

Problem type: Site is not usable
Description: No apps are listed in Apple's VPP store
Steps to Reproduce:
Entered the term "firefox" in the search box
Screenshot Description

From webcompat.com with ❤️

@webcompat-bot webcompat-bot added the type-stylo Firefox stylo engine label Nov 30, 2017
@webcompat-bot webcompat-bot added this to the needstriage milestone Nov 30, 2017
@adamopenweb
Copy link
Collaborator

adamopenweb commented Nov 30, 2017

Thanks for the report. I can reproduce this issue in Firefox 57 for OSX.

Works in Chrome:
screen shot 2017-11-30 at 2 00 07 pm

In the Firefox console:

TypeError: t is null                             web-storefront-volumestore.js:390:9

@barabadzhi
Copy link

barabadzhi commented Dec 2, 2017

In fact the same issue remains in Chromium:
Screenshot Description

So, it is not directly related to Firefox.

One major difference is that instead of Chromium Firefox just stops the whole script when it trows an error and Chromium continue to the point of fetching results and it-just-looks-like-it-is-working.

My advice will be to reach out Apple to fix their website instead, because it-is-broken.

@karlcow
Copy link
Member

karlcow commented Jan 5, 2018

Thanks @hiseni
Switching to contactready.

@jonathandavis do you think you could help raise this issue internally? or should we go through the partner mailing-list? @adamopenweb

@adamopenweb
Copy link
Collaborator

adamopenweb commented Apr 4, 2018

Contacting through partner mailing list.

Also just to note that this is broken in Chrome Canary now, release Chrome still looks-like-it-is-working. 😄

@adamopenweb adamopenweb modified the milestones: contactready, sitewait Apr 4, 2018
@adamopenweb
Copy link
Collaborator

This is working for me in Firefox 61+ for MacOS. Still seeing the TypeError in the console, but searching works at least.

Closing this report but please comment or reopen if you can still reproduce the issue.

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants