14.05.2018, 15:02
(This post was last modified: 14.05.2018, 15:03 by routeconverter.)
That is an interesting observation. The Eclipse SWT map implementation fires up the Windows WebBrowser Control internally while the JavaFX-based map uses a WebKit engine.
It's not the WebKit engine itself since the map is working for other non-Google tile servers.
It's not your ISP or IP-address being blocked since it works with Chrome.
So it has to be something with the way performs the GET requests for the map.
It could be that openstreetmap.org blocks requests from the WebKit engine. Or an antivirus/firewall something on your machine. Did you check that?
It's not the WebKit engine itself since the map is working for other non-Google tile servers.
It's not your ISP or IP-address being blocked since it works with Chrome.
So it has to be something with the way performs the GET requests for the map.
It could be that openstreetmap.org blocks requests from the WebKit engine. Or an antivirus/firewall something on your machine. Did you check that?
--
Christian
Christian