MutationObserverInit
dictionary's optional
attributeFilter
property is an array of strings specifying the names of the attributes whose values are to be monitored for changes.
If this property is specified, there's no need to also set
属性
to
true
, as it's implied.
若
属性
permission is
true
but no
attributeFilter
is included in the options object, all attributes' values are watched for changes.
var options = {
attributeFilter: [ "list", "of", "attribute", "names" ]
}
An array of
DOMString
objects, each specifying the name of one attribute whose value is to be monitored for changes. There is no default value.
If this property exists on the options object when the
MutationObserver()
构造函数用于创建新的
MutationObserver
, attribute monitoring is enabled regardless of whether or not the
属性
特性为
true
.
In this example, a Mutation Observer is set up to watch for changes to the
status
and
username
attributes in any elements contained within a subtree that displays the names of users in a chat room. This lets the code, for example, reflect changes to users' nicknames, or to mark them as away from keyboard (AFK) or offline.
function callback(mutationList) {
mutationList.forEach(function(mutation) {
switch(mutation.type) {
case "attributes":
switch(mutation.attributeName) {
case "status":
userStatusChanged(mutation.target.username, mutation.target.status);
break;
case "username":
usernameChanged(mutation.oldValue, mutation.target.username);
break;
}
break;
}
});
}
var userListElement = document.querySelector("#userlist");
var observer = new MutationObserver(callback);
observer.observe(userListElement, {
attributeFilter: [ "status", "username" ],
attributeOldValue: true,
subtree: true
});
callback()
function—which will be passed into the
observe()
method when starting the observer, looks at each item in the list of
MutationRecord
objects. For any items representing an attribute change (which can be detected by the value of
MutationRecord.type
being
"attributes"
), we use the attribute's name, obtained using
MutationRecord.attributeName
, to identify the type of change that occurred and then dispatch to the appropriate handler function.
Note the use of
MutationRecord.oldValue
to get the previous value of the
"username"
property so we have that information when doing lookups in our local array of users.
当
observe()
is called, the specified options include both
attributeFilter
and
subtree
, so that we monitor the attribute values for all of the nodes contained within the subtree rooted at the node with the ID
"userlist"
。
attributeOldValue
option is set to
true
because we want the prior value of the changed attributes recorded and reported in the mutation records we receive.
| 规范 | 状态 | 注释 |
|---|---|---|
|
DOM
The definition of 'MutationObserverInit: attributeFilter' in that specification. |
实时标准 |
| 桌面 | 移动 | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
attributeFilter
|
Chrome
26
|
Edge
12
注意事项
|
Firefox 14 |
IE
11
注意事项
|
Opera 15 |
Safari
7
|
WebView Android ? |
Chrome Android
26
|
Firefox Android 14 | Opera Android 14 |
Safari iOS
7
|
Samsung Internet Android
1.5
|
完整支持
兼容性未知
见实现注意事项。
要求使用供应商前缀或不同名称。
MutationObserverInit
attributeFilter
attributeOldValue
属性
characterData