Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(202)

Issue 16379002: inline WebCore::Node::Node constructor more safely (Closed)

Created:
7 years, 6 months ago by Mostyn Bramley-Moore
Modified:
7 years, 6 months ago
Reviewers:
dglazkov, adamk, eseidel
CC:
blink-reviews, dglazkov+blink, eae+blinkwatch, adamk+blink_chromium.org, Daniel Bratell
Base URL:
https://chromium.googlesource.com/chromium/blink.git@master
Visibility:
Public.

Description

inline WebCore::Node::Node constructor more safely Recently, some toolchains started giving link errors due to WebCore::Node::Node being undefined in libwebkit.so. I suspect this is due to incomplete inlining, since ContainerNode.h does not include Document.h (where the inlining was defined). This fix changes the Document argument to the Node constructor to a TreeScope, which is the sole purpose of this argument, and since Node isn't a TreeScope there's no circular dependency to worry about forward declarations. Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=151791

Patch Set 1 #

Total comments: 16

Patch Set 2 : style fixes #

Total comments: 1
Unified diffs Side-by-side diffs Delta from patch set Stats (+29 lines, -29 lines) Patch
M Source/core/dom/CharacterData.h View 1 1 chunk +2 lines, -2 lines 0 comments Download
M Source/core/dom/ContainerNode.h View 1 2 chunks +3 lines, -3 lines 0 comments Download
M Source/core/dom/Document.h View 1 chunk +0 lines, -18 lines 0 comments Download
M Source/core/dom/Node.h View 1 2 chunks +19 lines, -1 line 0 comments Download
M Source/core/dom/Notation.h View 1 1 chunk +1 line, -1 line 0 comments Download
M Source/core/dom/Notation.cpp View 1 1 chunk +2 lines, -2 lines 0 comments Download
M Source/core/dom/Text.h View 1 chunk +2 lines, -2 lines 1 comment Download

Messages

Total messages: 11 (0 generated)
Mostyn Bramley-Moore
Adding Eric for review since he commented on the patch that introduced this inlining: https://bugs.webkit.org/show_bug.cgi?id=38682 ...
7 years, 6 months ago (2013-06-04 21:49:29 UTC) #1
adamk
I'm not familiar with the build issues involved, but this seems like a fine change ...
7 years, 6 months ago (2013-06-04 23:08:08 UTC) #2
esprehn
I had always intended to make this change after I switched to m_treeScope, thanks for ...
7 years, 6 months ago (2013-06-04 23:24:00 UTC) #3
Mostyn Bramley-Moore
Style fixes should all be in patchset 2. On 2013/06/04 23:24:00, esprehn wrote: > I ...
7 years, 6 months ago (2013-06-04 23:46:01 UTC) #4
Mostyn Bramley-Moore
https://codereview.chromium.org/16379002/diff/1/Source/core/dom/CharacterData.h File Source/core/dom/CharacterData.h (right): https://codereview.chromium.org/16379002/diff/1/Source/core/dom/CharacterData.h#newcode27 Source/core/dom/CharacterData.h:27: #include "core/dom/TreeScope.h" On 2013/06/04 23:08:08, adamk wrote: > No ...
7 years, 6 months ago (2013-06-04 23:46:07 UTC) #5
adamk
lgtm
7 years, 6 months ago (2013-06-05 00:03:07 UTC) #6
commit-bot: I haz the power
CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/mostynb@opera.com/16379002/8001
7 years, 6 months ago (2013-06-05 00:03:16 UTC) #7
eseidel
lgtm https://codereview.chromium.org/16379002/diff/8001/Source/core/dom/Text.h File Source/core/dom/Text.h (right): https://codereview.chromium.org/16379002/diff/8001/Source/core/dom/Text.h#newcode61 Source/core/dom/Text.h:61: Text(TreeScope* tree_scope, const String& data, ConstructionType type) treeScope
7 years, 6 months ago (2013-06-05 00:29:11 UTC) #8
commit-bot: I haz the power
Change committed as 151791
7 years, 6 months ago (2013-06-05 01:27:16 UTC) #9
esprehn
On 2013/06/05 01:27:16, I haz the power (commit-bot) wrote: > Change committed as 151791 Hmm, ...
7 years, 6 months ago (2013-06-05 05:28:22 UTC) #10
Mostyn Bramley-Moore
7 years, 6 months ago (2013-06-05 05:38:46 UTC) #11
Message was sent while issue was closed.
Cleanup in https://codereview.chromium.org/15813017/

Should the style check false positive be reported somewhere?  (Was it even run?)

Powered by Google App Engine
This is Rietveld 408576698