Windy Community
    • Unread
    • Categories
    • Groups
    • Go to windy.com
    • Register
    • Login

    Firefox on Mac showing 2000000 km/h winds

    Bug Reports
    3
    6
    843
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • R
      richlafferty | Premium
      last edited by richlafferty

      As of earlier today, my wind numbers are wrong in Firefox. It is only this Firefox profile - a new profile works fine.

      Things I have tried:

      • Chrome - works fine.
      • Another computer - works fine.
      • A new Firefox profile on this computer - works fine.
      • Private browsing window - still broken.
      • This Firefox profile in safe mode (no extensions loaded) - still broken.
      • "Clear all site data" in Firefox - still broken.
      • "Log out and delete stored data" at windy.com - still broken.

      Other features are working fine including wind gusts, it's just the wind numbers that seem wrong. Any idea what's up?

      8926b8d1-54ab-4b3e-8f79-5a73d050e78e-image.png

      1 Reply Last reply Reply Quote 0
      • R
        richlafferty | Premium
        last edited by

        I've found more problems (again, just this browser and profile).

        Everything in the "Rain/Snow" category is empty.

        "Temperature" is corrupted:

        a454f9eb-8725-4e24-bf24-1f9ef446a430-image.png

        As is "Waves":

        bc99a5dd-9641-4c74-abf5-f234f40a13fb-image.png

        But everything in "Clouds/Aviation" works fine.

        R 1 Reply Last reply Reply Quote 0
        • R
          richlafferty @richlafferty | Premium
          last edited by

          crossing fingers and bumping this -- I have no idea what's gone wrong but I would love to be able to use Windy again!

          R 1 Reply Last reply Reply Quote 0
          • R
            richlafferty @richlafferty | Premium
            last edited by richlafferty

            Resolved, but only through lots of Firefox profile hacking (and I ended up making a new profile after all when I realized my current many-years-old one was >5GB).

            BUT!

            While doing so I managed to break Windy in a new profile in one step -- by adding the following in Firefox's about:config, which enables the P3 color gamut:

            user_pref("gfx.color_management.display_profile", "/System/Library/ColorSync/Profiles/Display P3.icc");
            user_pref("gfx.color_management.mode", 1);
            user_pref("gfx.color_management.native_srgb", false);
            

            I'm not going to do any more troubleshooting on this, and I don't know why that breaks Windy, but that was the culprit.

            SutyS schilpatS 2 Replies Last reply Reply Quote 1
            • SutyS
              Suty Administrator @richlafferty
              last edited by

              @richlafferty Thank you for informing us about this. I will forward this to colleagues, so they can consider any potential changes.

              1 Reply Last reply Reply Quote 0
              • schilpatS
                schilpat Developers @richlafferty | Premium
                last edited by

                @richlafferty
                Hi, thank you for troubleshooting the issue and finding its cause. On our end, we currently cannot reproduce the issue even after modifying the FF config. To help us resolve the issue, could you answer the following questions?

                • what version of Firefox and OS are you using
                • since when do you experience the mentioned problems (e.g., since the last Windy update - unlikely, FF update, etc.)
                • did you perform any changes in the config prior to the rendering problems - e.g. the mentioned color space adjustments
                  • alternatively, whether you have a display that supports p3 color space
                • in case you are still able to "corrupt" your profile, could you test whether satellite overlay has any rendering artefacts (using the corrupted profile)

                It is highly possible that it could be caused by the mentioned color space conversion during the image decoding phase (we already had a similar issue on iOS last year, which caused artefacts on radar+ layer). Thank you for your cooperation!

                1 Reply Last reply Reply Quote 0
                • First post
                  Last post
                Windyty, S.E. - all rights reserved. Powered by excellent NodeBB
                NodeBB & contributors, OSM & contributors, HERE maps
                Terms of Use     Privacy Policy