Tables with display:inline rendered in wrong position.

Source/core/rendering/RenderObject.cpp

Index: Source/core/rendering/RenderObject.cpp
diff --git a/Source/core/rendering/RenderObject.cpp b/Source/core/rendering/RenderObject.cpp
index bd3a26ede8eb02c0487d390342d6848837dac644..6e30912832b1caa0af214ac877f1a8d07dc72fce 100644
--- a/Source/core/rendering/RenderObject.cpp
+++ b/Source/core/rendering/RenderObject.cpp
@@ -166,6 +166,8 @@ RenderObject* RenderObject::createObject(Element* element, RenderStyle* style)
     // treat <rt> as ruby text ONLY if it still has its default treatment of block
     if (element->hasTagName(rtTag) && style->display() == BLOCK)
         return new RenderRubyText(element);
+    if (element->hasTagName(tableTag) && style->display() == INLINE)
+        return new RenderTable(element);

[esprehn, 2013/08/28 18:17:54]

This does not appear correct, if you make a table display: inline why shouldn't
it be inline?

This will break things like:

<div>Hello <table><tr><td>World</td></tr></table> </div>

table, tr, td { display: inline; }

[suchit.agrawal, 2013/08/29 04:31:09]

I have tried this example and check the behavior.
You are right, now it's behavior is changed but it is matching with Firfox.

[suchit.agrawal, 2013/08/29 05:49:05]

Our previous behavior of this example was wrong. 'World' was rendered in the
next line. But It should be in same line of 'Hello'.
After this patch, Behavior is correct.  

     if (RuntimeEnabledFeatures::cssRegionsEnabled() && style->isDisplayRegionType() && !style->regionThread().isEmpty() && doc->renderView())
         return new RenderRegion(element, 0);