Buggy Sites on Thurrott.com


Hello Support Team,

I would like to report a major problem with the Thurrott website. The pages do not work properly depending on the size of the display in the browser.

No problem on the desktop, but very unpleasant on an iPad Pro.

The problem occurs with almost all sub-pages. The main page and podcast page are OK.

The problem has been there since last year. I thought it would be fixed soon. But this is not the case. I already reported this directly to the support but thought it wouldn’t hurt to document it here.

Comments (5)

5 responses to “Buggy Sites on Thurrott.com”

  1. Paul Thurrott

    Please email [email protected] about this issue. We can't do tech support off of the forums.



    • goetti

      In reply to paul-thurrott:

      Thanks Paul.

      Of course, I've reported it to the support. On January 3rd. I've also provided much more information as well where the problem in the page layout seem to come from.

      Let me share the answer from the support here:

      "That would be implying this is by design. What your seeing is related to an unorthodox break point. I'll pass this forward to our front-end developers, it should be a minor modification of breakpoint behavior." 

      And this one arrived yesterday:

      "Your ticket - Web Site is buggy - Contact from Thurrott.com - has been closed.

      We hope that the ticket was resolved to your satisfaction. If you feel that the ticket should not be closed or if the ticket has not been resolved, please reply to this email."

      Nothing has been fixed and of course I am not satisfied. So I thought it would be useful to share it in the forum, hoping that someone would take the problem seriously.

      • Tim

        In reply to goetti:

        That ticket has not been closed. The issue is in the queue with our front-end developer and is slated to be released in the next code push we make to this site which is likely to happen within the next 7 days.

  2. goetti

    Got a message today that the problem has been fixed.

    It now works fine. 

    Everyone who uses an iPad to read the pages will surely appreciate that...