Bing 地图 - 保留特定版本
我正在使用 Bing 地图，并使用 CSS 设计 HTML 元素的样式以获得自定义控件。我将脚本的版本称为 7.0，如下所示。然而，Bing 团队似乎正在对从一个 7.0 版本返回到另一个版本的 HTML 元素进行更改。现在他们更改了元素的类名，我的 CSS 不再工作。因此，我想知道是否有一种方法不仅可以指定我要使用版本 7.0，而且可以更具体，以便我可以获得版本 7.0.2011100111334.47。这可能吗？
<script type="text/javascript" src="http://ecn.dev.virtualearth.net/mapcontrol/mapcontrol.ashx?v=7.0"></script>
这似乎不起作用：
<script type="text/javascript" src="http://ecn.dev.virtualearth.net/mapcontrol/mapcontrol.ashx?v=7.0.2011100111334.47"></script>
I'm using Bing Maps, and with CSS I'm styling the HTML-elements to get customized controls. I call version 7.0 of the script as seen below. However, it seems that the Bing team are making changes in what HTML-elements are returned from one 7.0-version to another. Now they have changed the class-names of the elements and my CSS is no longer working. I'm therefor wondering if there is a way to not only specify that I want to use version 7.0, but to be more specific so that I can get version 7.0.2011100111334.47 for example. Is this possible?
<script type="text/javascript" src="http://ecn.dev.virtualearth.net/mapcontrol/mapcontrol.ashx?v=7.0"></script>
This does not seem to work:
<script type="text/javascript" src="http://ecn.dev.virtualearth.net/mapcontrol/mapcontrol.ashx?v=7.0.2011100111334.47"></script>
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
不，不幸的是没有办法做到这一点，Bing 多次表示他们不能支持开发人员使用未记录/不受支持的方式自定义地图，因此不保证不改变他们执行某些操作（例如 div 名称）的方式。
不幸的是，这意味着如果你想做一些 API 本身没有提供方法的事情，那么你就必须冒它无法工作的风险:-)
我们已经问过为什么我们不能针对特定的次要版本，答复通常是基于它们不想支持多个版本，我可以理解，即使它使高级定制变得麻烦
No unfortunately there is not a way of doing this, Bing have said a number of times that they cannot support developers using undocumented/unsupported ways of customizing the map and don't therefore guarantee to not change how they do some things like div names.
Unfortunately this means if you want to do something that the API doesn't natively provide a way to do then you have to take the risk of it not working :-)
We have asked why we cannot target specific minor versions an the reply is usually based around them not wanted to have to support multiple versions which I can understand even if it makes advanced customization troublesome