如何更改 Internet Explorer 中工具栏按钮的顺序？
我知道我可以简单地写入 CommandBandLayout 注册表项，但由于我不知道它是什么格式，我怀疑这是否安全。
另外，这个答案表明这是错误的解决方案： 如何修改 CommandBandLayout reg key value< /a>
但是我怎样才能稍微改变一下顺序呢？我编写了一个 Internet Explorer 插件，并通过将其放入 HKCU 来注册它，但默认情况下它会从屏幕上掉下来，因此用户很难找到它。我想使栏更宽或将按钮移回屏幕中。
I know I can simply write to the CommandBandLayout regkey but since I don't know what format it is I'm having doubts if that is safe.
Also, this answer suggest it's the wrong solution: How to modify CommandBandLayout reg key value
But how can I change the order a bit? I have written an Internet Explorer Add-on and I've registered it by putting it in HKCU but by default it falls off the screen so users are having trouble finding it. I would like to make the bar wider or move the button back in the screen.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
您无法重新排列 IE 的工具栏布局。 IE 对其进行管理，用户可以使用内置 UI 对其进行自定义，但您不能。对不起。
实际上你可以，正如你所注意到的，布局以二进制格式保存在注册表中，但它涉及大量二进制数据的逆向工程，这些数据可能存储在注册表中，也可能不存储在注册表中，因为它是一个未记录的实现细节，IE 团队可以（并且实际上确实）改变了它在每个新版本 IE 中的工作方式。您必须将代码编写三次：一次用于 IE6，一次用于 IE7，一次用于 IE8。当 IE9 发布时，也不能确定它会是一样的。每一种都使用不同的格式，并且对于何时保存数据以及如何保存数据有不同的规则。并忘记升级场景。
所以，告诉提出这个要求的人你做不到。
实在不行，再推回去吧。事实上，我一直处于这个等式的两边；我在 IE 团队中，看到了扩展在尝试执行此操作时所造成的灾难，并且我曾在具有相同要求的公司工作过，我已经完成了逆向工程并试图保持其正常运行。相信我，你不想这样做。
You cannot re-arrange IE's toolbar layout. IE manages it, and users can customize it using the built-in UI, but you can't. Sorry.
Actually you can, as you've noticed that the layout is persisted in a binary format in the registry, but it involves a lot of reverse engineering of binary data that may or may not be stored in the registry and since it's an undocumented implementation detail, the IE team can (and actually does) change how it works in every new version of IE. You'd have to write the code three times: once for IE6, once for IE7, once for IE8. And again for IE9 when it ships, and there's no certainty it would be the same anyway. Each one uses a different format and has different rules about when data and how the data is persisted. And forget about the upgrade scenarios.
So, tell whoever made that requirement that you can't do it.
No really, push back. I've actually been on both sides of this equation; I was on the IE team and saw the disasters that extensions caused when they tried to do this, and I've been at companies who had the same requirements and I've done the reverse engineering and tried to keep it working. Trust me, you don't want to do this.