[ZBX-16401] Javascript error with chrome prevents maps from working Created: 2019 Jul 23  Updated: 2019 Jul 25  Resolved: 2019 Jul 24

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Frontend (F)
Affects Version/s: 4.0.9
Fix Version/s: None

Type: Incident report Priority: Minor
Reporter: Torbjorn Jansson Assignee: Zabbix Support Team
Resolution: Fixed Votes: 0
Labels: maps
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Capture.PNG    
Issue Links:
Duplicate

 Description   

Steps to reproduce:

  1. upgrade to 4.0.9
  2. open any map with chrome
  3. notice that map is completely missing, see screenshot
  4. try the same with firefox and it works

Result:
See screenshot...

there is a java script error about ED being undefined

jsLoader.php?lang=en_GB&ver=4.0.9&showGuiMessaging=1:19972 Uncaught ReferenceError: ED is not defined
    at HTMLDocument.<anonymous> (jsLoader.php?lang=en_GB&ver=4.0.9&showGuiMessaging=1:19972)
    at fire (jsLoader.php?lang=en_GB&ver=4.0.9&showGuiMessaging=1:8208)
    at Object.fireWith [as resolveWith] (jsLoader.php?lang=en_GB&ver=4.0.9&showGuiMessaging=1:8338)
    at Function.ready (jsLoader.php?lang=en_GB&ver=4.0.9&showGuiMessaging=1:8558)
    at HTMLDocument.completed (jsLoader.php?lang=en_GB&ver=4.0.9&showGuiMessaging=1:8593)

Expected:
a working map displayed just like on firefox

 

 

 Comments   
Comment by Torbjorn Jansson [ 2019 Jul 23 ]

Note that this problem also affects graphs and not just maps.

works with firefox but is broken in chrome due to javascript error

Comment by Valdis Murzins [ 2019 Jul 23 ]

Hello tobbe,

This may be because of having cached version of file. In this case hard refresh of page (Ctrl+F5) would help.
But it was not a recent change. Which version were you upgrading from?

Comment by Torbjorn Jansson [ 2019 Jul 23 ]

i upgraded from 3.0.27

yes a hard refresh made the map and graphs come back.
why was this needed in the first place?

Comment by Edgars Melveris [ 2019 Jul 24 ]

Because of cache, as Valdis stated.

Generated at Sun Apr 06 10:09:39 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.