Use WeakPtr for RenderTreePosition::m_nextSibling
authorantti@apple.com <antti@apple.com@268f45cc-cd09-0410-ab3c-d52691b4dbfc>
Sat, 6 Jan 2018 21:01:19 +0000 (21:01 +0000)
committerantti@apple.com <antti@apple.com@268f45cc-cd09-0410-ab3c-d52691b4dbfc>
Sat, 6 Jan 2018 21:01:19 +0000 (21:01 +0000)
commit77649c7ae8ecb074cfc308f6f14db1f27a8409e1
tree4c9c3892d434e1fdced54fc52f5a7ebf450291b7
parent94ee4b4f767c807d4011a0b20f53218916222f53
Use WeakPtr for RenderTreePosition::m_nextSibling
https://bugs.webkit.org/show_bug.cgi?id=181363

Reviewed by Zalan Bujtas.

For safety. In most cases it is null and won't cause us to instantiate WeakReferences for
many new objects.

* rendering/updating/RenderTreePosition.cpp:
(WebCore::RenderTreePosition::computeNextSibling):
* rendering/updating/RenderTreePosition.h:
(WebCore::RenderTreePosition::RenderTreePosition):
(WebCore::RenderTreePosition::nextSibling const):

git-svn-id: https://svn.webkit.org/repository/webkit/trunk@226488 268f45cc-cd09-0410-ab3c-d52691b4dbfc
Source/WebCore/ChangeLog
Source/WebCore/rendering/updating/RenderTreePosition.cpp
Source/WebCore/rendering/updating/RenderTreePosition.h