1641人阅读
WEB技术（27）
Internet Feature Controls (B..C)
7 out of 11 rated this helpful
Updated: July 2012
This article describes feature controls with names that begin with the letters B or C. For links to other feature controls, see
Binary Behavior Security
Microsoft Internet Explorer 6 for Windows XP Service Pack 2 (SP2). The FEATURE_BEHAVIORS allows
to run more securely. When the feature is enabled, it can be set differently for each security zone by using the URL action flag URLACTION_BEHAVIOR_RUN. For more information, see
By default, this feature is enabled for Windows Internet Explorer and for applications hosting the
. To disable this feature by using the registry, add the name of your executable file to the following setting.
HKEY_LOCAL_MACHINE (or HKEY_CURRENT_USER)
Internet Explorer
FeatureControl
FEATURE_BEHAVIORS
contoso.exe = (DWORD)
The feature is enabled when the value is set to (DWORD)
and disabled when the value is (DWORD)
Browser Emulation
Windows Internet Explorer 8 and later. The FEATURE_BROWSER_EMULATION feature defines the default emulation mode for Internet Explorer and supports the following values.
Description
Internet Explorer 11. Webpages are displayed in IE11 edge mode, regardless of the
IE11. Webpages containing standards-based
are displayed in IE11 edge mode. Default value for IE11.
Internet Explorer 10. Webpages are displayed in IE10 Standards mode, regardless of the
Internet Explorer 10. Webpages containing standards-based
are displayed in IE10 Standards mode. Default value for Internet Explorer 10.
Windows Internet Explorer 9. Webpages are displayed in IE9 Standards mode, regardless of the
Internet Explorer 9. Webpages containing standards-based
are displayed in IE9 mode. Default value for Internet Explorer 9.
Important In Internet Explorer 10, Webpages containing standards-based !DOCTYPE directives are displayed in IE10 Standards mode.
Webpages are displayed in IE8 Standards mode, regardless of the .
Webpages containing standards-based
are displayed in IE8 mode. Default value for Internet Explorer 8
Important In Internet Explorer 10, Webpages containing standards-based !DOCTYPE directives are displayed in IE10 Standards mode.
Webpages containing standards-based
are displayed in IE7 Standards mode. Default value for applications hosting the
For more information, see
To control the value of this feature by using the registry, add the name of your executable file to the following setting and set the value to match the desired setting.
HKEY_LOCAL_MACHINE (or HKEY_CURRENT_USER)
Internet Explorer
FeatureControl
FEATURE_BROWSER_EMULATION
contoso.exe = (DWORD)
Child Window Clipping
Internet Explorer 9. Internet Explorer 9 optimized the performance of window-drawing routines that involve clipping regions associated with
. This helped improve the performance of certain window drawing operations. However, certain applications hosting the
rely on the previous behavior and do not function correctly when these optimizations are enabled. The FEATURE_ENABLE_CLIPCHILDREN_OPTIMIZATION feature can disable these optimizations.
By default, this feature is enabled for Internet Explorer and for applications hosting the
. To disable this feature by using the registry, add the name of your executable file to the following setting.
HKEY_LOCAL_MACHINE (or HKEY_CURRENT_USER)
Internet Explorer
FeatureControl
FEATURE_ENABLE_CLIPCHILDREN_OPTIMIZATION
contoso.exe = (DWORD)
The feature is enabled when the value is set to (DWORD)
and disabled when the value is (DWORD)
Circular References in Script Management
Internet Explorer 8 and later. By default, Internet Explorer reduces memory leaks caused by circular references between Internet Explorer and the Microsoft JScript engine, especially in scenarios where a webpage defines an expando and the page is refreshed.
If a legacy application no longer functions with these changes, the FEATURE_MANAGE_SCRIPT_CIRCULAR_REFS feature can disable these improvements.
By default, this feature is enabled for Internet Explorer and for applications hosting the
. To disable this feature by using the registry, add the name of your executable file to the following setting.
HKEY_LOCAL_MACHINE (or HKEY_CURRENT_USER)
Internet Explorer
FeatureControl
FEATURE_MANAGE_SCRIPT_CIRCULAR_REFS
contoso.exe = (DWORD)
The feature is enabled when the value is set to (DWORD)
and disabled when the value is (DWORD)
Note Because this feature improves the stability of Internet Explorer, disabling this feature is strongly discouraged.
Clipboard Script Control
When enabled, the FEATURE_ENABLE_SCRIPT_PASTE_URLACTION_IF_PROMPT feature allows scripts control over the Clipboard, even when the URLACTION_SCRIPT_PASTE URL action is set to &Prompt.& This allows applications hosting the
to opt out of a specific security check that may be unnecessary for the content displayed by the application. If the content is fully trusted and cannot be modified by any third-party, it may be safe to enable this feature. However, such
a design decision should include a full security assessment. For more information, see
By default, this feature is disabled for Internet Explorer and enabled for applications hosting the
. To enable this feature by using the registry, add the name of your executable file to the following setting.
HKEY_LOCAL_MACHINE (or HKEY_CURRENT_USER)
Internet Explorer
FeatureControl
FEATURE_ENABLE_SCRIPT_PASTE_URLACTION_IF_PROMPT
contoso.exe = (DWORD)
The feature is enabled when the value is set to (DWORD)
and disabled when the value is (DWORD)
Cross Domain Capture Event
The FEATURE_BLOCK_SETCAPTURE_XDOMAIN feature prevents capture events from being propagated to elements in webpages hosted on domains different than the one hosting the page containing the element that triggered the capture event.
By default, this feature is enabled for Internet Explorer 8 and for applications hosting the
. To disable this feature by using the registry, add the name of your executable file to the following setting.
HKEY_LOCAL_MACHINE (or HKEY_CURRENT_USER)
Internet Explorer
FeatureControl
FEATURE_BLOCK_SETCAPTURE_XDOMAIN
contoso.exe = (DWORD)
The feature is enabled when the value is set to (DWORD)
and disabled when the value is (DWORD)
Cross Domain Redirection
When enabled, the FEATURE_CROSS DOMAIN_REDIRECT_MITIGATION feature applies cross-domain security to support files loaded by a webpage, including images, JavaScript libraries, Cascading Style Sheets (CSS) files, Microsoft ActiveX controls, and other file-based
resources.
Note For security reasons, this feature should not be changed.
By default, this feature is enabled for Internet Explorer 8 and for applications hosting the
. To disable this feature by using the registry, add the name of your executable to the following setting.
HKEY_LOCAL_MACHINE (or HKEY_CURRENT_USER)
Internet Explorer
FeatureControl
FEATURE_CROSS_DOMAIN_REDIRECT_MITIGATION
contoso.exe = (DWORD)
The feature is enabled when the value is set to (DWORD)
and disabled when the value is (DWORD)
参考知识库
* 以上用户言论只代表其个人观点，不代表CSDN网站的观点或立场
访问：680907次
积分：8034
积分：8034
排名：第1623名
原创：63篇
转载：335篇
评论：106条
(1)(4)(7)(5)(3)(8)(3)(1)(4)(4)(1)(3)(8)(5)(3)(1)(3)(3)(4)(7)(21)(3)(11)(6)(1)(2)(13)(8)(11)(6)(12)(26)(7)(16)(5)(13)(1)(2)(13)(6)(4)(8)(11)(4)(2)(9)(1)(1)(1)(3)(2)(5)(4)(3)(1)(1)(1)(6)(1)(1)(1)(3)(6)(2)(5)(2)(6)(1)(2)(3)(7)(6)(12)(1)(3)(12)(15)(5)自从装了IE10之后，就发现好些个网站显示都不是那么的正常，网站上有些功能竟然还会出现一些意想不到的BUG&&本来就是针对IE开发的，现在下竟然用不起来了，让用户情何以堪？但是就为少量用户使用的系统去大动干戈的调整功能，这实在是让人头疼！在经过一番折腾之后，竟然找到一个非常M$的方法来解决 && 强制高版本的IE浏览器用低地版本模式显示网页。
　　就是直接让IE10默认以指定的IE版本的浏览器模式来运行，并用这个指定的版本来进行解析页面，在上一篇的文章中，我们已经其实知道了浏览器模式和文档模式的 区别，并且我们通过修改X-UA-Compatible来修改了浏览器的文档模式。这个方法本来能够解决我们当下的问题，但实际上，我们不想让整个网站用 IE8或者IE7来解析，我们仅是想针对少数的几个人在核心的功能上使用IE8来处理。当然，我们还是能够使用页面上添加meta元素的 && 但在这里，我们寻求到另外的一个解决方案：由于使用核心功能的人群可控，并且数量少。因此直接控制IE，让高版本的浏览器（版本&=8）按照指定的 低版本模式进行解析。方法是直接调整注册表项：
HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_BROWSER_EMULATION
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\MAIN\FeatureControl\FEATURE_BROWSER_EMULATION
在这个注册表项下添加一个DWORD的值，名称为：iexplore.exe值为十进制的8888或者8000。保存后，重新打开IE浏览器(IE8或更高），你就会发现，浏览器此时使用的是IE8模式在进行浏览。
　　这个方法本来是用在解决那些使用了的 应用程序在需要特定的浏览器版本支持下的。既然如此，那么让我们更进一步的了解下，在我们的程序中如果使用了IE WebBrowser之后，应该如何指定浏览器版本。其实，如果有心，你可以打开上面两个注册表项的任意一个，说不定就能看到上面已经有一些值了，这些都 是已经指定特定浏览器版本的程序。&比如我这里就有下面这些：
devenv.exe是VS2010的应用程序，在这里我们可以看到，M$强制要求devenv.exe中使用的浏览器版本为IE9。既然他都这么 用，自然而然，我们也应该能从中找到解决问题的方法了。如果你在应用程序：SomeApplication.exe中使用了IE WebBrowser的控件，那么你如果想在SomeApplication.exe这个程序中的WebBrowser控件以某一个指定的版本的浏览器进 行解析页面，你就可以在上述的那个注册表项中加入你的程序了。比如你要指定为IE8运行，那么你只要新建一个DWORD值，名称为SomeApplication.exe，值为：8888即可。
　　到此我们已经会为浏览器和WebBrowser控件指定特定的浏览器运行版本了，但可能你会发现，后面的数值有那么一些不好理解，那我要使用IE怎么办？同样IE8怎么会有这样的数值呢，个表示什么？如果你也有疑问，那么请看下表吧，罗列出了常用的数值对照说明表：
Internet Explorer 10。网页以IE 10的标准模式展现，页面!DOCTYPE无效
Internet Explorer 10。在IE 10标准模式中按照网页上!DOCTYPE指令来显示网页。Internet Explorer 10 默认值。
Windows Internet Explorer 9. 强制IE9显示，忽略!DOCTYPE指令
Internet Explorer 9. Internet Explorer 9默认值，在IE9标准模式中按照网页上!DOCTYPE指令来显示网页。
Internet Explorer 8，强制IE8标准模式显示，忽略!DOCTYPE指令
Internet Explorer 8默认设置，在IE8标准模式中按照网页上!DOCTYPE指令展示网页
使用WebBrowser Control控件的应用程序所使用的默认值，在IE7标准模式中按照网页上!DOCTYPE指令来展示网页。
FEATURE_BROWSER_EMULATION设置说明
1. 准模式指的是浏览器模式，而!DOCTYPE控制的是文档模式。
2. 应用程序中包含的WebBrowser Control控件时，默认WebBrowser使用的是IE7，这是个很重要的知识点。
好了，到此应该对于IE运行于指定版本的方法已经介绍完毕，同时自己程序中如何设置的方法也有了明确方向，接下来的事情就是&&用起来吧。
阅读(...) 评论()trackbacks-0
一.问题的提出
偶然发现，Winform里的WebBrowser和IE实际安装的版本似乎并不同步，很有趣！
下面有张图，里面一个窗口是用IE9打开某网站，另一个窗口是用Winform+WebBrowser打开同样的网站，有意思的事情出现了。
在IE9窗口中，这个网站左边菜单树无法显示，原因是IE9使用的技术较新，而网站使用的技术较旧，未能及时同步更新到支持IE9所致。该如何办呢？
微软在IE9中提供一个兼容性视图功能，只要一点击兼容性视图就可以兼容旧版本浏览器的网站。&
引用MSDN &To overcome potential compatibility issues, Internet Explorer supports a feature called Compatibility View that allows users to display troublesome pages in IE7 mode. & URL:
也就是说，这个兼容模式就是IE7的模式。
又查了些ms资料，发现这个兼容性视图在IE8时首次引入，在IE9，IE10中都将继续支持。
再翻回来看Winform+WebBrowser这个窗口，它打开同样的网站却能显示左边菜单树，这样看来，似乎WebBrowser不用设置就默认自动打开了兼容性视图模式。
现在就去仔细查一下权威资料，核实一下两个问题：1.Webbrowser与IE到底是什么关系？是否确实用ie内核, 是否本质上和360安全浏览器，傲游浏览器和腾讯TT等IE内核浏览器相同。2.Webbrowser是否使用兼容浏览模式，以及这个模式是否能改？
二.查询结果
1.webbrowser调用的就是本机IE9，并且webbrowser默认就是运行在IE7 mode下，除非你改变它.
发现一个msdn的帖子，明确表示webbrowser调用的就是本机IE9，并且webbrowser默认就是运行在IE7 mode下，除非你改变它。How to make c# WebBrowser equivalent to IE browser&
摘几句：Wow first post with such bold claim without any source backing up. You probably should read the IE SDK (the manual you need to read if you want to use the webbrowser control) or dig through the IE programming forums (that's the place others often go when they are stuck on IE programming) if you want to use the webbrowser control.
Webbrowser is a wrapper around IE APIs. There is no such thing as multiple versions of IE coexisting on the same computer. You will always get the one and only version of IE installed on the computer from webbrowser control.
There are many, many documented setting differences between default IE and webbrowser. Basically you don't have to opt out new features in webbrowser that may break your app (the Visual Studio team learned a hard lesson here, when IE8 breaks Visual Studio's wizards) , you have to write code to opt in, unless the improvement is security related. That means the webbrowser will run in IE7 mode unless you change the mode in feature control.
Note some web site declare their requirement of IE7 or IE8 mode. It may not be wise to force the IE9 mode.&
2.微软新闻组的一个帖子，Webbrowser Control without IE，里面明确提到，不装IE，无法用webbrowser.
IE must be installed on the machine for you to use Webbrowser Control.
Internet Explorer MUST be installed to use the WebBrowser control.& There are simply no ifs, ands, or buts about it.& How can you expect to use IE functionality if IE is not installed?
3.如何设置WebBrowser在IE9 mode下工作呢？答曰：需要修改注册表，具体看下面4，5，6，尤其6最全面，可以光看6。
4.WPF webbrowser control using IE7 instead of IE9
摘抄几句：How do I make it so the WPF WebBrowser control will use IE9 as the browser engine instead of IE7?I have some HTML that is rendering differently in the WebBrowser control than in the IE9 browser. When I run the following javascript in the WebBrowser, the result is "7". as in IE7.
I found an article by Rick Strahl that describes registry settings that will get the WebBrowser to use IE9. But I would like to avoid that. And I am interested to know how IE7 comes about being used.http://www./weblog/posts/2011/May/21/Web-Browser-Control-Specifying-the-IE-Version回答：You want to avoid the only documented way to set document compatibility mode for webbrowser hosts? Why?
5.WebBrowser and CSS3 ?Web browser control by default runs in compatibility mode unless you set the feature browser emulation registry key. The fact that IE9 is able to render CSS3 correctly and browser control is not seems to suggest browser control is not running in IE9 standards mode.
You'll need to set Browser emulation feature key (FEATURE_BROWSER_EMULATION) described at this link
You can use 9000 value, unless you want to force IE 9 standards mode for all pages. In case of later, you need to use 9999.
If hklm and 64bit machine used, you need to check is Wow6432Node needs to be changed.
And finally you need to add process name hosting browser control as value name in the registry key.
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\MAIN\FeatureControl\FEATURE_BROWSER_EMULATION]"prevhost.exe"=dword:00001f40"sllauncher.exe"=dword:00001f40"WindowsFormsApplication1.exe"=dword:0000270f
6.Web Browser Control & Specifying the IE Version
I use the Internet Explorer Web Browser Control in a lot of my applications to display document type layout. HTML happens to be one of the most common document formats and displaying data in this format & even in desktop applications, is often way easier than using normal desktop technologies.
One issue the Web Browser Control has that it&s perpetually stuck in IE 7 rendering mode by default. Even though IE 8 and now 9 have significantly upgraded the IE rendering engine to be more CSS and HTML compliant by default the Web Browser control will have none of it. IE 9 in particular & with its much improved CSS support and basic HTML 5 support is a big improvement and even though the IE control uses some of IE&s internal rendering technology it&s still stuck in the old IE 7 rendering by default.
This applies whether you&re using the Web Browser control in a WPF application, a WinForms app, a FoxPro or VB classic application using the ActiveX control. Behind the scenes all these UI platforms use the COM interfaces and so you&re stuck by those same rules.
Feature Delegation via Registry HacksFortunately starting with Internet Explore 8 and later there&s a fix for this problem via a registry setting. You can specify a registry key to specify which rendering mode and version of IE should be used by that application. These are not global mind you & they have to be enabled for each application individually.
There are two different sets of keys for 32 bit and 64 bit applications.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\MAIN\FeatureControl\FEATURE_BROWSER_EMULATION
Value Key: yourapplication.exe
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\MAIN\FeatureControl\FEATURE_BROWSER_EMULATION
Value Key: yourapplication.exe
The value to set this key to is (taken from MSDN here) as decimal values:
F) Internet Explorer 9. Webpages are displayed in IE9 Standards mode, regardless of the !DOCTYPE directive.
8) Internet Explorer 9. Webpages containing standards-based !DOCTYPE directives are displayed in IE9 mode.
B8) Webpages are displayed in IE8 Standards mode, regardless of the !DOCTYPE directive.
F40) Webpages containing standards-based !DOCTYPE directives are displayed in IE8 mode.
B58) Webpages containing standards-based !DOCTYPE directives are displayed in IE7 Standards mode.
ok, 言尽至此，无话可说了！
阅读(...) 评论()Win7更新补丁时提示0X错误代码的原因及解决办法
作者：佚名
字体：[ ] 来源：互联网 时间：07-07 14:57:40
最近有很多用户在更新补丁总是弹出了“0X”的错误提示，对于该错误很多用户不知道是什么造成的,下面小编给大家分享Win7更新补丁时提示0X错误代码的原因及解决办法，一起看下吧
win7系统升级是windows日常维护的一种方式，通常情况当win7存在漏洞时，微软就会想到推送最新的更新补丁来强化系统，不过很多用户在更新补丁总是弹出了&0X&的错误提示，对于该错误很多用户不知道是什么造成的,下面小编给大家分享Win7更新补丁时提示0X错误代码的原因及解决办法，一起看下吧
　　这个错误是我在装VS2012的时候遇到的，在错误日志中发现了这个错误代码--0x。
　　通过长时间的查找资料和尝试，我基本搞明白了0x的大致原因和解决办法，顺便记录下来。
　　这个问题在安装很多软件的时候都可能会遇到，典型的像MSE（Microsoft Security Essentials），Zune，Visual Studio 2012，.NET 等，貌似都是微软的东西么。。。
　　先贴上日志文件中的错误部分的记录：
　　［199C:1944］［T17:24:08］： Error 0x： Failed to install MSI package.
　　［199C:1944］［T17:24:08］： Error 0x： Failed to execute MSI package.
　　［C］［T17:24:08］： Error 0x： Failed to configure per-machine MSI package.
　　［C］［T17:24:08］： MUX： Installation size in bytes for package： vs_devenv MaxAppDrive： 614400 MaxSysDrive： 450560 AppDrive： 0 SysDrive： 311296
　　［C］［T17:24:08］： MUX： Return Code:0x Msi Messages:1406 Result Detail:0 Restart:None
　　［C］［T17:24:09］： MUX： Unregistering and registering msiexec.
　　［C］［T17:24:09］： MUX： Executing Process： Exe:C：\Windows\system32\msiexec.exe Arguments:/unreg
　　［C］［T17:24:09］： MUX： Process exit code： 0
　　［C］［T17:24:09］： MUX： Executing Process： Exe:C：\Windows\system32\msiexec.exe Arguments:/regserver
　　［C］［T17:24:09］： MUX： Process exit code： 0
　　［C］［T17:24:09］： MUX： Retrying the package again
　　［C］［T17:24:09］： Application requested retry of package： vs_devenv， encountered error： 0x. Retrying.。。
　　［199C:1944］［T17:24:09］： Applying execute package： vs_devenv， action： Install， path： C：\ProgramData\Package Cache\{330E5D98-20D2-4CA4-AE51-FCB8AA80F634}v11.0.50727\packages\vs_devenv\vs_devenv.msi， arguments： & MSIFASTINSTALL=&7& VSEXTUI=&1& VS7.3643236F_FC70_11D3_A536_BB8=&H：\Program Files\microsoft visual studio 12&&
　　［C］［T17:24:12］： MUX： ExecuteError： Package （vs_devenv） failed： Error Message Id： 1406 ErrorMessage： Could not write value devenv.exe to key \SOFTWARE\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_RESTRICT_ABOUT_PROTOCOL_IE7. Verify that you have sufficient access to that key， or contact your support personnel.
　　［199C:1944］［T17:24:13］： Error 0x： Failed to install MSI package.
　　［199C:1944］［T17:24:13］： Error 0x： Failed to execute MSI package.
　　［C］［T17:24:13］： Error 0x： Failed to configure per-machine MSI package.
　　网上也有不少人遇到这个问题并且贴出了这段错误日志，然后得到的回复普遍是：安装包有问题，重新下一个iso或者在线安装之类的回答，而这种方法解决问题的几率貌似灰常低。
　　其实，有一种可能的问题是：注册表中
　　HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_RESTRICT_ABOUT_PROTOCOL_IE7的权限有问题。如果安装了某些优化软件，可能会将&完全读取&权限给毙了，只给&读取&权限。只要手动打开&完全读取&权限，应该就有解决的可能性。
　　当然，这只是多种错误情况的一种，具体问题还得看当时的错误日志。
　　然后，是安装.NET Framework时出现错误代码0x的可能的解决办法。（参考microsoft官方帮助与支持）
　　出现这个错误的原因是：如果 MSI 软件更新注册已损坏，或如果计算机中的 .NET 安装已损坏，可能会发生此问题。
　　方法1：修复 MSI 软件更新注册损坏问题。若要自动修复，可以从找到相关软件下载，安装即可。但是此方法不适用于Win7.
　　方法2：修复未更新版本的 .NET Framework。
　　如果您运行的是 Win Vista 或 Win7，请执行以下步骤：
　　关闭所有应用程序。
　　单击&开始&，在&搜索&框中键入&卸载&，然后单击&卸载程序&。
　　双击&Microsoft .NET Framework 4 Client Profile&。
　　选择&修复 .NET Framework 4 Client Profile 至其原始状态&，然后单击&下一步&。
　　完成修复后，请单击&完成&。
　　单击&立即重新启动&以重新启动计算机。
　　重新启动计算机后，单击&开始&，在&搜索&框中键入&Windows Update&，然后单击&Windows Update&安装最新的 Windows 更新。
　　如果您运行的是 WinXP，请执行以下步骤：
　　关闭所有应用程序。
　　依次单击&开始&、&控制面板&和&添加或删除程序&。
　　单击已安装程序列表中的&Microsoft .NET Framework 4 Client Profile&，然后单击&更改/删除&。
　　选择&修复 .NET Framework 4 Client Profile 至其原始状态&，然后单击&下一步&。
　　完成修复后，请单击&完成&。
　　单击&立即重新启动&。
　　重新启动计算机并登录Windows后，单击&开始&，在&搜索&框中键入&Windows Update&，然后单击&Windows Update&。
　　单击&检查更新&。扫描完成后，单击&安装 Windows 更新&，然后遵循说明执行操作。
以上所述是小编给大家介绍的Win7更新补丁时提示0X错误代码的原因及解决办法，希望对大家有所帮助，如果大家有任何疑问请给我留言，小编会及时回复大家的。在此也非常感谢大家对脚本之家网站的支持！
大家感兴趣的内容
12345678910
最近更新的内容}