search

GibbsConsulting / django-plotly-dash

Expose plotly dash apps as django tags
MIT License
549 stars 125 forks source link

Graph not visible on older Kindle Fire Generations #362

Closed janvv closed 2 years ago

janvv commented 2 years ago

Hi Guys! I built a dash application that so far has run on all my browsers without problems including Safari, Chrome both mobile and desktop as well as newer Kindle Fires. For Kindle, i always use a fullscreen browser such as (Fully Kiosk).

However, i have problems with older Kindle versions. For these, only the native kindle browser works but all other browsers don't show the graph component (headlines, checkboxes etc. are shown, also the loading screen). I tried several browsers and versions without success.

The Kindles that don't work are for example HD Fire 8 (6th generation), OS 5.6.8.0 (626542120). Interestingly, for the newer generations (e.g. HD Fire 8 (7th generation) running OS 5.6.9.0) the graph loads just fine.

I didn't find anything on google and would be happy about suggestions. What might be the problem? Any tips to allow backward compatibility of older browsers?

I am using the following dash packages: dash 1.21.0 core components 1.17.1 dash html components 1-1-4 dash renderer 1.9.1 django (3.1.7) using django-plotly-dash (1.6.5)

Thank you!

GibbsConsulting commented 2 years ago

@janvv at the moment we are requiring that the dash version be < 1.21.0; is it possible that using an earlier dash version resolves the problem?

Otherwise, the way forward would be to try to get an idea of what errors are being generated on the client, if that is possible, by using some form of developer tools or console.

GibbsConsulting commented 2 years ago

It does also look like the versions you refer to are quite old, and not necessarily supported, according to wikipedia

janvv commented 2 years ago

Hey guys!

I finally got it working using dash 1.19.0 This took a lot of testing (i wasn't able to load dash hosted within my local network) so i had to deploy this to a testing instance on Heroku. Your suggestion of using dash==1.19.0 did the trick. Also, here is the error that i received when loading the dashboard on a custom front-end using the native webview. Can't really tell if this is related to the problem though.

I/chromium: [INFO:CONSOLE(0)] "Failed to set referrer policy: The value 'same-origin' is not one of 'no-referrer', 'no-referrer-when-downgrade', 'origin', 'origin-when-cross-origin', or 'unsafe-url'. The referrer policy has been left unchanged.", source: (0) W/cr_BindingManager: Cannot call determinedVisibility() - never saw a connection for the pid: 10736 I/chromium: [INFO:CONSOLE(125)] "TypeError: window.ResizeObserver is not a constructor", source: (125) I/chromium: [INFO:CONSOLE(125)] "TypeError: window.ResizeObserver is not a constructor", source: (125) I/chromium: [INFO:CONSOLE(125)] "TypeError: window.ResizeObserver is not a constructor", source: (125) I/chromium: [INFO:CONSOLE(2)] "TypeError: window.ResizeObserver is not a constructor", source: (2) I/chromium: [INFO:CONSOLE(2)] "TypeError: window.ResizeObserver is not a constructor", source: (2)