Chromium Code Reviews| Index: Source/core/dom/ContainerNode.cpp |
| diff --git a/Source/core/dom/ContainerNode.cpp b/Source/core/dom/ContainerNode.cpp |
| index e9864bcd16ca9fb5d54ccd980cf004b0762e994c..a32170921d2e808f9d7a662629e228bcad14a1cb 100644 |
| --- a/Source/core/dom/ContainerNode.cpp |
| +++ b/Source/core/dom/ContainerNode.cpp |
| @@ -618,7 +618,7 @@ void ContainerNode::parserRemoveChild(Node& oldChild) |
| // This differs from other remove functions because it forcibly removes all the children, |
| // regardless of read-only status or event exceptions, e.g. |
| -void ContainerNode::removeChildren() |
| +void ContainerNode::removeChildren(bool sendModifiedEvent) |
| { |
| if (!m_firstChild) |
| return; |
| @@ -674,7 +674,7 @@ void ContainerNode::removeChildren() |
| // We don't fire the DOMSubtreeModified event for Attr Nodes. This matches the behavior |
|
sof
2014/11/20 12:09:59
Move this comment to Attr::setValue()
|
| // of IE and Firefox. This event is fired synchronously and is a source of trouble for |
| // attributes as the JS callback could alter the attributes and leave us in a bad state. |
| - if (!isAttributeNode()) |
| + if (sendModifiedEvent) |
| dispatchSubtreeModifiedEvent(); |
| } |